diff options
Diffstat (limited to 'docs/htmldocs/Samba3-ByExample')
42 files changed, 3228 insertions, 3228 deletions
diff --git a/docs/htmldocs/Samba3-ByExample/2000users.html b/docs/htmldocs/Samba3-ByExample/2000users.html index 08d6758469..5ba3718066 100644 --- a/docs/htmldocs/Samba3-ByExample/2000users.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.75.2"><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" title="Chapter 6. A Distributed 2000-User Network"><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#id2589825">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2589856">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2589924">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2590197">Technical Issues</a></span></dt><dt><span class="sect2"><a href="2000users.html#id2591142">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2591160">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2594319">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2594466">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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2589825"></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="id2589844"></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" title="Assignment Tasks"><div class="titlepage"><div><div><h3 class="title"><a name="id2589856"></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">“Making Happy Users”</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="id2589884"></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" title="Dissection and Discussion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2589924"></a>Dissection and Discussion</h2></div></div></div><p> -<a class="indexterm" name="id2589932"></a> -<a class="indexterm" name="id2589939"></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">“Making Happy Users”</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="id2589963"></a> -<a class="indexterm" name="id2589970"></a> -<a class="indexterm" name="id2589977"></a> -<a class="indexterm" name="id2589984"></a> +<a class="indexterm" name="id2583878"></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="id2590023"></a> -<a class="indexterm" name="id2590030"></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="id2590054"></a> -<a class="indexterm" name="id2590061"></a> -<a class="indexterm" name="id2590068"></a> -<a class="indexterm" name="id2590075"></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="id2590095"></a> -<a class="indexterm" name="id2590105"></a> -<a class="indexterm" name="id2590111"></a> -<a class="indexterm" name="id2590118"></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="id2590134"></a> -<a class="indexterm" name="id2590141"></a> -<a class="indexterm" name="id2590148"></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="id2590165"></a> +<a class="indexterm" name="id2584080"></a> In <a class="link" href="happy.html" title="Chapter 5. Making Happy Users">“Making Happy Users”</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" title="Technical Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2590197"></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 class="itemizedlist" type="disc"><li class="listitem"><p><a class="indexterm" name="id2590213"></a> - User needs such as mobility and data access</p></li><li class="listitem"><p>The nature of Windows networking protocols</p></li><li class="listitem"><p>Identity management infrastructure needs</p></li></ul></div><p>Let's look at each in turn.</p><div class="sect3" title="User Needs"><div class="titlepage"><div><div><h4 class="title"><a name="id2590236"></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" title="Technical Issues"><div class="titlepa 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="id2590261"></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" title="Technical Issues"><div class="titlepa This way, they can synchronize all files that have changed since each logon to the network. </p><p> - <a class="indexterm" name="id2590288"></a> - <a class="indexterm" name="id2590297"></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" title="Technical Issues"><div class="titlepa profile involves a transfer of over 750 KB from the profile server to and from the client. </p><p> - <a class="indexterm" name="id2590318"></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" title="The Nature of Windows Networking Protocols"><div class="titlepage"><div><div><h4 class="title"><a name="id2590330"></a>The Nature of Windows Networking Protocols</h4></div></div></div><p> - <a class="indexterm" name="id2590339"></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" title="Technical Issues"><div class="titlepa 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="id2590359"></a> - <a class="indexterm" name="id2590366"></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">“Making Happy Users”</a>, you implemented this in the new Windows XP Professional standard @@ -210,14 +210,14 @@ productivity.</p><div class="sect2" title="Technical Issues"><div class="titlepa 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="id2590394"></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="id2590409"></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 @@ -225,22 +225,22 @@ productivity.</p><div class="sect2" title="Technical Issues"><div class="titlepa </p><p> When a Windows NT4/200x/XP Professional client user logs onto the network, several important things must happen. - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> - <a class="indexterm" name="id2590432"></a> + </p><div class="itemizedlist"><ul type="disc"><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2590445"></a> - <a class="indexterm" name="id2590452"></a> + </p></li><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2590464"></a> + </p></li><li><p> + <a class="indexterm" name="id2584379"></a> The client must locate the closest domain controller. - </p></li><li class="listitem"><p> + </p></li><li><p> The client must log onto a domain controller and obtain as part of that process the location of the user's profile, load it, connect to redirected folders, and establish all network drive and printer connections. - </p></li><li class="listitem"><p> + </p></li><li><p> The domain controller must be able to resolve the user's credentials before the logon process is fully implemented. </p></li></ul></div><p> @@ -256,15 +256,15 @@ productivity.</p><div class="sect2" title="Technical Issues"><div class="titlepa name both by broadcast and Unicast registration that is directed at the WINS server. </p><p> - <a class="indexterm" name="id2590511"></a> - <a class="indexterm" name="id2590518"></a><a class="indexterm" name="id2590527"></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="id2590541"></a> - <a class="indexterm" name="id2590550"></a> - <a class="indexterm" name="id2590557"></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" title="Technical Issues"><div class="titlepa was listed in the WINS server response to a request for the list of domain controllers. </p><p> - <a class="indexterm" name="id2590583"></a> - <a class="indexterm" name="id2590592"></a> - <a class="indexterm" name="id2590599"></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" title="Technical Issues"><div class="titlepa needs. A secondary fact we need to know is, what happens when local domain controllers fail or break? </p><p> - <a class="indexterm" name="id2590619"></a> - <a class="indexterm" name="id2590626"></a> - <a class="indexterm" name="id2590632"></a> - <a class="indexterm" name="id2590639"></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" title="Technical Issues"><div class="titlepa domain controllers. Since there can be only one PDC, all additional domain controllers are by definition BDCs. </p><p> - <a class="indexterm" name="id2590656"></a> - <a class="indexterm" name="id2590663"></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" title="Identity Management Needs"><div class="titlepage"><div><div><h4 class="title"><a name="id2590677"></a>Identity Management Needs</h4></div></div></div><p> - <a class="indexterm" name="id2590685"></a> - <a class="indexterm" name="id2590692"></a> - <a class="indexterm" name="id2590699"></a> - <a class="indexterm" name="id2590706"></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" title="Technical Issues"><div class="titlepa by which user credentials are validated and filtered and appropriate rights and privileges are allocated. </p><p> - <a class="indexterm" name="id2590723"></a> - <a class="indexterm" name="id2590730"></a> - <a class="indexterm" name="id2590737"></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" title="Technical Issues"><div class="titlepa 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="id2590768"></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" title="Technical Issues"><div class="titlepa demands as the demand for directory services that can be coupled with other information systems is catching on. </p><p> - <a class="indexterm" name="id2590787"></a> - <a class="indexterm" name="id2590793"></a> - <a class="indexterm" name="id2590800"></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" title="Technical Issues"><div class="titlepa and large corporations that have a scientific or engineering focus. </p><p> - <a class="indexterm" name="id2590816"></a> - <a class="indexterm" name="id2590822"></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="id2590837"></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" title="Technical Issues"><div class="titlepa 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="id2590854"></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="id2590872"></a> - <a class="indexterm" name="id2590878"></a> - <a class="indexterm" name="id2590888"></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">“Making Happy Users”</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,8 +386,8 @@ productivity.</p><div class="sect2" title="Technical Issues"><div class="titlepa 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="id2590917"></a> - <a class="indexterm" name="id2590924"></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="2000users.html#chap7net" title="Figure 6.6. Network Topology 2000 User Complex Design A">“Network Topology 2000 User Complex Design A”</a>) demands the placement of @@ -398,7 +398,7 @@ productivity.</p><div class="sect2" title="Technical Issues"><div class="titlepa productivity against the cost of network management and maintenance. </p><p> - <a class="indexterm" name="id2590948"></a> + <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">“Network Topology 2000 User Complex Design B”</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 @@ -409,22 +409,22 @@ productivity.</p><div class="sect2" title="Technical Issues"><div class="titlepa the ability for network users to roam globally without some compromise in how they may access global resources. </p><p> - <a class="indexterm" name="id2590975"></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="id2590987"></a> - <a class="indexterm" name="id2590994"></a> - <a class="indexterm" name="id2591003"></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="id2591018"></a> - <a class="indexterm" name="id2591025"></a> - <a class="indexterm" name="id2591032"></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" title="Technical Issues"><div class="titlepa 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="id2591057"></a> - <a class="indexterm" name="id2591066"></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" title="Technical Issues"><div class="titlepa 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="id2591088"></a> - <a class="indexterm" name="id2591097"></a> - <a class="indexterm" name="id2591104"></a> - <a class="indexterm" name="id2591113"></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" title="Technical Issues"><div class="titlepa 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" title="Political Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2591142"></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,11 +471,11 @@ productivity.</p><div class="sect2" title="Technical Issues"><div class="titlepa become usable in a reasonable period, typically minutes rather than days (the old limitation of highly manual systems). - </p></div></div><div class="sect1" title="Implementation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2591160"></a>Implementation</h2></div></div></div><p> - <a class="indexterm" name="id2591167"></a> - <a class="indexterm" name="id2591174"></a> - <a class="indexterm" name="id2591181"></a> - <a class="indexterm" name="id2591188"></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="2000users.html#chap7idres" title="Figure 6.1. Samba and Authentication Backend Search Pathways">“Samba and Authentication Backend Search Pathways”</a> demonstrates how Samba uses winbind, LDAP, and NIS, the traditional system @@ -483,13 +483,13 @@ productivity.</p><div class="sect2" title="Technical Issues"><div class="titlepa 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="id2591252"></a> - <a class="indexterm" name="id2591259"></a> - <a class="indexterm" name="id2591266"></a> - <a class="indexterm" name="id2591273"></a> - <a class="indexterm" name="id2591279"></a> - <a class="indexterm" name="id2591286"></a> - <a class="indexterm" name="id2591293"></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" title="Technical Issues"><div class="titlepa backend. LDAP is the preferred passdb backend for distributed network operations. </p><p> - <a class="indexterm" name="id2591321"></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 @@ -509,8 +509,8 @@ 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="2000users.html#ch7singleLDAP" title="Figure 6.2. Samba Configuration to Use a Single LDAP Server">“Samba Configuration to Use a Single LDAP Server”</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="id2591394"></a> - <a class="indexterm" name="id2591404"></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): @@ -532,7 +532,7 @@ passdb backend = ldapsam:ldap://master.abmas.biz \ ldapsam:ldap://slave.abmas.biz ... </pre><p> - <a class="indexterm" name="id2591490"></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 @@ -543,7 +543,7 @@ passdb backend = ldapsam:ldap://master.abmas.biz \ 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="2000users.html#ch7dualok" title="Figure 6.5. Samba Configuration to Use Two LDAP Databases - The result is additive.">“Samba Configuration to Use Two LDAP Databases - The result is additive.”</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" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </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 master LDAP server as well as its own slave server, updates to the LDAP @@ -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">“Making Happy Users”</a>. The following steps permit the operation of a master/slave OpenLDAP arrangement. - </p><div class="procedure" title="Procedure 6.1. Implementation Steps for an LDAP Slave Server"><a name="id2591632"></a><p class="title"><b>Procedure 6.1. Implementation Steps for an LDAP Slave Server</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2591644"></a> - <a class="indexterm" name="id2591651"></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 @@ -567,11 +567,11 @@ passdb backend = ldapsam:ldap://master.abmas.biz \ </p><pre class="screen"> <code class="prompt">root# </code> service ldap stop </pre><p> - </p></li><li class="step" title="Step 2"><p> - <a class="indexterm" name="id2591696"></a> + </p></li><li><p> + <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="2000users.html#ch7-LDAP-master" title="Example 6.1. LDAP Master Server Configuration File /etc/openldap/slapd.conf">“LDAP Master Server Configuration File /etc/openldap/slapd.conf”</a>. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Create a file called <code class="filename">admin-accts.ldif</code> with the following contents: </p><pre class="screen"> dn: cn=updateuser,dc=abmas,dc=biz @@ -586,14 +586,14 @@ cn: sambaadmin sn: sambaadmin userPassword: buttercup </pre><p> - </p></li><li class="step" title="Step 4"><p> - Add an account called <span class="quote">“<span class="quote">updateuser</span>”</span> to the master LDAP server as shown here: + </p></li><li><p> + Add an account called “<span class="quote">updateuser</span>” to the master LDAP server as shown here: </p><pre class="screen"> <code class="prompt">root# </code> slapadd -v -l admin-accts.ldif </pre><p> - </p></li><li class="step" title="Step 5"><p> - <a class="indexterm" name="id2591769"></a> - <a class="indexterm" name="id2591776"></a> + </p></li><li><p> + <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: @@ -601,16 +601,16 @@ userPassword: buttercup <code class="prompt">root# </code> slapcat -v -l LDAP-transfer-LDIF.txt </pre><p> Each record is written to the file. - </p></li><li class="step" title="Step 6"><p> - <a class="indexterm" name="id2591808"></a> + </p></li><li><p> + <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 class="step" title="Step 7"><p> + </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="2000users.html#ch7-LDAP-slave" title="Example 6.2. LDAP Slave Configuration File /etc/openldap/slapd.conf">“LDAP Slave Configuration File /etc/openldap/slapd.conf”</a>. - </p></li><li class="step" title="Step 8"><p> + </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>). While in this directory, execute: @@ -640,7 +640,7 @@ added: "cn=Accounts,ou=Groups,dc=abmas,dc=biz" (00000011) added: "cn=Finances,ou=Groups,dc=abmas,dc=biz" (00000012) added: "cn=PIOps,ou=Groups,dc=abmas,dc=biz" (00000013) </pre><p> - </p></li><li class="step" title="Step 9"><p> + </p></li><li><p> Now start the LDAP server and set it to run automatically on system reboot by executing: </p><pre class="screen"> <code class="prompt">root# </code> rcldap start @@ -651,10 +651,10 @@ added: "cn=PIOps,ou=Groups,dc=abmas,dc=biz" (00000013) <code class="prompt">root# </code> service ldap start <code class="prompt">root# </code> chkconfig ldap on </pre><p> - </p></li><li class="step" title="Step 10"><p> - <a class="indexterm" name="id2591981"></a> - <a class="indexterm" name="id2591988"></a> - <a class="indexterm" name="id2591995"></a> + </p></li><li><p> + <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,16 +663,16 @@ 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="id2592040"></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 class="step" title="Step 11"><p> - <a class="indexterm" name="id2592061"></a> + </p></li><li><p> + <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">“Making Happy Users”</a>, execute: </p><pre class="screen"> <code class="prompt">root# </code> /var/lib/samba/sbin/smbldap-useradd -a fruitloop </pre><p> - </p></li><li class="step" title="Step 12"><p> + </p></li><li><p> On the slave LDAP server, change to the directory <code class="filename">/var/lib/ldap</code>. There should now be a file called <code class="filename">replogfile</code>. If replication worked as expected, the content of this file should be: @@ -696,10 +696,10 @@ replace: modifyTimestamp modifyTimestamp: 20031227004338Z - </pre><p> - </p></li><li class="step" title="Step 13"><p> + </p></li><li><p> Given that this first slave LDAP server is now working correctly, you may now implement additional slave LDAP servers as required. - </p></li><li class="step" title="Step 14"><p> + </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="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 @@ -791,72 +791,72 @@ 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 border="0" summary="Simple list" class="simplelist"><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="id2592324"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2592336"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2592348"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2592360"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2592372"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2592384"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2592395"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2592407"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2592419"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2592431"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2592443"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2592454"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2592466"></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="id2592479"></a><em class="parameter"><code>delete user script = /opt/IDEALX/sbin/smbldap-userdel '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2592491"></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="id2592504"></a><em class="parameter"><code>delete group script = /opt/IDEALX/sbin/smbldap-groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2592516"></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="id2592529"></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="id2592542"></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="id2592555"></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="id2592567"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2592580"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2592592"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2592604"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2592616"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2592627"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2592639"></a><em class="parameter"><code>domain master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2592651"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2592663"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2592674"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2592686"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2592698"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2592710"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2592722"></a><em class="parameter"><code>ldap admin dn = cn=sambaadmin,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2592735"></a><em class="parameter"><code>idmap backend = ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2592747"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2592759"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2592770"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td><a class="indexterm" name="id2592782"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[IPC$]</code></em></td></tr><tr><td><a class="indexterm" name="id2592828"></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="id2592848"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2592860"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2592872"></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="id2592892"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2592904"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2592916"></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="id2592936"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2592948"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2592960"></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="id2592980"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2592992"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2593004"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2593015"></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="id2593036"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2593047"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2593059"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2593071"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2593082"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2593128"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2593140"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2593151"></a><em class="parameter"><code>admin users = bjones</code></em></td></tr><tr><td><a class="indexterm" name="id2593163"></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="id2593183"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2593195"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2593207"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2593219"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2593231"></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="id2593251"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2593263"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2593275"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2593286"></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="id2593307"></a><em class="parameter"><code>comment = Profile Data Share</code></em></td></tr><tr><td><a class="indexterm" name="id2593319"></a><em class="parameter"><code>path = /var/lib/samba/profdata</code></em></td></tr><tr><td><a class="indexterm" name="id2593331"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2593342"></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="id2593363"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2593375"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2593387"></a><em class="parameter"><code>write list = root</code></em></td></tr><tr><td><a class="indexterm" name="id2593398"></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 border="0" summary="Simple list" class="simplelist"><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="id2593448"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2593459"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2593471"></a><em class="parameter"><code>netbios name = BLDG1</code></em></td></tr><tr><td><a class="indexterm" name="id2593483"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://lapdc.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2593495"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2593507"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2593519"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2593530"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2593542"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2593554"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2593565"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2593577"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2593589"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2593601"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2593613"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2593625"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2593637"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2593649"></a><em class="parameter"><code>os level = 63</code></em></td></tr><tr><td><a class="indexterm" name="id2593660"></a><em class="parameter"><code>domain master = No</code></em></td></tr><tr><td><a class="indexterm" name="id2593672"></a><em class="parameter"><code>wins server = 192.168.2.1</code></em></td></tr><tr><td><a class="indexterm" name="id2593684"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2593696"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2593708"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2593720"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2593732"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2593744"></a><em class="parameter"><code>ldap admin dn = cn=sambaadmin,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2593756"></a><em class="parameter"><code>utmp = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2593767"></a><em class="parameter"><code>idmap backend = ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2593779"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2593791"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2593803"></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="id2593823"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2593835"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2593847"></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="id2593867"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2593879"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2593891"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[pidata]</code></em></td></tr><tr><td><a class="indexterm" name="id2593937"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2593949"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2593960"></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="id2593980"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2593992"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2594004"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2594015"></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="id2594036"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2594048"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2594059"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2594071"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2594083"></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="id2594103"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2594115"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2594126"></a><em class="parameter"><code>admin users = bjones</code></em></td></tr><tr><td><a class="indexterm" name="id2594138"></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="id2594159"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2594171"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2594182"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2594194"></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="id2594215"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2594226"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2594238"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2594250"></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="id2594270"></a><em class="parameter"><code>comment = Profile Data Share</code></em></td></tr><tr><td><a class="indexterm" name="id2594282"></a><em class="parameter"><code>path = /var/lib/samba/profdata</code></em></td></tr><tr><td><a class="indexterm" name="id2594294"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2594306"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr></table></div></div><br class="example-break"><div class="sect2" title="Key Points Learned"><div class="titlepage"><div><div><h3 class="title"><a name="id2594319"></a>Key Points Learned</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> - <a class="indexterm" name="id2594330"></a><a class="indexterm" name="id2594335"></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 class="listitem"><p> - <a class="indexterm" name="id2594348"></a> + </p></li><li><p> + <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 class="listitem"><p> + </p></li><li><p> Network administration presents many complex challenges, most of which can be satisfied by good design but that also require sound communication and unification of management practices. This can be highly challenging in a large, globally distributed network. - </p></li><li class="listitem"><p> + </p></li><li><p> 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" title="Questions and Answers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2594466"></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" title="Frequently Asked Questions"><a name="id2594478"></a><dl><dt> <a href="2000users.html#id2594484"> + </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="2000users.html#id2594619"> + </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="2000users.html#id2594680"> + </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="2000users.html#id2594744"> + </a></dt><dt> <a href="2000users.html#id2588659"> Can Active Directory obtain account information from an OpenLDAP server? - </a></dt><dt> <a href="2000users.html#id2594779"> + </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="2000users.html#id2594928"> + </a></dt><dt> <a href="2000users.html#id2588842"> Can the My Documents folder be stored on a network drive? - </a></dt><dt> <a href="2000users.html#id2594976"> + </a></dt><dt> <a href="2000users.html#id2588890"> How much WAN bandwidth does WINS consume? - </a></dt><dt> <a href="2000users.html#id2595060"> + </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="2000users.html#id2595096"> + </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="2000users.html#id2595130"> + </a></dt><dt> <a href="2000users.html#id2589044"> Can I use NIS in place of LDAP? - </a></dt></dl><table border="0" width="100%" summary="Q and A Set"><col align="left" width="1%"><col><tbody><tr class="question"><td align="left" valign="top"><a name="id2594484"></a><a name="id2594486"></a></td><td align="left" valign="top"><p> - <a class="indexterm" name="id2594491"></a> - <a class="indexterm" name="id2594497"></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="id2594514"></a> - <a class="indexterm" name="id2594523"></a> - <a class="indexterm" name="id2594530"></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="id2594549"></a> - <a class="indexterm" name="id2594558"></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="id2594596"></a> - <a class="indexterm" name="id2594605"></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="id2594619"></a><a name="id2594621"></a></td><td align="left" valign="top"><p> - <a class="indexterm" name="id2594625"></a> - <a class="indexterm" name="id2594632"></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="id2594653"></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="id2594680"></a><a name="id2594682"></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="id2594694"></a> - <a class="indexterm" name="id2594701"></a> - <a class="indexterm" name="id2594710"></a> - <a class="indexterm" name="id2594716"></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,57 +904,57 @@ 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="id2594744"></a><a name="id2594746"></a></td><td align="left" valign="top"><p> - <a class="indexterm" name="id2594750"></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="id2594765"></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="id2594779"></a><a name="id2594781"></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="id2594792"></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 class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> Desktop folders such as <code class="constant">Desktop</code>, <code class="constant">My Documents</code>, <code class="constant">My Pictures</code>, <code class="constant">My Music</code>, <code class="constant">Internet Files</code>, <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">“Making Happy Users”</a>, <a class="link" href="happy.html#XP-screen001" title="Figure 5.3. Windows XP Professional User Shared Folders">“Windows XP Professional User Shared Folders”</a>. </p><p> - <a class="indexterm" name="id2594853"></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">“Configuration of Default Profile with Folder Redirection”</a> for more information regarding folder redirection. - </p></li><li class="listitem"><p> + </p></li><li><p> A static or rewritable portion that is typically only a few files (2-5 KB of information). - </p></li><li class="listitem"><p> - <a class="indexterm" name="id2594880"></a> - <a class="indexterm" name="id2594886"></a> + </p></li><li><p> + <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="id2594909"></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="id2594928"></a><a name="id2594930"></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="id2594945"></a> - <a class="indexterm" name="id2594952"></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">“Configuration of Default Profile with Folder Redirection”</a>. - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2594976"></a><a name="id2594978"></a></td><td align="left" valign="top"><p> - <a class="indexterm" name="id2594982"></a> - <a class="indexterm" name="id2594989"></a> - <a class="indexterm" name="id2594998"></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="id2595012"></a> - <a class="indexterm" name="id2595021"></a> - <a class="indexterm" name="id2595028"></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="id2595060"></a><a name="id2595062"></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="id2595096"></a><a name="id2595098"></a></td><td align="left" valign="top"><p> - <a class="indexterm" name="id2595102"></a><a class="indexterm" name="id2595108"></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="id2595130"></a><a name="id2595132"></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="id2595143"></a> - <a class="indexterm" name="id2595150"></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 68e6184d81..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.75.2"><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" title="Chapter 4. The 500-User Office"><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#id2571305">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2571350">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2571456">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2571492">Technical Issues</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2571695">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2571718">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#id2572445">Server Preparation: All Servers</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2573010">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#id2576210">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2576268">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">“Secure Office Networking”</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 @@ -6,9 +6,9 @@ </p><p> An analysis of the history of postings to the Samba mailing list easily demonstrates that the two most prevalent Samba problem areas are - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> Defective resolution of a NetBIOS name to its IP address - </p></li><li class="listitem"><p> + </p></li><li><p> Printing problems </p></li></ul></div><p> The exercises @@ -17,9 +17,9 @@ that same approach to printing, but <a class="link" href="happy.html" title="Chapter 5. Making Happy Users">“Making Happy Users”</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="id2571241"></a> - <a class="indexterm" name="id2571248"></a> - <a class="indexterm" name="id2571255"></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">“Secure Office Networking”</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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2571305"></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" title="Assignment Tasks"><div class="titlepage"><div><div><h3 class="title"><a name="id2571350"></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="id2571428"></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" title="Dissection and Discussion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2571456"></a>Dissection and Discussion</h2></div></div></div><p> - <a class="indexterm" name="id2571464"></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">“Making Happy Users”</a>). - </p><div class="sect2" title="Technical Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2571492"></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 class="itemizedlist" type="disc"><li class="listitem"><p> - <a class="indexterm" name="id2571513"></a> - <a class="indexterm" name="id2571520"></a> - <a class="indexterm" name="id2571527"></a> + </p><div class="itemizedlist"><ul type="disc"><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2571544"></a> - <a class="indexterm" name="id2571550"></a> + </p></li><li><p> + <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 @@ -151,63 +151,63 @@ memory but not yet written to disk will not be replicated, and (2) domain member machines periodically change the secret machine password. When this happens, there is no mechanism to return the changed password to the PDC. - </p></li><li class="listitem"><p> + </p></li><li><p> All domain user, group, and machine accounts are managed on the PDC. This makes for a simple mode of operation but has to be balanced with network performance and integrity of operations considerations. - </p></li><li class="listitem"><p> - <a class="indexterm" name="id2571591"></a> + </p></li><li><p> + <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 entries for the PDC are added to the <code class="filename">LMHOSTS</code>. This file is normally located on the Windows XP Professional client in the <code class="filename">C:\WINDOWS\SYSTEM32\ETC\DRIVERS</code> directory. - </p></li><li class="listitem"><p> + </p></li><li><p> 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 class="listitem"><p> - <a class="indexterm" name="id2571628"></a> + </p></li><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2571647"></a> - <a class="indexterm" name="id2571657"></a> + </p></li><li><p> + <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 all routers. The DHCP Relay agent must be programmed to pass DHCP Requests from the network directed at the backup DHCP server. - </p></li><li class="listitem"><p> + </p></li><li><p> All network users are granted the ability to print to any printer that is network-attached. All printers are available from each server. Print jobs that are spooled to a printer that is not on the local network segment are automatically routed to the print spooler that is in control of that printer. The specific details of how this might be done are demonstrated for one example only. - </p></li><li class="listitem"><p> + </p></li><li><p> 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" title="Political Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2571695"></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">“Making Happy Users”</a>. - </p></div></div><div class="sect1" title="Implementation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2571718"></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.">“Network Topology 500 User Network Using tdbsam passdb backend.”</a>. You have selected hardware that is appropriate to the task. - </p><div class="figure"><a name="chap05net"></a><p class="title"><b>Figure 4.1. Network Topology 500 User Network Using tdbsam passdb backend.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/chap5-net.png" width="270" alt="Network Topology 500 User Network Using tdbsam passdb backend."></div></div></div><br class="figure-break"><div class="sect2" title="Installation of DHCP, DNS, and Samba Control Files"><div class="titlepage"><div><div><h3 class="title"><a name="ch5-dnshcp-setup"></a>Installation of DHCP, DNS, and Samba Control Files</h3></div></div></div><p> + </p><div class="figure"><a name="chap05net"></a><p class="title"><b>Figure 4.1. Network Topology 500 User Network Using tdbsam passdb backend.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/chap5-net.png" width="270" alt="Network Topology 500 User Network Using tdbsam passdb backend."></div></div></div><br class="figure-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ch5-dnshcp-setup"></a>Installation of DHCP, DNS, and Samba Control Files</h3></div></div></div><p> Carefully install the configuration files into the correct locations as shown in <a class="link" href="Big500users.html#ch5-filelocations" title="Table 4.1. Domain: MEGANET, File Locations for Servers">“Domain: MEGANET, File Locations for Servers”</a>. You should validate that the full file path is correct as shown. </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">“Server: MASSIVE (PDC), File: /etc/samba/smb.conf”</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">“Server: MASSIVE (PDC), File: /etc/samba/dc-common.conf”</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">“Common Samba Configuration File: /etc/samba/common.conf”</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">“Server: BLDG1 (Member), File: smb.conf”</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">“Server: BLDG2 (Member), File: smb.conf”</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">“Common Domain Member Include File: dom-mem.conf”</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">“Server: MASSIVE, File: dhcpd.conf”</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">“Server: BLDG1, File: dhcpd.conf”</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">“Server: BLDG2, File: dhcpd.conf”</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">“Server: MASSIVE, File: named.conf, Part: A”</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">“Server: MASSIVE, File: named.conf, Part: B”</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">“Server: MASSIVE, File: named.conf, Part: C”</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">“Forward Zone File: abmas.biz.hosts”</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">“Forward Zone File: abmas.biz.hosts”</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">“Servers: BLDG1/BLDG2, File: named.conf, Part: A”</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">“Servers: BLDG1/BLDG2, File: named.conf, Part: B”</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">“DNS Localhost Forward Zone File: /var/lib/named/localhost.zone”</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">“DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone”</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">“DNS Root Name Server Hint File: /var/lib/named/root.hint”</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" title="Server Preparation: All Servers"><div class="titlepage"><div><div><h3 class="title"><a name="id2572445"></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">“Server: MASSIVE (PDC), File: /etc/samba/smb.conf”</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">“Server: MASSIVE (PDC), File: /etc/samba/dc-common.conf”</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">“Common Samba Configuration File: /etc/samba/common.conf”</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">“Server: BLDG1 (Member), File: smb.conf”</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">“Server: BLDG2 (Member), File: smb.conf”</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">“Common Domain Member Include File: dom-mem.conf”</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">“Server: MASSIVE, File: dhcpd.conf”</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">“Server: BLDG1, File: dhcpd.conf”</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">“Server: BLDG2, File: dhcpd.conf”</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">“Server: MASSIVE, File: named.conf, Part: A”</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">“Server: MASSIVE, File: named.conf, Part: B”</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">“Server: MASSIVE, File: named.conf, Part: C”</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">“Forward Zone File: abmas.biz.hosts”</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">“Forward Zone File: abmas.biz.hosts”</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">“Servers: BLDG1/BLDG2, File: named.conf, Part: A”</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">“Servers: BLDG1/BLDG2, File: named.conf, Part: B”</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">“DNS Localhost Forward Zone File: /var/lib/named/localhost.zone”</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">“DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone”</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">“DNS Root Name Server Hint File: /var/lib/named/root.hint”</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" title="Procedure 4.1. Server Preparation Steps"><a name="id2572456"></a><p class="title"><b>Procedure 4.1. Server Preparation Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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.">“Network Topology 500 User Network Using tdbsam passdb backend.”</a>. For SUSE Linux products, the tool that permits this is called <code class="literal">yast2</code>; for Red Hat Linux products, @@ -220,17 +220,17 @@ </p><pre class="screen"> <code class="prompt">root# </code> hostname -f </pre><p> - </p></li><li class="step" title="Step 2"><p> - <a class="indexterm" name="id2572520"></a> - <a class="indexterm" name="id2572527"></a> + </p></li><li><p> + <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 startup of the DNS server. You should check the startup order of your system. If the 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 class="step" title="Step 3"><p> - <a class="indexterm" name="id2572566"></a> + </p></li><li><p> + <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: @@ -240,9 +240,9 @@ nameserver 127.0.0.1 </pre><p> 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 class="step" title="Step 4"><p> - <a class="indexterm" name="id2572597"></a> - <a class="indexterm" name="id2572604"></a> + </p></li><li><p> + <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 @@ -254,9 +254,9 @@ Retype new SMB password: XXXXXXXX This account is essential in the regular maintenance of your Samba server. It must never be deleted. If for any reason the account is deleted, you may not be able to recreate this account without considerable trouble. - </p></li><li class="step" title="Step 5"><p> - <a class="indexterm" name="id2572650"></a> - <a class="indexterm" name="id2572656"></a> + </p></li><li><p> + <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: @@ -282,39 +282,39 @@ root = Administrator # End of File #### </pre><p> - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> Configure all network-attached printers to have a fixed IP address. - </p></li><li class="step" title="Step 7"><p> + </p></li><li><p> Create an entry in the DNS database on the server <code class="constant">MASSIVE</code> in both the forward lookup database for the zone <code class="constant">abmas.biz.hosts</code> and in the reverse lookup database for the network segment that the printer is located in. Example configuration files for similar zones were presented in <a class="link" href="secure.html" title="Chapter 3. Secure Office Networking">“Secure Office Networking”</a>, <a class="link" href="secure.html#abmasbiz" title="Example 3.14. DNS Abmas.biz Forward Zone File">“DNS Abmas.biz Forward Zone File”</a> and <a class="link" href="secure.html#eth2zone" title="Example 3.13. DNS 192.168.2 Reverse Zone File">“DNS 192.168.2 Reverse Zone File”</a>. - </p></li><li class="step" title="Step 8"><p> + </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. This allows the CUPS spooler to print using raw mode protocols. - <a class="indexterm" name="id2572748"></a> - <a class="indexterm" name="id2572755"></a> - </p></li><li class="step" title="Step 9"><p> - <a class="indexterm" name="id2572768"></a> + <a class="indexterm" name="id2566663"></a> + <a class="indexterm" name="id2566669"></a> + </p></li><li><p> + <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="id2572803"></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 the particular printer. - </p></li><li class="step" title="Step 10"><p> + </p></li><li><p> Print queues may not be enabled at creation. Make certain that the queues you have just created are enabled by executing the following: </p><pre class="screen"> <code class="prompt">root# </code> /usr/bin/enable <em class="parameter"><code>printque</code></em> </pre><p> - </p></li><li class="step" title="Step 11"><p> + </p></li><li><p> Even though your print queue may be enabled, it is still possible that it does not accept print jobs. A print queue services incoming printing requests only when configured to do so. Ensure that your print queue is @@ -322,10 +322,10 @@ root = Administrator </p><pre class="screen"> <code class="prompt">root# </code> /usr/bin/accept <em class="parameter"><code>printque</code></em> </pre><p> - </p></li><li class="step" title="Step 12"><p> - <a class="indexterm" name="id2572882"></a> - <a class="indexterm" name="id2572889"></a> - <a class="indexterm" name="id2572896"></a> + </p></li><li><p> + <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 @@ -335,41 +335,41 @@ root = Administrator </p><pre class="screen"> application/octet-stream application/vnd.cups-raw 0 - </pre><p> - </p></li><li class="step" title="Step 13"><p> - <a class="indexterm" name="id2572932"></a> + </p></li><li><p> + <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 </pre><p> - </p></li><li class="step" title="Step 14"><p> + </p></li><li><p> Refer to the CUPS printing manual for instructions regarding how to configure CUPS so that print queues that reside on CUPS servers on remote networks route print jobs to the print server that owns that queue. The default setting on your CUPS server may automatically discover remotely installed printers and may permit this functionality without requiring specific configuration. - </p></li><li class="step" title="Step 15"><p> + </p></li><li><p> As part of the roll-out program, you need to configure the application's server shares. This can be done once on the central server and may then be replicated using a tool such as <code class="literal">rsync</code>. Refer to the man page for <code class="literal">rsync</code> for details regarding use. The notes in <a class="link" href="secure.html#ch4appscfg" title="Application Share Configuration">“Application Share Configuration”</a> may help in your decisions to use an application server facility. - </p></li></ol></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p></li></ol></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Logon scripts that are run from a domain controller (PDC or BDC) are capable of using semi-intelligent 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" title="Server-Specific Preparation"><div class="titlepage"><div><div><h3 class="title"><a name="id2573010"></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" title="Configuration for Server: MASSIVE"><div class="titlepage"><div><div><h4 class="title"><a name="id2573023"></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" title="Procedure 4.2. Primary Domain Controller Preparation"><a name="id2573038"></a><p class="title"><b>Procedure 4.2. Primary Domain Controller Preparation</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2573050"></a> - <a class="indexterm" name="id2573057"></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: @@ -378,7 +378,7 @@ echo 1 > /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. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> This server is dual hosted (i.e., has two network interfaces) one goes to the Internet and the other to a local network that has a router that is the gateway to the remote networks. You must therefore configure the server with route table entries so that it can find machines @@ -396,46 +396,46 @@ echo 1 > /proc/sys/net/ipv4/ip_forward not persistent across system reboots. You may add these commands directly to the local 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 class="step" title="Step 3"><p> - <a class="indexterm" name="id2573151"></a> + </p></li><li><p> + <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: </p><pre class="screen"> hosts: files dns wins </pre><p> - </p></li><li class="step" title="Step 4"><p> - <a class="indexterm" name="id2573180"></a> + </p></li><li><p> + <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">“Initialize Groups Script, File: /etc/samba/initGrps.sh”</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 class="step" title="Step 5"><p> - <a class="indexterm" name="id2573212"></a> - <a class="indexterm" name="id2573219"></a> - <a class="indexterm" name="id2573228"></a> + </p></li><li><p> + <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="id2573255"></a> - <a class="indexterm" name="id2573262"></a> - <a class="indexterm" name="id2573268"></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. - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> Using the preferred tool for your UNIX system, add each user to the UNIX groups created previously as necessary. File system access control is based on UNIX group membership. - </p></li><li class="step" title="Step 7"><p> + </p></li><li><p> Create the directory mount point for the disk subsystem that is to be mounted to provide data storage for company files, in this case, the mount point indicated in the <code class="filename">smb.conf</code> 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 class="step" title="Step 8"><p> - <a class="indexterm" name="id2573332"></a> + </p></li><li><p> + <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} @@ -453,7 +453,7 @@ hosts: files dns wins The directory root of the <code class="literal">finsvcs</code> share is <code class="filename">/data/finsvcs</code>. The <code class="filename">/apps</code> directory is the root of the <code class="constant">apps</code> share that provides the application server infrastructure. - </p></li><li class="step" title="Step 9"><p> + </p></li><li><p> The <code class="filename">smb.conf</code> file specifies an infrastructure to support roaming profiles and network logon services. You can now create the file system infrastructure to provide the locations on disk that these services require. Adequate planning is essential @@ -474,9 +474,9 @@ hosts: files dns wins <code class="prompt">root# </code> chown 'username':users /var/lib/samba/profiles/'username' <code class="prompt">root# </code> chmod ug+wrx,o+rx,-w /var/lib/samba/profiles/'username' </pre><p> - </p></li><li class="step" title="Step 10"><p> - <a class="indexterm" name="id2573538"></a> - <a class="indexterm" name="id2573545"></a> + </p></li><li><p> + <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. @@ -491,7 +491,7 @@ net use h: /home <code class="prompt">root# </code> dos2unix < /var/lib/samba/netlogon/scripts/logon.bat.unix \ > /var/lib/samba/netlogon/scripts/logon.bat </pre><p> - </p></li><li class="step" title="Step 11"><p> + </p></li><li><p> There is one preparatory step without which you cannot have a working Samba network environment. You must add an account for each network user. You can do this by executing the following steps for each user: @@ -508,18 +508,18 @@ Retype new SMB password: XXXXXXXX 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 class="step" title="Step 12"><p> + </p></li><li><p> Follow the processes shown in <a class="link" href="Big500users.html#ch5-procstart" title="Process Startup Configuration">“Process Startup Configuration”</a> to start all services. - </p></li><li class="step" title="Step 13"><p> + </p></li><li><p> 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">“Configuration Specific to Domain Member Servers: BLDG1, BLDG2”</a> until after the operation of the server has been validated following the same methods as outlined in <a class="link" href="secure.html" title="Chapter 3. Secure Office Networking">“Secure Office Networking”</a>, <a class="link" href="secure.html#ch4valid" title="Validation">“Validation”</a>. - </p></li></ol></div></div><div class="sect3" title="Configuration Specific to Domain Member Servers: BLDG1, BLDG2"><div class="titlepage"><div><div><h4 class="title"><a name="ch5-domsvrspec"></a>Configuration Specific to Domain Member Servers: <code class="constant">BLDG1, BLDG2</code></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="ch5-domsvrspec"></a>Configuration Specific to Domain Member Servers: <code class="constant">BLDG1, BLDG2</code></h4></div></div></div><p> 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" title="Procedure 4.3. Backup Domain Controller Configuration Steps"><a name="id2573731"></a><p class="title"><b>Procedure 4.3. Backup Domain Controller Configuration Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2573743"></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: @@ -528,27 +528,27 @@ passwd: files winbind group: files winbind hosts: files dns wins </pre><p> - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Follow the steps outlined in <a class="link" href="Big500users.html#ch5-procstart" title="Process Startup Configuration">“Process Startup Configuration”</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 class="step" title="Step 3"><p> - <a class="indexterm" name="id2573795"></a> + </p></li><li><p> + <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 class="step" title="Step 4"><p> - <a class="indexterm" name="id2573827"></a> + </p></li><li><p> + <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 </pre><p> - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> 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">“Configuration Specific to Domain Member Servers: BLDG1, BLDG2”</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">“Validation”</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 border="0" summary="Simple list" class="simplelist"><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="id2573912"></a><em class="parameter"><code>workgroup = MEGANET</code></em></td></tr><tr><td><a class="indexterm" name="id2573924"></a><em class="parameter"><code>netbios name = MASSIVE</code></em></td></tr><tr><td><a class="indexterm" name="id2573936"></a><em class="parameter"><code>interfaces = eth1, lo</code></em></td></tr><tr><td><a class="indexterm" name="id2573948"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2573960"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id2573971"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2573983"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2573995"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2574007"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2574020"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2574032"></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="id2574044"></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="id2574057"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2574069"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2574081"></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="id2574102"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2574113"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2574125"></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="id2574146"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2574157"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2574169"></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="id2574190"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2574202"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2574213"></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 border="0" summary="Simple list" class="simplelist"><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="id2574261"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2574273"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2574285"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2574297"></a><em class="parameter"><code>logon path = \%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2574309"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2574321"></a><em class="parameter"><code>logon home = \%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2574332"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2574344"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2574356"></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="id2574377"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2574389"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2574400"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2574412"></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="id2574432"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2574444"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2574456"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2574468"></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="id2574488"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2574500"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2574512"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2574523"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2574568"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2574580"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2574591"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2574603"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2574614"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2574626"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2574638"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2574650"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2574662"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2574673"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2574686"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2574698"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2574710"></a><em class="parameter"><code>utmp = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2574722"></a><em class="parameter"><code>map acl inherit = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2574734"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2574745"></a><em class="parameter"><code>veto files = /*.eml/*.nws/*.{*}/</code></em></td></tr><tr><td><a class="indexterm" name="id2574757"></a><em class="parameter"><code>veto oplock files = /*.doc/*.xls/*.mdb/</code></em></td></tr><tr><td><a class="indexterm" name="id2574769"></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="id2574794"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2574806"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2574817"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2574829"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2574840"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2574852"></a><em class="parameter"><code>default devmode = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2574864"></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="id2574885"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2574896"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2574908"></a><em class="parameter"><code>admin users = bjordan</code></em></td></tr><tr><td><a class="indexterm" name="id2574920"></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 border="0" summary="Simple list" class="simplelist"><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="id2574963"></a><em class="parameter"><code>workgroup = MEGANET</code></em></td></tr><tr><td><a class="indexterm" name="id2574974"></a><em class="parameter"><code>netbios name = BLDG1</code></em></td></tr><tr><td><a class="indexterm" name="id2574986"></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 border="0" summary="Simple list" class="simplelist"><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="id2575029"></a><em class="parameter"><code>workgroup = MEGANET</code></em></td></tr><tr><td><a class="indexterm" name="id2575041"></a><em class="parameter"><code>netbios name = BLDG2</code></em></td></tr><tr><td><a class="indexterm" name="id2575053"></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 border="0" summary="Simple list" class="simplelist"><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="id2575096"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2575108"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2575120"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575132"></a><em class="parameter"><code>wins server = 172.16.0.1</code></em></td></tr><tr><td><a class="indexterm" name="id2575144"></a><em class="parameter"><code>idmap uid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2575156"></a><em class="parameter"><code>idmap gid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2575168"></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; @@ -897,9 +897,9 @@ net groupmap add ntgroup="Domain Guests" unixgroup=nobody type=d 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" title="Process Startup Configuration"><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="id2575523"></a> - <a class="indexterm" name="id2575530"></a> +</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="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="id2575566"></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" title="Procedure 4.4. Process Startup Configuration Steps"><a name="id2575610"></a><p class="title"><b>Procedure 4.4. Process Startup Configuration Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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="id2575625"></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 @@ -929,10 +929,10 @@ net groupmap add ntgroup="Insurance Group" unixgroup=piops type=d <code class="prompt">root# </code> chkconfig smb on <code class="prompt">root# </code> chkconfig swat on </pre><p> - </p></li><li class="step" title="Step 2"><p> - <a class="indexterm" name="id2575674"></a> - <a class="indexterm" name="id2575681"></a> - <a class="indexterm" name="id2575688"></a> + </p></li><li><p> + <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: @@ -943,70 +943,70 @@ net groupmap add ntgroup="Insurance Group" unixgroup=piops type=d <code class="prompt">root# </code> service smb restart <code class="prompt">root# </code> service swat restart </pre><p> - </p></li></ol></div></div><div class="sect2" title="Windows Client Configuration"><div class="titlepage"><div><div><h3 class="title"><a name="ch5wincfg"></a>Windows Client Configuration</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="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" title="Procedure 4.5. Windows Client Configuration Steps"><a name="id2575754"></a><p class="title"><b>Procedure 4.5. Windows Client Configuration Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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="id2575768"></a> - <a class="indexterm" name="id2575775"></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 class="step" title="Step 2"><p> + </p></li><li><p> Join the Windows domain <code class="constant">MEGANET</code>. Use the domain administrator username <code class="constant">root</code> and the SMB password you assigned to this account. A detailed step-by-step procedure for joining a Windows 200x/XP Professional client to a Windows domain is given in <a class="link" href="appendix.html" title="Chapter 15. A Collection of Useful Tidbits">“A Collection of Useful Tidbits”</a>, <a class="link" href="appendix.html#domjoin" title="Joining a Domain: Windows 200x/XP Professional">“Joining a Domain: Windows 200x/XP Professional”</a>. Reboot the machine as prompted and then log on using the domain administrator account (<code class="constant">root</code>). - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Verify that the server called <code class="constant">MEGANET</code> is visible in <span class="guimenu">My Network Places</span>, that it is possible to connect to it and see the shares <span class="guimenuitem">accounts</span>, <span class="guimenuitem">apps</span>, and <span class="guimenuitem">finsvcs</span>, and that it is possible to open each share to reveal its contents. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Create a drive mapping to the <code class="constant">apps</code> share on a server. At this time, it does not particularly matter which application server is used. It is necessary to manually set a persistent drive mapping to the local applications server on each workstation at the time of installation. This step is avoided by the improvements to the design of the network configuration in the next chapter. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> Perform an administrative installation of each application to be used. Select the options that you wish to use. Of course, you choose to run applications over the network, correct? - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> Now install all applications to be installed locally. Typical tools include Adobe Acrobat, NTP-based time synchronization software, drivers for specific local devices such as fingerprint scanners, and the like. Probably the most significant application to be locally installed is antivirus software. - </p></li><li class="step" title="Step 7"><p> + </p></li><li><p> Now install all four printers onto the staging system. The printers you install 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" title="Procedure 4.6. Steps to Install Printer Drivers on Windows Clients"><a name="id2575906"></a><p class="title"><b>Procedure 4.6. Steps to Install Printer Drivers on Windows Clients</b></p><ol class="procedure" type="1"><li class="step" title="Step 7.1"><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> → <span class="guimenuitem">Settings</span> → <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 class="step" title="Step 7.2"><p> + </p></li><li><p> Click <span class="guibutton">Next</span>. In the <span class="guimenuitem">Manufacturer:</span> panel, select <code class="constant">HP</code>. In the <span class="guimenuitem">Printers:</span> panel, select the printer called <code class="constant">HP LaserJet 6</code>. Click <span class="guibutton">Next</span>. - </p></li><li class="step" title="Step 7.3"><p> + </p></li><li><p> In the <span class="guimenuitem">Available ports:</span> panel, select <code class="constant">FILE:</code>. Accept the default printer name by clicking - <span class="guibutton">Next</span>. When asked, <span class="quote">“<span class="quote">Would you like to print a - test page?</span>”</span>, click <span class="guimenuitem">No</span>. Click + <span class="guibutton">Next</span>. When asked, “<span class="quote">Would you like to print a + test page?</span>”, click <span class="guimenuitem">No</span>. Click <span class="guibutton">Finish</span>. - </p></li><li class="step" title="Step 7.4"><p> + </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> → <span class="guimenuitem">Properties</span>. - </p></li><li class="step" title="Step 7.5"><p> + </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>. Click <span class="guibutton">OK</span>+<span class="guibutton">OK</span> to complete the installation. - </p></li><li class="step" title="Step 7.6"><p> + </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. Remember to install all printers but to set the destination port for each to the server on the @@ -1018,69 +1018,69 @@ net groupmap add ntgroup="Insurance Group" unixgroup=piops type=d 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><p> - </p></li><li class="step" title="Step 8"><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 defragmentation tool so that the file system is in optimal condition before replication. - </p></li><li class="step" title="Step 9"><p> + </p></li><li><p> Boot the workstation using the Norton (Symantec) Ghosting disk (or CD-ROM) and image the machine to a network share on the server. - </p></li><li class="step" title="Step 10"><p> + </p></li><li><p> You may now replicate the image using the appropriate Norton Ghost procedure to the target machines. Make sure to use the procedure that ensures each machine has a unique Windows security identifier (SID). When the installation of the disk image is complete, boot the PC. - </p></li><li class="step" title="Step 11"><p> + </p></li><li><p> Log onto the machine as the local Administrator (the only option), and join the machine to the domain following the procedure set out in <a class="link" href="appendix.html" title="Chapter 15. A Collection of Useful Tidbits">“A Collection of Useful Tidbits”</a>, <a class="link" href="appendix.html#domjoin" title="Joining a Domain: Windows 200x/XP Professional">“Joining a Domain: Windows 200x/XP Professional”</a>. You must now set the persistent drive mapping to the applications server that the user is to use. The system is now ready for the user to log on, provided you have created a network logon account for that user, of course. - </p></li><li class="step" title="Step 12"><p> + </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" title="Key Points Learned"><div class="titlepage"><div><div><h3 class="title"><a name="id2576210"></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">“Making Happy Users”</a> bring the network to life. The following key learning points were experienced: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> The power of using <code class="filename">smb.conf</code> include files - </p></li><li class="listitem"><p> + </p></li><li><p> Use of a single PDC over a routed network - </p></li><li class="listitem"><p> + </p></li><li><p> Joining a Samba-3 domain member server to a Samba-3 domain - </p></li><li class="listitem"><p> + </p></li><li><p> Configuration of winbind to use domain users and groups for Samba access to resources on the domain member servers - </p></li><li class="listitem"><p> + </p></li><li><p> The introduction of roaming profiles - </p></li></ul></div></div></div><div class="sect1" title="Questions and Answers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2576268"></a>Questions and Answers</h2></div></div></div><p> - </p><div class="qandaset" title="Frequently Asked Questions"><a name="id2576277"></a><dl><dt> <a href="Big500users.html#id2576284"> + </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#id2576333"> + </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#id2576396"> + </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#id2576451"> + </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#id2576481"> + </a></dt><dt> <a href="Big500users.html#id2570396"> How does the Windows client find the PDC? - </a></dt><dt> <a href="Big500users.html#id2576504"> + </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#id2576534"> + </a></dt><dt> <a href="Big500users.html#id2570449"> You did nothing special to implement roaming profiles. Why? - </a></dt><dt> <a href="Big500users.html#id2576554"> + </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#id2576586"> + </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#id2576627"> + </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" width="100%" summary="Q and A Set"><col align="left" width="1%"><col><tbody><tr class="question"><td align="left" valign="top"><a name="id2576284"></a><a name="id2576286"></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> @@ -1088,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="id2576333"></a><a name="id2576335"></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 @@ -1101,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="id2576396"></a><a name="id2576398"></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! @@ -1111,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="id2576451"></a><a name="id2576453"></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 @@ -1120,26 +1120,26 @@ net groupmap add ntgroup="Insurance Group" unixgroup=piops type=d </p><p> The only exception to this rule is when the client makes a directed request from a specific DHCP server for renewal of the lease it has. This means that under normal circumstances there is no risk of a clash. - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2576481"></a><a name="id2576483"></a></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570396"></a><a name="id2570398"></a></td><td align="left" valign="top"><p> How does the Windows client find the PDC? </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p> The Windows client obtains the WINS server address from the DHCP lease information. It also 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="id2576504"></a><a name="id2576506"></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="id2576534"></a><a name="id2576536"></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 clients is to use roaming profiles. - </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2576554"></a><a name="id2576556"></a></td><td align="left" valign="top"><p> + </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570469"></a><a name="id2570471"></a></td><td align="left" valign="top"><p> On the domain member computers, you configured winbind in the <code class="filename">/etc/nsswitch.conf</code> file. You did not configure any PAM settings. Is this an omission? </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p> @@ -1148,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="id2576586"></a><a name="id2576588"></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 @@ -1157,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="id2576627"></a><a name="id2576629"></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 eb0500d887..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.75.2"><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" title="Part II. Domain Members, Updating Samba and Migration"><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" title="Domain Members, Updating Samba and Migration"><div><div><div><h1 class="title"><a name="id2595183"></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#id2595324">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2595378">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2595413">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2595441">Technical Issues</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596090">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2596190">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#id2602396">UNIX/Linux Client Domain Member</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2602971">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2603025">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#id2604185">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2604281">Cautions and Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2605610">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#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2606312">Samba-2.x with LDAP Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2606494">Updating a Samba-3 Installation</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2606604">Samba-3 to Samba-3 Updates on the Same Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2606808">Migrating Samba-3 to a New Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2607222">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#id2607394">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2607479">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2607534">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2607720">Technical Issues</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2608043">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2608069">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2610669">NT4 Migration Using tdbsam Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2611075">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2611114">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#id2612089">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2612206">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2612318">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2612395">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2612585">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2612594">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> +</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 7aa0ce0457..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.75.2"><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" title="Chapter 12. Integrating Additional Services"><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#id2622230">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2622261">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2622372">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2622405">Technical Issues</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2622561">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2622578">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#id2624430">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2624491">Questions and Answers</a></span></dt></dl></div><p> - <a class="indexterm" name="id2622181"></a> - <a class="indexterm" name="id2622187"></a> - <a class="indexterm" name="id2622194"></a> - <a class="indexterm" name="id2622201"></a> - <a class="indexterm" name="id2622208"></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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622230"></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" title="Assignment Tasks"><div class="titlepage"><div><div><h3 class="title"><a name="id2622261"></a>Assignment Tasks</h3></div></div></div><p> - <a class="indexterm" name="id2622269"></a> - <a class="indexterm" name="id2622278"></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="id2622296"></a> - <a class="indexterm" name="id2622303"></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="id2622334"></a> - <a class="indexterm" name="id2622341"></a> - <a class="indexterm" name="id2622348"></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,30 +63,30 @@ </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" title="Dissection and Discussion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622372"></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: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> Internet access for most employees - </p></li><li class="listitem"><p> + </p></li><li><p> Distributed system to accommodate load and geographical distribution of users - </p></li><li class="listitem"><p> + </p></li><li><p> Seamless and transparent interoperability with the existing Active Directory domain - </p></li></ul></div><div class="sect2" title="Technical Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2622405"></a>Technical Issues</h3></div></div></div><p> - <a class="indexterm" name="id2622413"></a> - <a class="indexterm" name="id2622419"></a> - <a class="indexterm" name="id2622426"></a> - <a class="indexterm" name="id2622433"></a> - <a class="indexterm" name="id2622440"></a> - <a class="indexterm" name="id2622447"></a> - <a class="indexterm" name="id2622454"></a> - <a class="indexterm" name="id2622460"></a> - <a class="indexterm" name="id2622468"></a> - <a class="indexterm" name="id2622474"></a> - <a class="indexterm" name="id2622481"></a> - <a class="indexterm" name="id2622488"></a> - <a class="indexterm" name="id2622498"></a><a class="indexterm" name="id2622503"></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 @@ -99,79 +99,79 @@ This process is entirely transparent and seamless to the user. </p><p> Enabling this consists of: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> Preparing the necessary environment using preconfigured packages - </p></li><li class="listitem"><p> + </p></li><li><p> Setting up raw Kerberos authentication against the Active Directory domain - </p></li><li class="listitem"><p> + </p></li><li><p> Configuring, compiling, and then installing the supporting Samba-3 components - </p></li><li class="listitem"><p> + </p></li><li><p> Tying it all together - </p></li></ul></div></div><div class="sect2" title="Political Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2622561"></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" title="Implementation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622578"></a>Implementation</h2></div></div></div><p> - <a class="indexterm" name="id2622586"></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="id2622603"></a> + <a class="indexterm" name="id2616518"></a> The following packages should be available on your Red Hat Linux system: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> - <a class="indexterm" name="id2622618"></a> - <a class="indexterm" name="id2622625"></a> + </p><div class="itemizedlist"><ul type="disc"><li><p> + <a class="indexterm" name="id2616533"></a> + <a class="indexterm" name="id2616540"></a> krb5-libs - </p></li><li class="listitem"><p> + </p></li><li><p> krb5-devel - </p></li><li class="listitem"><p> + </p></li><li><p> krb5-workstation - </p></li><li class="listitem"><p> + </p></li><li><p> krb5-server - </p></li><li class="listitem"><p> + </p></li><li><p> pam_krb5 </p></li></ul></div><p> - <a class="indexterm" name="id2622655"></a> + <a class="indexterm" name="id2616570"></a> In the case of SUSE Linux, these packages are called: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> heimdal-lib - </p></li><li class="listitem"><p> + </p></li><li><p> heimdal-devel - </p></li><li class="listitem"><p> - <a class="indexterm" name="id2622680"></a> + </p></li><li><p> + <a class="indexterm" name="id2616595"></a> heimdal - </p></li><li class="listitem"><p> + </p></li><li><p> pam_krb5 </p></li></ul></div><p> If the required packages are not present on your system, you must install 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" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - <a class="indexterm" name="id2622705"></a> - <a class="indexterm" name="id2622712"></a> - <a class="indexterm" name="id2622719"></a> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + <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="id2622733"></a> - <a class="indexterm" name="id2622739"></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" title="Removal of Pre-Existing Conflicting RPMs"><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="id2622762"></a> + </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="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="id2622774"></a> - <a class="indexterm" name="id2622781"></a> - <a class="indexterm" name="id2622787"></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" title="Kerberos Configuration"><div class="titlepage"><div><div><h3 class="title"><a name="id2622828"></a>Kerberos Configuration</h3></div></div></div><p> - <a class="indexterm" name="id2622836"></a> - <a class="indexterm" name="id2622842"></a> - <a class="indexterm" name="id2622852"></a> - <a class="indexterm" name="id2622858"></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="id2622877"></a> - <a class="indexterm" name="id2622884"></a> - <a class="indexterm" name="id2622891"></a> - <a class="indexterm" name="id2622898"></a> - <a class="indexterm" name="id2622904"></a> - <a class="indexterm" name="id2622913"></a> - <a class="indexterm" name="id2622920"></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,30 +207,30 @@ 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" title="Procedure 12.1. Kerberos Configuration Steps"><a name="id2622954"></a><p class="title"><b>Procedure 12.1. Kerberos Configuration Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2622966"></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">“Kerberos Configuration File: /etc/krb5.conf”</a>. The final fully qualified path for this file should be <code class="filename">/etc/krb5.conf</code>. - </p></li><li class="step" title="Step 2"><p> - <a class="indexterm" name="id2623000"></a> - <a class="indexterm" name="id2623007"></a> - <a class="indexterm" name="id2623014"></a> - <a class="indexterm" name="id2623021"></a> - <a class="indexterm" name="id2623028"></a> - <a class="indexterm" name="id2623034"></a> - <a class="indexterm" name="id2623041"></a> - <a class="indexterm" name="id2623048"></a> - <a class="indexterm" name="id2623055"></a> - <a class="indexterm" name="id2623064"></a> - <a class="indexterm" name="id2623071"></a> - <a class="indexterm" name="id2623078"></a> - <a class="indexterm" name="id2623085"></a> + </p></li><li><p> + <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: <span class="quote">“<span class="quote">Cannot find KDC for requested realm while getting - initial credentials</span>”</span>. Kerberos is picky about time synchronization. The time + be in UPPERCASE, or you will get an error: “<span class="quote">Cannot find KDC for requested realm while getting + initial credentials</span>”. Kerberos is picky about time synchronization. The time according to your participating servers must be within 5 minutes or you get an error: - <span class="quote">“<span class="quote">kinit(v5): Clock skew too great while getting initial credentials</span>”</span>. + “<span class="quote">kinit(v5): Clock skew too great while getting initial credentials</span>”. Clock skew limits are, in fact, configurable in the Kerberos protocols (the default is 5 minutes). A better solution is to implement NTP throughout your server network. Kerberos needs to be able to do a reverse DNS lookup on the IP address of your KDC. @@ -240,8 +240,8 @@ <code class="filename">/etc/hosts</code> entry mapping the IP address of your KDC to its 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 class="step" title="Step 3"><p> - <a class="indexterm" name="id2623129"></a> + </p></li><li><p> + <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,57 +261,57 @@ 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="id2623194"></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" title="Samba Configuration"><div class="titlepage"><div><div><h4 class="title"><a name="id2623217"></a>Samba Configuration</h4></div></div></div><p> - <a class="indexterm" name="id2623225"></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" title="Procedure 12.2. Securing Samba-3 With ADS Support Steps"><a name="id2623235"></a><p class="title"><b>Procedure 12.2. Securing Samba-3 With ADS Support Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2623247"></a> - <a class="indexterm" name="id2623254"></a> - <a class="indexterm" name="id2623261"></a> - <a class="indexterm" name="id2623268"></a> - <a class="indexterm" name="id2623275"></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="id2623301"></a> - <a class="indexterm" name="id2623308"></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 <code class="literal">ntlm_auth</code> tool, and are statically linked against suitably patched Heimdal 0.6 libraries. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> 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">“Samba Configuration File: /etc/samba/smb.conf”</a>. - </p></li><li class="step" title="Step 3"><p> - <a class="indexterm" name="id2623359"></a> - <a class="indexterm" name="id2623366"></a> - <a class="indexterm" name="id2623373"></a>i - <a class="indexterm" name="id2623384"></a> - <a class="indexterm" name="id2623391"></a> + </p></li><li><p> + <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. - This is done with the <span class="quote">“<span class="quote">net ads join -U [Administrator%Password]</span>”</span> + This is done with the “<span class="quote">net ads join -U [Administrator%Password]</span>” command, as follows: </p><pre class="screen"> <code class="prompt">root# </code> net ads join -U administrator%vulcon </pre><p> - </p></li><li class="step" title="Step 4"><p> - <a class="indexterm" name="id2623425"></a> - <a class="indexterm" name="id2623432"></a> - <a class="indexterm" name="id2623439"></a> - <a class="indexterm" name="id2623446"></a> - <a class="indexterm" name="id2623452"></a> + </p></li><li><p> + <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"> @@ -319,12 +319,12 @@ Password for ADMINISTRATOR@LONDON.ABMAS.BIZ: <code class="prompt">root# </code> nmbd -D <code class="prompt">root# </code> winbindd -D </pre><p> - </p></li><li class="step" title="Step 5"><p> - <a class="indexterm" name="id2623493"></a> - <a class="indexterm" name="id2623500"></a> - <a class="indexterm" name="id2623509"></a> - <a class="indexterm" name="id2623516"></a> - <a class="indexterm" name="id2623523"></a> + </p></li><li><p> + <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: @@ -356,9 +356,9 @@ LONDON+Group Policy Creator Owners LONDON+DnsUpdateProxy </pre><p> This enumerates all the groups in your Active Directory tree. - </p></li><li class="step" title="Step 6"><p> - <a class="indexterm" name="id2623587"></a> - <a class="indexterm" name="id2623594"></a> + </p></li><li><p> + <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"> @@ -369,20 +369,20 @@ password: XXXXXXXX </p><pre class="screen"> <code class="prompt">root# </code> NT_STATUS_OK: Success (0x0) </pre><p> - </p></li><li class="step" title="Step 7"><p> - <a class="indexterm" name="id2623646"></a> - <a class="indexterm" name="id2623653"></a> - <a class="indexterm" name="id2623660"></a> - <a class="indexterm" name="id2623667"></a> - <a class="indexterm" name="id2623674"></a> - <a class="indexterm" name="id2623680"></a> - <a class="indexterm" name="id2623687"></a> - <a class="indexterm" name="id2623694"></a> + </p></li><li><p> + <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 - <span class="quote">“<span class="quote">root</span>”</span>, authenticates against your Active Directory domain (with + “<span class="quote">root</span>”, authenticates against your Active Directory domain (with the aid of winbind). It manages this by reading from the winbind privileged pipe. - Squid is running with the permissions of user <span class="quote">“<span class="quote">squid</span>”</span> and group - <span class="quote">“<span class="quote">squid</span>”</span> and is not able to do this unless we make a vital change. + Squid is running with the permissions of user “<span class="quote">squid</span>” and group + “<span class="quote">squid</span>” and is not able to do this unless we make a vital change. Squid cannot read from the winbind privilege pipe unless you change the permissions of its directory. This is the single biggest cause of failure in the whole process. Remember to issue the following command (for Red Hat Linux): @@ -395,77 +395,77 @@ 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" title="NSS Configuration"><div class="titlepage"><div><div><h4 class="title"><a name="id2623769"></a>NSS Configuration</h4></div></div></div><p> - <a class="indexterm" name="id2623777"></a> - <a class="indexterm" name="id2623783"></a> - <a class="indexterm" name="id2623790"></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">“NSS Configuration File Extract File: /etc/nsswitch.conf”</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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2623848"></a><em class="parameter"><code>workgroup = LONDON</code></em></td></tr><tr><td><a class="indexterm" name="id2623860"></a><em class="parameter"><code>netbios name = W2K3S</code></em></td></tr><tr><td><a class="indexterm" name="id2623872"></a><em class="parameter"><code>realm = LONDON.ABMAS.BIZ</code></em></td></tr><tr><td><a class="indexterm" name="id2623884"></a><em class="parameter"><code>security = ads</code></em></td></tr><tr><td><a class="indexterm" name="id2623895"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623907"></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="id2623924"></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="id2623940"></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="id2623956"></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="id2623971"></a><em class="parameter"><code>winbind enum users = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623983"></a><em class="parameter"><code>winbind enum groups = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623995"></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" title="Squid Configuration"><div class="titlepage"><div><div><h4 class="title"><a name="id2624034"></a>Squid Configuration</h4></div></div></div><p> - <a class="indexterm" name="id2624042"></a> - <a class="indexterm" name="id2624049"></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" title="Configuration"><div class="titlepage"><div><div><h3 class="title"><a name="id2624064"></a>Configuration</h3></div></div></div></div><div class="procedure" title="Procedure 12.3. Squid Configuration Steps"><a name="id2624069"></a><p class="title"><b>Procedure 12.3. Squid Configuration Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2624081"></a> - <a class="indexterm" name="id2624088"></a> - <a class="indexterm" name="id2624095"></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 class="step" title="Step 2"><p> - <a class="indexterm" name="id2624113"></a> - <a class="indexterm" name="id2624119"></a> - <a class="indexterm" name="id2624126"></a> - <a class="indexterm" name="id2624133"></a> - <a class="indexterm" name="id2624140"></a> + </p></li><li><p> + <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 Red Hat squid rpms were installed, they will be). Set up a <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 class="step" title="Step 3"><p> - <a class="indexterm" name="id2624187"></a> - <a class="indexterm" name="id2624194"></a> + </p></li><li><p> + <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 class="step" title="Step 4"><p> - <a class="indexterm" name="id2624225"></a> - <a class="indexterm" name="id2624232"></a> + </p></li><li><p> + <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 <code class="prompt">root# </code> chmod 770 /var/log/squid </pre><p> - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> Finally, Squid must be able to write to its disk cache! Enter the following commands: </p><pre class="screen"> <code class="prompt">root# </code> chown -R chown squid:squid /var/cache/squid <code class="prompt">root# </code> chmod 770 /var/cache/squid </pre><p> - </p></li><li class="step" title="Step 6"><p> - <a class="indexterm" name="id2624292"></a> + </p></li><li><p> + <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]">“Squid Configuration File Extract /etc/squid.conf [ADMINISTRATIVE PARAMETERS Section]”</a> and <a class="link" href="DomApps.html#etcsquid2" title="Example 12.5. Squid Configuration File extract File: /etc/squid.conf [AUTHENTICATION PARAMETERS Section]">“Squid Configuration File extract File: /etc/squid.conf [AUTHENTICATION PARAMETERS Section]”</a>. - </p></li><li class="step" title="Step 7"><p> - <a class="indexterm" name="id2624326"></a> + </p></li><li><p> + <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 </pre><p> - </p></li><li class="step" title="Step 8"><p> + </p></li><li><p> Finally, start Squid and enjoy transparent Active Directory authentication. Enter the following command: </p><pre class="screen"> @@ -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" title="Key Points Learned"><div class="titlepage"><div><div><h3 class="title"><a name="id2624430"></a>Key Points Learned</h3></div></div></div><p> - <a class="indexterm" name="id2624438"></a> - <a class="indexterm" name="id2624445"></a> - <a class="indexterm" name="id2624452"></a> - <a class="indexterm" name="id2624459"></a> - <a class="indexterm" name="id2624471"></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" title="Questions and Answers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2624491"></a>Questions and Answers</h2></div></div></div><p> - <a class="indexterm" name="id2624499"></a> - <a class="indexterm" name="id2624506"></a> - <a class="indexterm" name="id2624513"></a> - <a class="indexterm" name="id2624520"></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 @@ -515,41 +515,41 @@ group: files winbind wishes to remain anonymous, the sustained transaction load on this server hovers around 140 hits/sec. The following comments were made with respect to questions regarding the performance of this installation: </p><div class="blockquote"><blockquote class="blockquote"><p> - [In our] EXTREMELY optimized environment . . . [the] performance impact is almost [nothing]. The <span class="quote">“<span class="quote">almost</span>”</span> + [In our] EXTREMELY optimized environment . . . [the] performance impact is almost [nothing]. The “<span class="quote">almost</span>” part is due to the brain damage of the ntlm-over-http protocol definition. Suffice to say that its worst-case scenario triples the number of hits needed to perform the same transactions versus basic or digest auth[entication]. </p></blockquote></div><p> 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" title="Frequently Asked Questions"><a name="id2624598"></a><dl><dt> <a href="DomApps.html#id2624605"> + </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#id2624771"> + </a></dt><dt> <a href="DomApps.html#id2618686"> What other services does Samba provide? - </a></dt><dt> <a href="DomApps.html#id2624914"> + </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" width="100%" summary="Q and A Set"><col align="left" width="1%"><col><tbody><tr class="question"><td align="left" valign="top"><a name="id2624605"></a><a name="id2624607"></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="id2624619"></a> - <a class="indexterm" name="id2624626"></a> - <a class="indexterm" name="id2624633"></a> - <a class="indexterm" name="id2624642"></a> - <a class="indexterm" name="id2624649"></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="id2624671"></a> - <a class="indexterm" name="id2624678"></a> - <a class="indexterm" name="id2624687"></a> - <a class="indexterm" name="id2624696"></a> - <a class="indexterm" name="id2624705"></a> - <a class="indexterm" name="id2624712"></a> - <a class="indexterm" name="id2624719"></a> - <a class="indexterm" name="id2624726"></a> - <a class="indexterm" name="id2624733"></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="id2624757"></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="id2624771"></a><a name="id2624773"></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="id2624784"></a> - <a class="indexterm" name="id2624791"></a> - <a class="indexterm" name="id2624798"></a> - <a class="indexterm" name="id2624805"></a> - <a class="indexterm" name="id2624812"></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="id2624842"></a> - <a class="indexterm" name="id2624849"></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="id2624867"></a> - <a class="indexterm" name="id2624873"></a> - <a class="indexterm" name="id2624880"></a> - <a class="indexterm" name="id2624887"></a> - <a class="indexterm" name="id2624894"></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="id2624914"></a><a name="id2624916"></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 2773fbf621..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.75.2"><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" title="Part I. Example Network Configurations"><div class="titlepage"><div><div><h1 class="title"><a name="ExNetworks"></a>Part I. Example Network Configurations</h1></div></div></div><div class="partintro" title="Example Network Configurations"><div><div><div><h1 class="title"><a name="id2556849"></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#id2556922">Introduction</a></span></dt><dt><span class="sect1"><a href="simple.html#id2556963">Assignment Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="simple.html#id2557004">Drafting Office</a></span></dt><dt><span class="sect2"><a href="simple.html#id2557714">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#id2561049">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#id2561519">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2561542">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2561602">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2561650">Technical Issues</a></span></dt><dt><span class="sect2"><a href="small.html#id2561848">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2561869">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2563413">Validation</a></span></dt><dt><span class="sect2"><a href="small.html#id2564061">Notebook Computers: A Special Case</a></span></dt><dt><span class="sect2"><a href="small.html#id2564087">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2564161">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#id2564639">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2564691">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2564924">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2564939">Technical Issues</a></span></dt><dt><span class="sect2"><a href="secure.html#id2565367">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2565406">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#id2566260">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#id2570721">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2570783">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#id2571305">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2571350">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2571456">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2571492">Technical Issues</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2571695">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2571718">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#id2572445">Server Preparation: All Servers</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2573010">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#id2576210">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2576268">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#id2577106">Regarding LDAP Directories and Windows Computer Accounts</a></span></dt><dt><span class="sect1"><a href="happy.html#id2577248">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2577346">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2577483">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2577941">Technical Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2579819">Political Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2579834">Installation Checklist</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2580015">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#id2582912">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#id2586862">Miscellaneous Server Preparation Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2586882">Configuring Directory Share Point Roots</a></span></dt><dt><span class="sect2"><a href="happy.html#id2586977">Configuring Profile Directories</a></span></dt><dt><span class="sect2"><a href="happy.html#id2587221">Preparation of Logon Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2587332">Assigning User Rights and Privileges</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2587466">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#id2588220">Configuration of MS Outlook to Relocate PST File</a></span></dt><dt><span class="sect2"><a href="happy.html#id2588536">Configure Delete Cached Profiles on Logout</a></span></dt><dt><span class="sect2"><a href="happy.html#id2588716">Uploading Printer Drivers to Samba Servers</a></span></dt><dt><span class="sect2"><a href="happy.html#id2589218">Software Installation</a></span></dt><dt><span class="sect2"><a href="happy.html#id2589254">Roll-out Image Creation</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2589288">Key Points Learned</a></span></dt><dt><span class="sect1"><a href="happy.html#id2589403">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#id2589825">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2589856">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2589924">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2590197">Technical Issues</a></span></dt><dt><span class="sect2"><a href="2000users.html#id2591142">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2591160">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2594319">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2594466">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 4bfa59024d..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.75.2"><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" title="Chapter 13. Performance, Reliability, and Availability"><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#id2625018">Introduction</a></span></dt><dt><span class="sect1"><a href="HA.html#id2625115">Dissection and Discussion</a></span></dt><dt><span class="sect1"><a href="HA.html#id2625588">Guidelines for Reliable Samba Operation</a></span></dt><dd><dl><dt><span class="sect2"><a href="HA.html#id2625615">Name Resolution</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626091">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626419">Use and Location of BDCs</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626494">Use One Consistent Version of MS Windows Client</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626516">For Scalability, Use SAN-Based Storage on Samba Servers</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626565">Distribute Network Load with MSDFS</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626620">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626666">Hardware Problems</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626814">Large Directories</a></span></dt></dl></dd><dt><span class="sect1"><a href="HA.html#id2626917">Key Points Learned</a></span></dt></dl></div><p> - <a class="indexterm" name="id2624980"></a> - <a class="indexterm" name="id2624986"></a> - <a class="indexterm" name="id2624993"></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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2625018"></a>Introduction</h2></div></div></div><p> - <a class="indexterm" name="id2625026"></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="id2625056"></a> - <a class="indexterm" name="id2625062"></a> - <a class="indexterm" name="id2625069"></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&lr=&ie=ISO-8859-1&q=samba+cluster&btnG=Google+Search" target="_top">A search</a> - for <span class="quote">“<span class="quote">samba cluster</span>”</span> produced 71,600 hits. And a search for <span class="quote">“<span class="quote">highly available samba</span>”</span> - and <span class="quote">“<span class="quote">highly available windows</span>”</span> produced an amazing number of references. + for “<span class="quote">samba cluster</span>” produced 71,600 hits. And a search for “<span class="quote">highly available samba</span>” + and “<span class="quote">highly available windows</span>” 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="id2625103"></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" title="Dissection and Discussion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2625115"></a>Dissection and Discussion</h2></div></div></div><p> - <a class="indexterm" name="id2625123"></a> - <a class="indexterm" name="id2625130"></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="id2625152"></a> - <a class="indexterm" name="id2625159"></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="id2625186"></a> - <a class="indexterm" name="id2625193"></a> - <a class="indexterm" name="id2625200"></a> - <a class="indexterm" name="id2625207"></a> - <a class="indexterm" name="id2625213"></a> - <a class="indexterm" name="id2625220"></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="id2625281"></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 class="itemizedlist" type="disc"><li class="listitem"><p>Not Working (NW)</p></li><li class="listitem"><p>Broken Behavior (BB)</p></li><li class="listitem"><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="id2625575"></a> + </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="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" title="Guidelines for Reliable Samba Operation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2625588"></a>Guidelines for Reliable Samba Operation</h2></div></div></div><p> - <a class="indexterm" name="id2625596"></a> - <a class="indexterm" name="id2625603"></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" title="Name Resolution"><div class="titlepage"><div><div><h3 class="title"><a name="id2625615"></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" title="Bad Hostnames"><div class="titlepage"><div><div><h4 class="title"><a name="id2625627"></a>Bad Hostnames</h4></div></div></div><p> - <a class="indexterm" name="id2625635"></a> - <a class="indexterm" name="id2625644"></a> - <a class="indexterm" name="id2625651"></a> - <a class="indexterm" name="id2625658"></a> - <a class="indexterm" name="id2625665"></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="id2625719"></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="id2625733"></a> - <a class="indexterm" name="id2625742"></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> @@ -121,50 +121,50 @@ (workgroup) <code class="constant">collision.parrots.com</code>, since this results in DNS lookup 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" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - <a class="indexterm" name="id2625787"></a> - <a class="indexterm" name="id2625796"></a> - <a class="indexterm" name="id2625803"></a> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + <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" title="Routed Networks"><div class="titlepage"><div><div><h4 class="title"><a name="id2625819"></a>Routed Networks</h4></div></div></div><p> - <a class="indexterm" name="id2625827"></a> - <a class="indexterm" name="id2625834"></a> - <a class="indexterm" name="id2625843"></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">“Networking Primer”</a>. </p><p> - <a class="indexterm" name="id2625862"></a> - <a class="indexterm" name="id2625869"></a> - <a class="indexterm" name="id2625876"></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 class="itemizedlist" type="disc"><li class="listitem"><p> - <a class="indexterm" name="id2625893"></a> - <a class="indexterm" name="id2625900"></a> - <a class="indexterm" name="id2625907"></a> + </p><div class="itemizedlist"><ul type="disc"><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2625952"></a> + </p></li><li><p> + <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" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - <a class="indexterm" name="id2625969"></a> - <a class="indexterm" name="id2625979"></a> + </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="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" title="Network Collisions"><div class="titlepage"><div><div><h4 class="title"><a name="id2625992"></a>Network Collisions</h4></div></div></div><p> - <a class="indexterm" name="id2625999"></a> - <a class="indexterm" name="id2626009"></a> - <a class="indexterm" name="id2626018"></a> - <a class="indexterm" name="id2626025"></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">“Networking Primer”</a>. </p><p> - <a class="indexterm" name="id2626053"></a> - <a class="indexterm" name="id2626060"></a> - <a class="indexterm" name="id2626067"></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" title="Samba Configuration"><div class="titlepage"><div><div><h3 class="title"><a name="id2626091"></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="id2626111"></a> - <a class="indexterm" name="id2626118"></a> - <a class="indexterm" name="id2626125"></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="id2626175"></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="id2626234"></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 = <server list>' cannot be set in the smb.conf file. nmbd will abort with this setting. </pre><p> </p><p> - <a class="indexterm" name="id2626262"></a> - <a class="indexterm" name="id2626269"></a> - <a class="indexterm" name="id2626276"></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="id2626310"></a> - <a class="indexterm" name="id2626317"></a> - <a class="indexterm" name="id2626323"></a> - <a class="indexterm" name="id2626330"></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="id2626372"></a> - <a class="indexterm" name="id2626379"></a> - <a class="indexterm" name="id2626386"></a> - <a class="indexterm" name="id2626393"></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">“Shared Data Integrity”</a> for more information. - </p></div><div class="sect2" title="Use and Location of BDCs"><div class="titlepage"><div><div><h3 class="title"><a name="id2626419"></a>Use and Location of BDCs</h3></div></div></div><p> - <a class="indexterm" name="id2626427"></a> - <a class="indexterm" name="id2626433"></a> - <a class="indexterm" name="id2626440"></a> - <a class="indexterm" name="id2626446"></a> - <a class="indexterm" name="id2626453"></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="id2626472"></a> - <a class="indexterm" name="id2626479"></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" title="Use One Consistent Version of MS Windows Client"><div class="titlepage"><div><div><h3 class="title"><a name="id2626494"></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" title="For Scalability, Use SAN-Based Storage on Samba Servers"><div class="titlepage"><div><div><h3 class="title"><a name="id2626516"></a>For Scalability, Use SAN-Based Storage on Samba Servers</h3></div></div></div><p> - <a class="indexterm" name="id2626524"></a> - <a class="indexterm" name="id2626531"></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="id2626545"></a> - <a class="indexterm" name="id2626552"></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" title="Distribute Network Load with MSDFS"><div class="titlepage"><div><div><h3 class="title"><a name="id2626565"></a>Distribute Network Load with MSDFS</h3></div></div></div><p> - <a class="indexterm" name="id2626574"></a> - <a class="indexterm" name="id2626580"></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="id2626599"></a> - <a class="indexterm" name="id2626608"></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" title="Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth"><div class="titlepage"><div><div><h3 class="title"><a name="id2626620"></a>Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</h3></div></div></div><p> - <a class="indexterm" name="id2626629"></a> - <a class="indexterm" name="id2626636"></a> - <a class="indexterm" name="id2626642"></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" title="Hardware Problems"><div class="titlepage"><div><div><h3 class="title"><a name="id2626666"></a>Hardware Problems</h3></div></div></div><p> - <a class="indexterm" name="id2626674"></a> - <a class="indexterm" name="id2626681"></a> - <a class="indexterm" name="id2626688"></a> - <a class="indexterm" name="id2626694"></a> - <a class="indexterm" name="id2626704"></a> - <a class="indexterm" name="id2626713"></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="id2626729"></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="id2626743"></a> - <a class="indexterm" name="id2626750"></a> - <a class="indexterm" name="id2626757"></a> - <a class="indexterm" name="id2626764"></a> - <a class="indexterm" name="id2626771"></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="id2626794"></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" title="Large Directories"><div class="titlepage"><div><div><h3 class="title"><a name="id2626814"></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" title="Key Points Learned"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2626917"></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="id2626938"></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 5880eae8fc..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.75.2"><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" title="Part III. Reference Section"><div class="titlepage"><div><div><h1 class="title"><a name="RefSection"></a>Part III. Reference Section</h1></div></div></div><div class="partintro" title="Reference Section"><div><div><div><h1 class="title"><a name="id2616575"></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#id2616672">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2617322">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2617338">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2617736">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#id2619366">Share Access Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2619714">Share Definition Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2620328">Share Point Directory and File Permissions</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2620740">Managing Windows 200x ACLs</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2621467">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2621601">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#id2622230">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2622261">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2622372">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2622405">Technical Issues</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2622561">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2622578">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#id2624430">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2624491">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#id2625018">Introduction</a></span></dt><dt><span class="sect1"><a href="HA.html#id2625115">Dissection and Discussion</a></span></dt><dt><span class="sect1"><a href="HA.html#id2625588">Guidelines for Reliable Samba Operation</a></span></dt><dd><dl><dt><span class="sect2"><a href="HA.html#id2625615">Name Resolution</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626091">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626419">Use and Location of BDCs</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626494">Use One Consistent Version of MS Windows Client</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626516">For Scalability, Use SAN-Based Storage on Samba Servers</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626565">Distribute Network Load with MSDFS</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626620">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626666">Hardware Problems</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626814">Large Directories</a></span></dt></dl></dd><dt><span class="sect1"><a href="HA.html#id2626917">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#id2627087">Free Support</a></span></dt><dt><span class="sect1"><a href="ch14.html#id2627306">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#id2628013">Samba System File Location</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2628434">Starting Samba</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2628774">DNS Configuration Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2628786">The Forward Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2628834">The Reverse Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2628974">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#id2629033">Initialization of the LDAP Database</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#id2629619">The LDAP Account Manager</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2630616">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#id2631091">Microsoft Access</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2631238">Act! Database Sharing</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2631322">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#id2631489">Requirements and Notes</a></span></dt><dt><span class="sect1"><a href="primer.html#id2631650">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2631710">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#id2631827">Exercises</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2631953">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#id2633100">Simple Windows Client Connection Characteristics</a></span></dt><dt><span class="sect2"><a href="primer.html#id2633603">Windows 200x/XP Client Interaction with Samba-3</a></span></dt><dt><span class="sect2"><a href="primer.html#id2634171">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#id2634286">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. - <acronym class="acronym">GNU</acronym> General Public License version 3 - </a></span></dt><dd><dl><dt><span class="bridgehead"><a href="apa.html#id2634952">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#id2628866">A. Preamble - </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2635097">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#id2635101">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#id2635193">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#id2635291">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#id2635331">A. + </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629246">A. 3. Protecting Users’ Legal Rights From Anti-Circumvention Law. - </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2635367">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#id2635394">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#id2635489">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#id2635679">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#id2635814">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#id2635858">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#id2635878">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#id2635930">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#id2636075">A. + </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629990">A. 12. No Surrender of Others’ Freedom. - </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2636097">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#id2636126">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#id2636188">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#id2636214">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#id2636235">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#id2636251">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#id2636255">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 8e4b4ee2a5..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.75.2"><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. +<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="id2628837"></a>Appendix A. <acronym class="acronym">GNU</acronym> 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" title="Appendix A. GNU General Public License version 3"><div class="titlepage"><div><div><h2 class="title"><a name="id2634922"></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#id2634952">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#id2635097">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#id2635101">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#id2635193">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#id2635291">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#id2635331">A. + </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629246">A. 3. Protecting Users’ Legal Rights From Anti-Circumvention Law. - </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2635367">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#id2635394">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#id2635489">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#id2635679">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#id2635814">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#id2635858">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#id2635878">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#id2635930">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#id2636075">A. + </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629990">A. 12. No Surrender of Others’ Freedom. - </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2636097">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#id2636126">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#id2636188">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#id2636214">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#id2636235">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#id2636251">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#id2636255">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="id2634952"></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="id2635097"></a> + </p><h2><a name="id2629012"></a> TERMS AND CONDITIONS - </h2><h2><a name="id2635101"></a> + </h2><h2><a name="id2629015"></a> 0. Definitions. </h2><p> “This License” 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="id2635193"></a> + </p><h2><a name="id2629108"></a> 1. Source Code. </h2><p> The “source code” 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="id2635291"></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="id2635331"></a> + </p><h2><a name="id2629246"></a> 3. Protecting Users’ 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’s users, your or third parties’ legal rights to forbid circumvention of technological measures. - </p><h2><a name="id2635367"></a> + </p><h2><a name="id2629281"></a> 4. Conveying Verbatim Copies. </h2><p> You may convey verbatim copies of the Program’s source code as you @@ -255,21 +255,21 @@ </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="id2635394"></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 it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: - </p><div class="orderedlist"><ol class="orderedlist" type="a"><li class="listitem"><p> + </p><div class="orderedlist"><ol type="a"><li><p> The work must carry prominent notices stating that you modified it, and giving a relevant date. - </p></li><li class="listitem"><p> + </p></li><li><p> The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”. - </p></li><li class="listitem"><p> + </p></li><li><p> You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the @@ -277,7 +277,7 @@ packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. - </p></li><li class="listitem"><p> + </p></li><li><p> If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need @@ -291,18 +291,18 @@ or legal rights of the compilation’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="id2635489"></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 sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: - </p><div class="orderedlist"><ol class="orderedlist" type="a"><li class="listitem"><p> + </p><div class="orderedlist"><ol type="a"><li><p> Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. - </p></li><li class="listitem"><p> + </p></li><li><p> Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts @@ -313,12 +313,12 @@ price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. - </p></li><li class="listitem"><p> + </p></li><li><p> Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. - </p></li><li class="listitem"><p> + </p></li><li><p> Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no @@ -331,7 +331,7 @@ Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. - </p></li><li class="listitem"><p> + </p></li><li><p> Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under @@ -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="id2635679"></a> + </p><h2><a name="id2629594"></a> 7. Additional Terms. </h2><p> “Additional permissions” are terms that supplement the terms of @@ -408,24 +408,24 @@ Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: - </p><div class="orderedlist"><ol class="orderedlist" type="a"><li class="listitem"><p> + </p><div class="orderedlist"><ol type="a"><li><p> Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or - </p></li><li class="listitem"><p> + </p></li><li><p> Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or - </p></li><li class="listitem"><p> + </p></li><li><p> Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or - </p></li><li class="listitem"><p> + </p></li><li><p> Limiting the use for publicity purposes of names of licensors or authors of the material; or - </p></li><li class="listitem"><p> + </p></li><li><p> Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or - </p></li><li class="listitem"><p> + </p></li><li><p> Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any @@ -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="id2635814"></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="id2635858"></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="id2635878"></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="id2635930"></a> + </p><h2><a name="id2629844"></a> 11. Patents. </h2><p> A “contributor” 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="id2636075"></a> + </p><h2><a name="id2629990"></a> 12. No Surrender of Others’ 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="id2636097"></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="id2636126"></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="id2636188"></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="id2636214"></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="id2636235"></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="id2636251"></a> + </p><h2><a name="id2630166"></a> END OF TERMS AND CONDITIONS - </h2><h2><a name="id2636255"></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 341782f10c..e944d450ba 100644 --- a/docs/htmldocs/Samba3-ByExample/appendix.html +++ b/docs/htmldocs/Samba3-ByExample/appendix.html @@ -1,26 +1,26 @@ -<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.75.2"><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" title="Chapter 15. A Collection of Useful Tidbits"><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#id2628013">Samba System File Location</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2628434">Starting Samba</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2628774">DNS Configuration Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2628786">The Forward Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2628834">The Reverse Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2628974">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#id2629033">Initialization of the LDAP Database</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#id2629619">The LDAP Account Manager</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2630616">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#id2631091">Microsoft Access</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2631238">Act! Database Sharing</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2631322">Opportunistic Locking Controls</a></span></dt></dl></dd></dl></div><p> - <a class="indexterm" name="id2627434"></a> - <a class="indexterm" name="id2627441"></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" title="Joining a Domain: Windows 200x/XP Professional"><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="id2627471"></a> + </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="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" title="Procedure 15.1. Steps to Join a Domain"><a name="id2627485"></a><p class="title"><b>Procedure 15.1. Steps to Join a Domain</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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 class="step" title="Step 2"><p> + </p></li><li><p> Right-click <span class="guimenu">My Computer</span>, and then select <span class="guimenuitem">Properties</span>. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> 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="appendix.html#swxpp001" title="Figure 15.1. The General Panel.">“The General Panel.”</a>. </p><div class="figure"><a name="swxpp001"></a><p class="title"><b>Figure 15.1. 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 class="step" title="Step 4"><p> + </p></li><li><p> 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>. @@ -29,40 +29,40 @@ 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="appendix.html#swxpp004" title="Figure 15.2. The Computer Name Panel.">“The Computer Name Panel.”</a>. </p><div class="figure"><a name="swxpp004"></a><p class="title"><b>Figure 15.2. The Computer Name Panel.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/wxpp004.png" alt="The Computer Name Panel."></div></div></div><p><br class="figure-break"> - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> Click on <span class="guimenu">Change</span>. This panel shows that our example machine (TEMPTATION) is in a workgroup called WORKGROUP. We join the domain called MIDEARTH. See <a class="link" href="appendix.html#swxpp006" title="Figure 15.3. The Computer Name Changes Panel">“The Computer Name Changes Panel”</a>. </p><div class="figure"><a name="swxpp006"></a><p class="title"><b>Figure 15.3. 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 class="step" title="Step 6"><p> + </p></li><li><p> 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="appendix.html#swxpp007" title="Figure 15.4. The Computer Name Changes Panel Domain MIDEARTH">“The Computer Name Changes Panel Domain MIDEARTH”</a>. </p><div class="figure"><a name="swxpp007"></a><p class="title"><b>Figure 15.4. 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 class="step" title="Step 7"><p> + </p></li><li><p> 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> - Enter the name <span class="quote">“<span class="quote">root</span>”</span> and the root password from your Samba-3 server. See <a class="link" href="appendix.html#swxpp008" title="Figure 15.5. Computer Name Changes User name and Password Panel">“Computer Name Changes User name and Password Panel”</a>. + Enter the name “<span class="quote">root</span>” and the root password from your Samba-3 server. See <a class="link" href="appendix.html#swxpp008" title="Figure 15.5. Computer Name Changes User name and Password Panel">“Computer Name Changes User name and Password Panel”</a>. </p><div class="figure"><a name="swxpp008"></a><p class="title"><b>Figure 15.5. Computer Name Changes User name and Password Panel</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/wxpp008.png" alt="Computer Name Changes User name and Password Panel"></div></div></div><p><br class="figure-break"> - </p></li><li class="step" title="Step 8"><p> + </p></li><li><p> Click <span class="guimenu">OK</span>. </p><p> - The <span class="quote">“<span class="quote">Welcome to the MIDEARTH domain</span>”</span> dialog box should appear. At this point, the machine must be rebooted. + The “<span class="quote">Welcome to the MIDEARTH domain</span>” 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="id2627903"></a> - <a class="indexterm" name="id2627910"></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">“The Computer Name Changes Panel Domain MIDEARTH”</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="id2627936"></a> - <a class="indexterm" name="id2627943"></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="id2627962"></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="id2627985"></a> - According to Microsoft documentation, <span class="quote">“<span class="quote">If this computer belongs to a group with <code class="constant">Group Policy</code> + <a class="indexterm" name="id2621900"></a> + According to Microsoft documentation, “<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>”</span> - </p></div><div class="sect1" title="Samba System File Location"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2628013"></a>Samba System File Location</h2></div></div></div><p><a class="indexterm" name="id2628020"></a><a class="indexterm" name="id2628028"></a><a class="indexterm" name="id2628036"></a> + used only if Group Policy is disabled or unspecified.</span>” + </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="id2628072"></a><a class="indexterm" name="id2628084"></a><a class="indexterm" name="id2628092"></a><a class="indexterm" name="id2628103"></a><a class="indexterm" name="id2628111"></a><a class="indexterm" name="id2628123"></a><a class="indexterm" name="id2628130"></a><a class="indexterm" name="id2628138"></a><a class="indexterm" name="id2628146"></a><a class="indexterm" name="id2628154"></a><a class="indexterm" name="id2628162"></a><a class="indexterm" name="id2628170"></a><a class="indexterm" name="id2628178"></a><a class="indexterm" name="id2628186"></a><a class="indexterm" name="id2628194"></a><a class="indexterm" name="id2628202"></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="id2628271"></a><a class="indexterm" name="id2628279"></a><a class="indexterm" name="id2628287"></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="id2628325"></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="id2628398"></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="id2628421"></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" title="Starting Samba"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2628434"></a>Starting Samba</h2></div></div></div><p><a class="indexterm" name="id2628441"></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="id2628504"></a> - <a class="indexterm" name="id2628511"></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="id2628540"></a> - <a class="indexterm" name="id2628547"></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="id2628576"></a> - <a class="indexterm" name="id2628582"></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="id2628696"></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">“A Useful Samba Control Script for SUSE Linux”</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="id2628731"></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">“A Sample Samba Control Script for Red Hat Linux”</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" title="DNS Configuration Files"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2628774"></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" title="The Forward Zone File for the Loopback Adaptor"><div class="titlepage"><div><div><h3 class="title"><a name="id2628786"></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">“DNS Localhost Forward Zone File: /var/lib/named/localhost.zone”</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" title="The Reverse Zone File for the Loopback Adaptor"><div class="titlepage"><div><div><h3 class="title"><a name="id2628834"></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">“DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone”</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,21 +344,21 @@ 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" title="DNS Root Server Hint File"><div class="titlepage"><div><div><h3 class="title"><a name="id2628974"></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">“DNS Root Name Server Hint File: /var/lib/named/root.hint”</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" title="Alternative LDAP Database Initialization"><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="id2629005"></a><a class="indexterm" name="id2629016"></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" title="Initialization of the LDAP Database"><div class="titlepage"><div><div><h3 class="title"><a name="id2629033"></a>Initialization of the LDAP Database</h3></div></div></div><p><a class="indexterm" name="id2629040"></a><a class="indexterm" name="id2629048"></a><a class="indexterm" name="id2629060"></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 preload the well-known Windows NT Domain Groups, as they must have the correct SID so that they can be recognized as special NT Groups by the MS Windows clients. - </p><div class="procedure" title="Procedure 15.2. LDAP Directory Pre-Load Steps"><a name="ldapinit"></a><p class="title"><b>Procedure 15.2. LDAP Directory Pre-Load Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> + </p><div class="procedure"><a name="ldapinit"></a><p class="title"><b>Procedure 15.2. LDAP Directory Pre-Load Steps</b></p><ol type="1"><li><p> Create a directory in which to store the files you use to generate the LDAP LDIF file for your system. Execute the following: </p><pre class="screen"> @@ -366,16 +366,16 @@ M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33 <code class="prompt">root# </code> chown root:root /etc/openldap/SambaInit <code class="prompt">root# </code> chmod 700 /etc/openldap/SambaInit </pre><p> - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Install the files shown in <a class="link" href="appendix.html#sbehap-ldapreconfa" title="Example 15.6. LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part A">“LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part A”</a>, <a class="link" href="appendix.html#sbehap-ldapreconfb" title="Example 15.7. LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part B">“LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part B”</a>, and <a class="link" href="appendix.html#sbehap-ldapreconfc" title="Example 15.8. LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part C">“LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part C”</a> into the directory <code class="filename">/etc/openldap/SambaInit/SMBLDAP-ldif-preconfig.sh.</code> These three files are, respectively, parts A, B, and C of the <code class="filename">SMBLDAP-ldif-preconfig.sh</code> file. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Install the files shown in <a class="link" href="appendix.html#sbehap-ldifpata" title="Example 15.9. LDIF Pattern File Used to Pre-configure LDAP Part A">“LDIF Pattern File Used to Pre-configure LDAP Part A”</a> and <a class="link" href="appendix.html#sbehap-ldifpatb" title="Example 15.10. LDIF Pattern File Used to Pre-configure LDAP Part B">“LDIF Pattern File Used to Pre-configure LDAP Part B”</a> into the directory <code class="filename">/etc/openldap/SambaInit/.</code> These two files are parts A and B, respectively, of the <code class="filename">init-ldif.pat</code> file. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Change to the <code class="filename">/etc/openldap/SambaInit</code> directory. Execute the following: </p><pre class="screen"> <code class="prompt">root# </code> sh SMBLDAP-ldif-preconfig.sh @@ -415,7 +415,7 @@ Enter the top level org name or press Enter to continue: <code class="prompt">root# </code> </pre><p> This creates a file called <code class="filename">MEGANET2.ldif</code>. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> It is now time to preload the LDAP database with the following command: </p><pre class="screen"> @@ -466,14 +466,14 @@ createTimestamp: 20031217055747Z modifyTimestamp: 20031217055747Z entryCSN: 2003121705:57:47Z#0x000a#0#0000 </pre><p> - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> Your LDAP database is ready for testing. You can now start the LDAP server using the system tool for your Linux operating system. For SUSE Linux, you can do this as follows: </p><pre class="screen"> <code class="prompt">root# </code> rcldap start </pre><p> - </p></li><li class="step" title="Step 7"><p> + </p></li><li><p> It is now a good idea to validate that the LDAP server is running correctly. Execute the following: </p><pre class="screen"> @@ -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" title="The LDAP Account Manager"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2629619"></a>The LDAP Account Manager</h2></div></div></div><p> -<a class="indexterm" name="id2629627"></a> -<a class="indexterm" name="id2629634"></a> -<a class="indexterm" name="id2629643"></a> -<a class="indexterm" name="id2629650"></a> -<a class="indexterm" name="id2629656"></a> -<a class="indexterm" name="id2629663"></a> -<a class="indexterm" name="id2629670"></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,29 +724,29 @@ 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="id2629702"></a> -<a class="indexterm" name="id2629708"></a> -<a class="indexterm" name="id2629715"></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 class="itemizedlist" type="disc"><li class="listitem"><p>A web server that will work with PHP4.</p></li><li class="listitem"><p>PHP4 (available from the <a class="ulink" href="http://www.php.net/" target="_top">PHP</a> home page.)</p></li><li class="listitem"><p>OpenLDAP 2.0 or later.</p></li><li class="listitem"><p>A Web browser that supports CSS.</p></li><li class="listitem"><p>Perl.</p></li><li class="listitem"><p>The gettext package.</p></li><li class="listitem"><p>mcrypt + mhash (optional).</p></li><li class="listitem"><p>It is also a good idea to install SSL support.</p></li></ul></div><p> +</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="id2629776"></a> -<a class="indexterm" name="id2629783"></a> -<a class="indexterm" name="id2629790"></a> -</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Display user/group/host and Domain entries.</p></li><li class="listitem"><p>Manage entries (Add/Delete/Edit).</p></li><li class="listitem"><p>Filter and sort entries.</p></li><li class="listitem"><p>Store and use multiple operating profiles.</p></li><li class="listitem"><p>Edit organizational units (OUs).</p></li><li class="listitem"><p>Upload accounts from a file.</p></li><li class="listitem"><p>Is compatible with Samba-2.2.x and Samba-3.</p></li></ul></div><p> +<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="id2629844"></a> -<a class="indexterm" name="id2629851"></a> -<a class="indexterm" name="id2629858"></a> -<a class="indexterm" name="id2629864"></a> -The default password is <span class="quote">“<span class="quote">lam.</span>”</span> It is highly recommended that you use only +<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 “<span class="quote">lam.</span>” 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 to LAM using only SSL. -</p><div class="procedure" title="Procedure 15.3. Apache Configuration Steps for LAM"><a name="sbehap-laminst"></a><p class="title"><b>Procedure 15.3. Apache Configuration Steps for LAM</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> +</p><div class="procedure"><a name="sbehap-laminst"></a><p class="title"><b>Procedure 15.3. Apache Configuration Steps for LAM</b></p><ol type="1"><li><p> Extract the LAM package by untarring it as shown here: </p><pre class="screen"> <code class="prompt">root# </code> tar xzf ldap-account-manager_0.4.9.tar.gz @@ -755,12 +755,12 @@ to LAM using only SSL. </p><pre class="screen"> <code class="prompt">root# </code> dpkg -i ldap-account-manager_0.4.9.all.deb </pre><p> - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Copy the extracted files to the document root directory of your Web server. For example, on SUSE Linux Enterprise Server 9, copy to the <code class="filename">/srv/www/htdocs</code> directory. - </p></li><li class="step" title="Step 3"><p> - <a class="indexterm" name="id2629944"></a> + </p></li><li><p> + <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 @@ -769,8 +769,8 @@ to LAM using only SSL. <code class="prompt">root# </code> chmod 755 /srv/www/htdocs/lam/config <code class="prompt">root# </code> chmod 755 /srv/www/htdocs/lam/lib/*pl </pre><p> - </p></li><li class="step" title="Step 4"><p> - <a class="indexterm" name="id2629997"></a> + </p></li><li><p> + <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,13 +778,13 @@ 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="id2630038"></a> - <a class="indexterm" name="id2630047"></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">“Example LAM Configuration File config.cfg”</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 configuration suite. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> Start your Web server then, using your Web browser, connect to <a class="ulink" href="http://localhost/lam" target="_top">LAM</a> URL. Click on the the <em class="parameter"><code>Configuration Login</code></em> link then click on the @@ -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="id2630106"></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">“LAM Profile Control File lam.conf”</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="id2630130"></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">“The LDAP Account Manager Login Screen”</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="id2630192"></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">“The LDAP Account Manager Configuration Screen”</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="id2630264"></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="id2630279"></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">“The LDAP Account Manager User Edit Screen”</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="id2630459"></a><a class="indexterm" name="id2630464"></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">“The LDAP Account Manager Host Edit Screen”</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" title="IDEALX Management Console"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2630616"></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" title="Effect of Setting File and Directory SUID/SGID Permissions Explained"><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="id2630722"></a><a class="indexterm" name="id2630728"></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" title="Shared Data Integrity"><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="id2630960"></a><a class="indexterm" name="id2630967"></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="id2630990"></a><a class="indexterm" name="id2631002"></a><a class="indexterm" name="id2631013"></a> - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>application-level locking controls</p></li><li class="listitem"><p>client-side locking controls</p></li><li class="listitem"><p>server-side locking controls</p></li></ul></div><p><a class="indexterm" name="id2631046"></a><a class="indexterm" name="id2631054"></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="id2631070"></a><a class="indexterm" name="id2631078"></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" title="Microsoft Access"><div class="titlepage"><div><div><h3 class="title"><a name="id2631091"></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 class="itemizedlist" type="disc"><li class="listitem"><p>http://support.microsoft.com/default.aspx?scid=kb;en-us;208778</p></li><li class="listitem"><p>http://support.microsoft.com/default.aspx?scid=kb;en-us;299373</p></li></ul></div><p><a class="indexterm" name="id2631118"></a><a class="indexterm" name="id2631129"></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="id2631180"></a> - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Default open mode: Shared</p></li><li class="listitem"><p>Default Record Locking: Edited Record</p></li><li class="listitem"><p>Open databases using record_level locking</p></li></ul></div><p><a class="indexterm" name="id2631209"></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" title="Act! Database Sharing"><div class="titlepage"><div><div><h3 class="title"><a name="id2631238"></a>Act! Database Sharing</h3></div></div></div><p><a class="indexterm" name="id2631245"></a><a class="indexterm" name="id2631253"></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="id2631283"></a><a class="indexterm" name="id2631291"></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" title="Opportunistic Locking Controls"><div class="titlepage"><div><div><h3 class="title"><a name="id2631322"></a>Opportunistic Locking Controls</h3></div></div></div><p><a class="indexterm" name="id2631330"></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="id2631342" href="#ftn.id2631342" 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="id2631356"></a><a class="indexterm" name="id2631364"></a><a class="indexterm" name="id2631372"></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="id2631393"></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. diff --git a/docs/htmldocs/Samba3-ByExample/ch14.html b/docs/htmldocs/Samba3-ByExample/ch14.html index 79c82256ad..57d4492cee 100644 --- a/docs/htmldocs/Samba3-ByExample/ch14.html +++ b/docs/htmldocs/Samba3-ByExample/ch14.html @@ -1,12 +1,12 @@ -<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.75.2"><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 lang="en-US" class="chapter" title="Chapter 14. Samba Support"><div class="titlepage"><div><div><h2 class="title"><a name="id2626956"></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#id2627087">Free Support</a></span></dt><dt><span class="sect1"><a href="ch14.html#id2627306">Commercial Support</a></span></dt></dl></div><p> -<a class="indexterm" name="id2626966"></a> -One of the most difficult to answer questions in the information technology industry is, <span class="quote">“<span class="quote">What is -support?</span>”</span>. That question irritates some folks, as much as common answers may annoy others. +<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, “<span class="quote">What is +support?</span>”. That question irritates some folks, as much as common answers may annoy others. </p><p> -<a class="indexterm" name="id2626982"></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: -<span class="quote">“<span class="quote">Oh, Linux? We do not support Linux!</span>”</span>. It has happened to me, and similar situations happen +“<span class="quote">Oh, Linux? We do not support Linux!</span>”. It has happened to me, and similar situations happen through-out the IT industry. Answers like that are designed to inform us that there are some customers that a business just does not want to deal with, and well may we feel the anguish of the rejection that is dished out. @@ -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="id2627013"></a> -<a class="indexterm" name="id2627020"></a> -<a class="indexterm" name="id2627027"></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="id2627042"></a> -<a class="indexterm" name="id2627048"></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="id2627063"></a> -<a class="indexterm" name="id2627070"></a> -<a class="indexterm" name="id2627077"></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" title="Free Support"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2627087"></a>Free Support</h2></div></div></div><p> -<a class="indexterm" name="id2627095"></a> -<a class="indexterm" name="id2627102"></a> -<a class="indexterm" name="id2627108"></a> -<a class="indexterm" name="id2627115"></a> -<a class="indexterm" name="id2627122"></a> -<a class="indexterm" name="id2627129"></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="id2627143"></a> -<a class="indexterm" name="id2627150"></a> -<a class="indexterm" name="id2627157"></a> -<a class="indexterm" name="id2627164"></a> -<a class="indexterm" name="id2627171"></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="id2627212"></a> -<a class="indexterm" name="id2627219"></a> -<a class="indexterm" name="id2627226"></a> -<a class="indexterm" name="id2627233"></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="id2627253"></a> -<a class="indexterm" name="id2627260"></a> -<a class="indexterm" name="id2627267"></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="id2627291"></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" title="Commercial Support"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2627306"></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 class="itemizedlist" type="disc"><li class="listitem"><p>Assistance with network design</p></li><li class="listitem"><p>Staff Training</p></li><li class="listitem"><p>Assistance with Samba network deployment and installation</p></li><li class="listitem"><p>Priority telephone or email Samba configuration assistance</p></li><li class="listitem"><p>Trouble-shooting and diagnostic assistance</p></li><li class="listitem"><p>Provision of quality assured ready-to-install Samba binary packages</p></li></ul></div><p> -<a class="indexterm" name="id2627352"></a> -<a class="indexterm" name="id2627359"></a> + </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="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="id2627385"></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="id2627402"></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 4efb55a903..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.75.2"><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" title="Glossary"><div class="titlepage"><div><div><h2 class="title"><a name="id2636444"></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> @@ -11,7 +11,7 @@ the Internet hype in the 1990s. At about the time that the SMB protocol was renamed to CIFS, an additional dialect of the SMB protocol was in development. The need for the deployment of the NetBIOS layer was also removed, thus paving the way for use of the SMB - protocol natively over TCP/IP (known as NetBIOS-less SMB or <span class="quote">“<span class="quote">naked</span>”</span> TCP + protocol natively over TCP/IP (known as NetBIOS-less SMB or “<span class="quote">naked</span>” TCP transport). </p></dd><dt>Common UNIX Printing System</dt><dd><p> A recent implementation of a high-capability printing system for UNIX developed by @@ -96,8 +96,8 @@ DER refers to Distinguished Encoding Rules. These are a set of common rules for creating binary encodings in a platform-independent manner. Samba has support for SPNEGO. </p></dd><dt>The Official Samba-3 HOWTO and Reference Guide, Second Edition</dt><dd><p> - This book makes repeated reference to <span class="quote">“<span class="quote">The Official Samba-3 HOWTO and Reference Guide, Second - Edition</span>”</span> by John H. Terpstra and Jelmer R. Vernooij. This publication is available from + This book makes repeated reference to “<span class="quote">The Official Samba-3 HOWTO and Reference Guide, Second + Edition</span>” by John H. Terpstra and Jelmer R. Vernooij. This publication is available from Amazon.com. Publisher: Prentice Hall PTR (August 2005), ISBN: 013122282. </p></dd><dt>User IDentifier</dt><dd><p> @@ -111,5 +111,5 @@ freely available for UNIX/Linux and Microsoft Windows systems from <a class="ulink" href="http://www.wireshark.org" target="_top">the Wireshark Web site</a>. </p></dd></dl></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="apa.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ix01.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix A. - <acronym class="acronym">GNU</acronym> General Public License version 3 + GNU General Public License version 3 </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Index</td></tr></table></div></body></html> diff --git a/docs/htmldocs/Samba3-ByExample/happy.html b/docs/htmldocs/Samba3-ByExample/happy.html index 1105d80890..41cd3b5a67 100644 --- a/docs/htmldocs/Samba3-ByExample/happy.html +++ b/docs/htmldocs/Samba3-ByExample/happy.html @@ -1,12 +1,12 @@ -<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.75.2"><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" title="Chapter 5. Making Happy Users"><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#id2577106">Regarding LDAP Directories and Windows Computer Accounts</a></span></dt><dt><span class="sect1"><a href="happy.html#id2577248">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2577346">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2577483">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2577941">Technical Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2579819">Political Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2579834">Installation Checklist</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2580015">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#id2582912">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#id2586862">Miscellaneous Server Preparation Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2586882">Configuring Directory Share Point Roots</a></span></dt><dt><span class="sect2"><a href="happy.html#id2586977">Configuring Profile Directories</a></span></dt><dt><span class="sect2"><a href="happy.html#id2587221">Preparation of Logon Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2587332">Assigning User Rights and Privileges</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2587466">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#id2588220">Configuration of MS Outlook to Relocate PST File</a></span></dt><dt><span class="sect2"><a href="happy.html#id2588536">Configure Delete Cached Profiles on Logout</a></span></dt><dt><span class="sect2"><a href="happy.html#id2588716">Uploading Printer Drivers to Samba Servers</a></span></dt><dt><span class="sect2"><a href="happy.html#id2589218">Software Installation</a></span></dt><dt><span class="sect2"><a href="happy.html#id2589254">Roll-out Image Creation</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2589288">Key Points Learned</a></span></dt><dt><span class="sect1"><a href="happy.html#id2589403">Questions and Answers</a></span></dt></dl></div><p> - It is said that <span class="quote">“<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>”</span> +<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 “<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>” </p><p> In the world of computer networks, problems are as varied as the people who create them or experience them. The design of the network implemented in <a class="link" href="Big500users.html" title="Chapter 4. The 500-User Office">“The 500-User Office”</a> may create problems for some network users. The following lists some of the problems that may occur: - </p><a class="indexterm" name="id2576684"></a><a class="indexterm" name="id2576691"></a><a class="indexterm" name="id2576700"></a><a class="indexterm" name="id2576707"></a><a class="indexterm" name="id2576714"></a><div class="caution" title="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 @@ -19,8 +19,8 @@ be found (when you know it exists), that may be an indication that the domain co overloaded or network bandwidth is overloaded. The guidance given for PDC/BDC ratio to Windows 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="id2576759"></a> - <a class="indexterm" name="id2576768"></a> + <a class="indexterm" name="id2570674"></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="id2576788"></a> - <a class="indexterm" name="id2576795"></a> - <a class="indexterm" name="id2576801"></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 @@ -46,42 +46,42 @@ clients is conservative and if followed will minimize problems but it is not ab that can be supported is limited by the CPU speed, memory and the workload on the Samba server as well as network bandwidth utilization. </p></dd><dt><span class="term">Slow logons and log-offs</span></dt><dd><p> - <a class="indexterm" name="id2576835"></a> + <a class="indexterm" name="id2570750"></a> Slow logons and log-offs may be caused by many factors that include: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> - <a class="indexterm" name="id2576848"></a> - <a class="indexterm" name="id2576860"></a> + </p><div class="itemizedlist"><ul type="disc"><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2576879"></a> - <a class="indexterm" name="id2576886"></a> - <a class="indexterm" name="id2576892"></a> + </p></li><li><p> + <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. - </p></li><li class="listitem"><p> - <a class="indexterm" name="id2576907"></a> + </p></li><li><p> + <a class="indexterm" name="id2570822"></a> Defective networking hardware. Over the past few years, we have seen on the Samba mailing list a significant increase in the number of problems that were traced to a defective network interface controller, a defective HUB or Ethernet switch, or defective cabling. In most cases, it was the erratic nature of the problem that ultimately pointed to the cause of the problem. - </p></li><li class="listitem"><p> - <a class="indexterm" name="id2576927"></a> - <a class="indexterm" name="id2576936"></a> + </p></li><li><p> + <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 MS Outlook PST files as well as by not storing files on the desktop. These are old bad habits that require much discipline and vigilance on the part of network management. - </p></li><li class="listitem"><p> - <a class="indexterm" name="id2576957"></a> + </p></li><li><p> + <a class="indexterm" name="id2570872"></a> You should verify that the Windows XP WebClient service is not running. The use of the WebClient service has been implicated in many Windows networking-related problems. @@ -89,27 +89,27 @@ clients is conservative and if followed will minimize problems but it is not ab </p></dd><dt><span class="term">Loss of access to network drives and printer resources</span></dt><dd><p> Loss of access to network resources during client operation may be caused by a number of factors, including: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> - <a class="indexterm" name="id2576989"></a> + </p><div class="itemizedlist"><ul type="disc"><li><p> + <a class="indexterm" name="id2570904"></a> Network overload (typically indicated by a high network collision rate) - </p></li><li class="listitem"><p> + </p></li><li><p> Server overload - </p></li><li class="listitem"><p> - <a class="indexterm" name="id2577009"></a> + </p></li><li><p> + <a class="indexterm" name="id2570924"></a> Timeout causing the client to close a connection that is in use but has been latent (no traffic) for some time (5 minutes or more) - </p></li><li class="listitem"><p> - <a class="indexterm" name="id2577025"></a> + </p></li><li><p> + <a class="indexterm" name="id2570940"></a> Defective networking hardware </p></li></ul></div><p> - <a class="indexterm" name="id2577039"></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 may restore operations, but in any case this is a serious problem that may lead to the next problem, data corruption. </p></dd><dt><span class="term">Potential data corruption</span></dt><dd><p> - <a class="indexterm" name="id2577073"></a> + <a class="indexterm" name="id2570988"></a> Data corruption is one of the most serious problems. It leads to uncertainty, anger, and frustration, and generally precipitates immediate corrective demands. Management response to this type of problem may be rational, as well as highly irrational. There have been @@ -123,48 +123,48 @@ 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" title="Regarding LDAP Directories and Windows Computer Accounts"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2577106"></a>Regarding LDAP Directories and Windows Computer Accounts</h2></div></div></div><p> - <a class="indexterm" name="id2577115"></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="id2577130"></a> - <a class="indexterm" name="id2577136"></a> - <a class="indexterm" name="id2577143"></a> - <a class="indexterm" name="id2577150"></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="id2577167"></a> - <a class="indexterm" name="id2577173"></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="id2577188"></a> - <a class="indexterm" name="id2577195"></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 switch (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> - Samba asks the host OS to provide a UID via the <span class="quote">“<span class="quote">passwd</span>”</span>, <span class="quote">“<span class="quote">shadow</span>”</span> - and <span class="quote">“<span class="quote">group</span>”</span> facilities in the NSS control (configuration) file. The best tool + Samba asks the host OS to provide a UID via the “<span class="quote">passwd</span>”, “<span class="quote">shadow</span>” + and “<span class="quote">group</span>” 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 Samba. Samba provides winbindd together with its support libraries as one method. It is 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="id2577232"></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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2577248"></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="id2577310"></a> - <a class="indexterm" name="id2577318"></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,56 +204,56 @@ 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" title="Assignment Tasks"><div class="titlepage"><div><div><h3 class="title"><a name="id2577346"></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 class="orderedlist" type="1"><li class="listitem"><p> - <a class="indexterm" name="id2577366"></a> - <a class="indexterm" name="id2577375"></a> - <a class="indexterm" name="id2577382"></a> - <a class="indexterm" name="id2577389"></a><a class="indexterm" name="id2577394"></a> + </p><div class="orderedlist"><ol type="1"><li><p> + <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="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. </p><p> You can implement a single central LDAP server for this purpose. - </p></li><li class="listitem"><p> - <a class="indexterm" name="id2577417"></a> - <a class="indexterm" name="id2577424"></a> - <a class="indexterm" name="id2577430"></a> - <a class="indexterm" name="id2577437"></a> + </p></li><li><p> + <a class="indexterm" name="id2571332"></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="id2577456"></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. </p><p> - <a class="indexterm" name="id2577471"></a> + <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" title="Dissection and Discussion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2577483"></a>Dissection and Discussion</h2></div></div></div><p> - <a class="indexterm" name="id2577491"></a> - <a class="indexterm" name="id2577498"></a> - <a class="indexterm" name="id2577505"></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 class="itemizedlist" type="disc"><li class="listitem"><p> - <a class="indexterm" name="id2577522"></a> + </p><div class="itemizedlist"><ul type="disc"><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2577542"></a> + </p></li><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2577570"></a> + </p></li><li><p> + <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 @@ -264,19 +264,19 @@ clients is conservative and if followed will minimize problems but it is not ab initialize the LDAP directory database. OpenLDAP itself has only command-line tools to help you to get OpenLDAP and Samba-3 running as required, albeit with some learning curve challenges. </p><p> - <a class="indexterm" name="id2577607"></a> + <a class="indexterm" name="id2571522"></a> For most sites, the deployment of Microsoft Active Directory from the shrink-wrapped installation is quite adequate. If you are migrating from Microsoft Active Directory, be warned that OpenLDAP does not include 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="id2577624"></a> - <a class="indexterm" name="id2577631"></a> - <a class="indexterm" name="id2577638"></a> - <a class="indexterm" name="id2577647"></a> - <a class="indexterm" name="id2577657"></a> - <a class="indexterm" name="id2577663"></a> - <a class="indexterm" name="id2577673"></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="id2577698"></a> - <a class="indexterm" name="id2577707"></a> - <a class="indexterm" name="id2577714"></a> - <a class="indexterm" name="id2577721"></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 @@ -300,8 +300,8 @@ clients is conservative and if followed will minimize problems but it is not ab MS ADAM</a> that provides more generic LDAP services, yet it does not have the vanilla-like services of OpenLDAP. </p><p> - <a class="indexterm" name="id2577751"></a> - <a class="indexterm" name="id2577760"></a> + <a class="indexterm" name="id2571666"></a> + <a class="indexterm" name="id2571675"></a> You may wish to consider outsourcing the development of your OpenLDAP directory to an expert, particularly if you find the challenge of learning about LDAP directories, schemas, configuration, and management tools and the creation of shell and Perl scripts a bit @@ -309,7 +309,7 @@ clients is conservative and if followed will minimize problems but it is not ab many ready-to-use schemas. Samba-3 provides an OpenLDAP schema file that is required for use as a passdb backend. </p><p> - <a class="indexterm" name="id2577778"></a> + <a class="indexterm" name="id2571693"></a> For those who are willing to brave the process of installing and configuring LDAP and Samba-3 interoperability, there are a few nice Web-based tools that may help you to manage your users and groups more effectively. The Web-based tools you might like to consider include the @@ -323,7 +323,7 @@ clients is conservative and if followed will minimize problems but it is not ab LDAP <a class="ulink" href="http://www.iit.edu/~gawojar/ldap/" target="_top">Browser/Editor</a> <a class="ulink" href="http://www.jxplorer.org/" target="_top">; JXplorer</a> (by Computer Associates); and <a class="ulink" href="http://phpldapadmin.sourceforge.net/" target="_top">phpLDAPadmin</a>. - </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The following prescriptive guidance is not an LDAP tutorial. The LDAP implementation expressly uses minimal security controls. No form of secure LDAP communications is attempted. The LDAP configuration information provided is considered to consist of the barest essentials only. You are strongly encouraged to learn more about @@ -334,10 +334,10 @@ clients is conservative and if followed will minimize problems but it is not ab <a class="ulink" href="http://www.oreilly.com/catalog/ldapsa/index.html" target="_top"><span class="emphasis"><em>LDAP System Administration</em></span>,</a> by Jerry Carter quite useful. </p><p> - <a class="indexterm" name="id2577876"></a> - <a class="indexterm" name="id2577882"></a> - <a class="indexterm" name="id2577892"></a> - <a class="indexterm" name="id2577898"></a> + <a class="indexterm" name="id2571791"></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 @@ -345,31 +345,31 @@ clients is conservative and if followed will minimize problems but it is not ab user desktops, and this must be done in a way that wins their support and does not cause further loss of staff morale. The following procedures solve this problem. </p><p> - <a class="indexterm" name="id2577921"></a> + <a class="indexterm" name="id2571836"></a> There is also an opportunity to implement smart printing features. You add this to the Samba configuration so that future printer changes can be managed without need to change desktop configurations. </p><p> You add the ability to automatically download new printer drivers, even if they are not installed 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" title="Technical Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2577941"></a>Technical Issues</h3></div></div></div><p> - <a class="indexterm" name="id2577949"></a> - <a class="indexterm" name="id2577958"></a> - <a class="indexterm" name="id2577967"></a> + </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="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 server for UNIX system accounts as well as for Samba. From the OpenLDAP perspective, UNIX system 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 class="itemizedlist" type="disc"><li class="listitem"><p>Windows Networking User Accounts</p></li><li class="listitem"><p>Windows NT Group Accounts</p></li><li class="listitem"><p>Mapping Information between UNIX Groups and Windows NT Groups</p></li><li class="listitem"><p>ID Mappings for SIDs to UIDs (also for foreign Domain SIDs)</p></li></ul></div><p> - <a class="indexterm" name="id2578008"></a> - <a class="indexterm" name="id2578015"></a> - <a class="indexterm" name="id2578022"></a> - <a class="indexterm" name="id2578028"></a> - <a class="indexterm" name="id2578035"></a> - <a class="indexterm" name="id2578042"></a> - <a class="indexterm" name="id2578051"></a> - <a class="indexterm" name="id2578058"></a> - <a class="indexterm" name="id2578064"></a> + </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="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 @@ -378,16 +378,16 @@ clients is conservative and if followed will minimize problems but it is not ab that integrates with the NSS. The same requirements exist for resolution of the UNIX username to the UID. The relationships are demonstrated in <a class="link" href="happy.html#sbehap-LDAPdiag" title="Figure 5.1. The Interaction of LDAP, UNIX Posix Accounts and Samba Accounts">“The Interaction of LDAP, UNIX Posix Accounts and Samba Accounts”</a>. </p><div class="figure"><a name="sbehap-LDAPdiag"></a><p class="title"><b>Figure 5.1. The Interaction of LDAP, UNIX Posix Accounts and Samba Accounts</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/UNIX-Samba-and-LDAP.png" width="270" alt="The Interaction of LDAP, UNIX Posix Accounts and Samba Accounts"></div></div></div><br class="figure-break"><p> - <a class="indexterm" name="id2578150"></a> - <a class="indexterm" name="id2578157"></a> + <a class="indexterm" name="id2572065"></a> + <a class="indexterm" name="id2572072"></a> You configure OpenLDAP so that it is operational. Before deploying the OpenLDAP, you really 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="id2578173"></a> - <a class="indexterm" name="id2578180"></a> - <a class="indexterm" name="id2578189"></a> - <a class="indexterm" name="id2578196"></a> + <a class="indexterm" name="id2572088"></a> + <a class="indexterm" name="id2572095"></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="id2578230"></a> - <a class="indexterm" name="id2578237"></a> - <a class="indexterm" name="id2578244"></a> + <a class="indexterm" name="id2572145"></a> + <a class="indexterm" name="id2572152"></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="id2578263"></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="id2578277"></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" title="Addition of Machines to the Domain"><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="id2578299"></a> - <a class="indexterm" name="id2578304"></a> - <a class="indexterm" name="id2578309"></a> - <a class="indexterm" name="id2578315"></a> + </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="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" title="Roaming Profile Background"><div class="titlepage"><div><div><h4 class="title"><a name="id2578452"></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="id2578465"></a> - <a class="indexterm" name="id2578472"></a> - <a class="indexterm" name="id2578479"></a> - <a class="indexterm" name="id2578486"></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="id2578565"></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="id2578583"></a> - <a class="indexterm" name="id2578590"></a> - <a class="indexterm" name="id2578597"></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="id2578618"></a> - <a class="indexterm" name="id2578625"></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. @@ -474,11 +474,11 @@ clients is conservative and if followed will minimize problems but it is not ab user's profile. Then just create a Network Default Profile. Of course, it is necessary to copy all files from redirected folders to the network share to which they are redirected. - </p></div><div class="sect3" title="The Local Group Policy"><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="id2578665"></a> - <a class="indexterm" name="id2578672"></a> - <a class="indexterm" name="id2578679"></a> - <a class="indexterm" name="id2578686"></a> + </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="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>). @@ -487,31 +487,31 @@ clients is conservative and if followed will minimize problems but it is not ab be found under <span class="guimenu">User Configuration</span> → <span class="guimenuitem">Administrative Templates</span> → <span class="guimenuitem">System</span> → <span class="guimenuitem">User Profiles</span>. By default this setting contains - <span class="quote">“<span class="quote">Local Settings; Temporary Internet Files; History; Temp</span>”</span>. + “<span class="quote">Local Settings; Temporary Internet Files; History; Temp</span>”. </p><p> 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" title="Profile Changes"><div class="titlepage"><div><div><h4 class="title"><a name="id2578753"></a>Profile Changes</h4></div></div></div><p> - <a class="indexterm" name="id2578761"></a> - <a class="indexterm" name="id2578768"></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="id2578795"></a> - <a class="indexterm" name="id2578802"></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">“Configuration of Default Profile with Folder Redirection”</a>. - </p></div><div class="sect3" title="Using a Network Default User Profile"><div class="titlepage"><div><div><h4 class="title"><a name="id2578847"></a>Using a Network Default User Profile</h4></div></div></div><p> - <a class="indexterm" name="id2578855"></a> - <a class="indexterm" name="id2578862"></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,20 +520,20 @@ 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" title="Installation of Printer Driver Auto-Download"><div class="titlepage"><div><div><h4 class="title"><a name="id2578906"></a>Installation of Printer Driver Auto-Download</h4></div></div></div><p> - <a class="indexterm" name="id2578914"></a> - <a class="indexterm" name="id2578923"></a> - <a class="indexterm" name="id2578930"></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 <span class="quote">“<span class="quote">dumb</span>”</span> printing. Dumb printing is the arrangement by which all drivers + known as “<span class="quote">dumb</span>” printing. Dumb printing is the arrangement by which all drivers are manually installed on each client and the printing subsystems perform no filtering or intelligent processing. Dumb printing is easily understood. It usually works without 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="id2578959"></a> - <a class="indexterm" name="id2578968"></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="id2579015"></a> - <a class="indexterm" name="id2579022"></a> - <a class="indexterm" name="id2579029"></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 @@ -566,7 +566,7 @@ clients is conservative and if followed will minimize problems but it is not ab This book is about Samba-3, so you can confine the printing style to just the smart style of installation. Those interested in further information regarding intelligent printing should review documentation on the Easy Software Products Web site. - </p></div><div class="sect3" title="Avoiding Failures: Solving Problems Before They Happen"><div class="titlepage"><div><div><h4 class="title"><a name="sbeavoid"></a>Avoiding Failures: Solving Problems Before They Happen</h4></div></div></div><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="sbeavoid"></a>Avoiding Failures: Solving Problems Before They Happen</h4></div></div></div><p> It has often been said that there are three types of people in the world: those who have sharp minds and those who forget things. Please do not ask what the third group is like! Well, it seems that many of us have company in the second group. There must @@ -574,12 +574,12 @@ 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" title="Preliminary Advice: Dangers Can Be Avoided"><div class="titlepage"><div><div><h5 class="title"><a name="id2579096"></a>Preliminary Advice: Dangers Can Be Avoided</h5></div></div></div><p> - The best advice regarding how to mend a broken leg is <span class="quote">“<span class="quote">Never break a leg!</span>”</span> + </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 “<span class="quote">Never break a leg!</span>” </p><p> - <a class="indexterm" name="id2579112"></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: <span class="quote">“<span class="quote">Avoid them like the plague!</span>”</span> + regarding the best way to remedy LDAP and Samba problems: “<span class="quote">Avoid them like the plague!</span>” </p><p> If you are now asking yourself how problems can be avoided, the best advice is to start out your learning experience with a <span class="emphasis"><em>known-good configuration.</em></span> After @@ -589,11 +589,11 @@ clients is conservative and if followed will minimize problems but it is not ab The examples in this chapter (also in the book as a whole) are known to work. That means that they could serve as the kick-off point for your journey through fields of knowledge. Use this resource carefully; we hope it serves you well. - </p><div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> + </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> 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" title="The Name Service Caching Daemon"><div class="titlepage"><div><div><h5 class="title"><a name="id2579156"></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" title="Debugging LDAP"><div class="titlepage"><div><div><h5 class="title"><a name="id2579330"></a>Debugging LDAP</h5></div></div></div><p> - <a class="indexterm" name="id2579338"></a> - <a class="indexterm" name="id2579345"></a> - <a class="indexterm" name="id2579351"></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">“LDAP DB_CONFIG File”</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="id2579387"></a> - <a class="indexterm" name="id2579394"></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" title="Debugging NSS_LDAP"><div class="titlepage"><div><div><h5 class="title"><a name="id2579436"></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" title="Procedure 5.1. NSS_LDAP Diagnostic Steps"><a name="id2579479"></a><p class="title"><b>Procedure 5.1. NSS_LDAP Diagnostic Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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. @@ -739,7 +739,7 @@ nss_base_passwd dc=abmas,dc=biz?sub will be evaluated sequentially. Let us consider an example of use where the following DIT has been implemented: </p><p> - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>User accounts are stored under the DIT: ou=Users, dc=abmas, dc=biz</p></li><li class="listitem"><p>User login accounts are under the DIT: ou=People, ou-Users, dc=abmas, dc=biz</p></li><li class="listitem"><p>Computer accounts are under the DIT: ou=Computers, ou=Users, dc=abmas, dc=biz</p></li></ul></div><p> + </p><div class="itemizedlist"><ul type="disc"><li><p>User accounts are stored under the DIT: ou=Users, dc=abmas, dc=biz</p></li><li><p>User login accounts are under the DIT: ou=People, ou-Users, dc=abmas, dc=biz</p></li><li><p>Computer accounts are under the DIT: ou=Computers, ou=Users, dc=abmas, dc=biz</p></li></ul></div><p> </p><p> The appropriate multiple entry for the <code class="constant">nss_base_passwd</code> directive in the <code class="filename">/etc/ldap.conf</code> file may be: @@ -747,7 +747,7 @@ nss_base_passwd dc=abmas,dc=biz?sub nss_base_passwd ou=People,ou=Users,dc=abmas,dc=org?one nss_base_passwd ou=Computers,ou=Users,dc=abmas,dc=org?one </pre><p> - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Perform lookups such as: </p><pre class="screen"> <code class="prompt">root# </code> getent passwd @@ -755,7 +755,7 @@ nss_base_passwd ou=Computers,ou=Users,dc=abmas,dc=org?one Each such lookup will create an entry in the <code class="filename">/data/log</code> directory for each such process executed. The contents of each file created in this directory may provide a hint as to the cause of the a problem that is under investigation. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> For additional diagnostic information, check the contents of the <code class="filename">/var/log/messages</code> to see what error messages are being generated as a result of the LDAP lookups. Here is an example of a successful lookup: @@ -788,11 +788,11 @@ nentries=2 text= slapd[12164]: conn=1 fd=10 closed </pre><p> - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> 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" title="Debugging Samba"><div class="titlepage"><div><div><h5 class="title"><a name="id2579730"></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" title="Debugging on the Windows Client"><div class="titlepage"><div><div><h5 class="title"><a name="id2579801"></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" title="Political Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2579819"></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" title="Installation Checklist"><div class="titlepage"><div><div><h3 class="title"><a name="id2579834"></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">“The 500-User Office”</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,18 +840,18 @@ 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 class="itemizedlist" type="disc"><li class="listitem"><p>Samba-3 PDC Server Configuration</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>DHCP and DNS servers</p></li><li class="listitem"><p>OpenLDAP server</p></li><li class="listitem"><p>PAM and NSS client tools</p></li><li class="listitem"><p>Samba-3 PDC</p></li><li class="listitem"><p>Idealx smbldap scripts</p></li><li class="listitem"><p>LDAP initialization</p></li><li class="listitem"><p>Create user and group accounts</p></li><li class="listitem"><p>Printers</p></li><li class="listitem"><p>Share point directory roots</p></li><li class="listitem"><p>Profile directories</p></li><li class="listitem"><p>Logon scripts</p></li><li class="listitem"><p>Configuration of user rights and privileges</p></li></ol></div></li><li class="listitem"><p>Samba-3 BDC Server Configuration</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>DHCP and DNS servers</p></li><li class="listitem"><p>PAM and NSS client tools</p></li><li class="listitem"><p>Printers</p></li><li class="listitem"><p>Share point directory roots</p></li><li class="listitem"><p>Profiles directories</p></li></ol></div></li><li class="listitem"><p>Windows XP Client Configuration</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Default profile folder redirection</p></li><li class="listitem"><p>MS Outlook PST file relocation</p></li><li class="listitem"><p>Delete roaming profile on logout</p></li><li class="listitem"><p>Upload printer drivers to Samba servers</p></li><li class="listitem"><p>Install software</p></li><li class="listitem"><p>Creation of roll-out images</p></li></ol></div></li></ul></div></div></div><div class="sect1" title="Samba Server Implementation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2580015"></a>Samba Server Implementation</h2></div></div></div><p> - <a class="indexterm" name="id2580023"></a> - <a class="indexterm" name="id2580030"></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">“Network Topology 500 User Network Using ldapsam passdb backend”</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="id2580092"></a> - <a class="indexterm" name="id2580099"></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. - </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The following information applies to Samba-3.0.20 when used with the Idealx smbldap-tools scripts version 0.9.1. If using a different version of Samba or of the smbldap-tools tarball, please verify that the versions you are about to use are matching. The smbldap-tools package @@ -867,23 +867,23 @@ They could just as well be located under the rdn <code class="constant">cn=NextF have completed the network implementation shown in that chapter. If you are starting 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">“Installation of DHCP, DNS, and Samba Control Files”</a> before commencing at <a class="link" href="happy.html#ldapsetup" title="OpenLDAP Server Configuration">“OpenLDAP Server Configuration”</a>. - </p><div class="sect2" title="OpenLDAP Server Configuration"><div class="titlepage"><div><div><h3 class="title"><a name="ldapsetup"></a>OpenLDAP Server Configuration</h3></div></div></div><p> - <a class="indexterm" name="id2580181"></a> - <a class="indexterm" name="id2580187"></a> - <a class="indexterm" name="id2580194"></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="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">“Required OpenLDAP Linux Packages”</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" title="Procedure 5.2. OpenLDAP Server Configuration Steps"><a name="id2580326"></a><p class="title"><b>Procedure 5.2. OpenLDAP Server Configuration Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2580338"></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">“LDAP Master Configuration File /etc/openldap/slapd.conf Part A”</a> in the directory <code class="filename">/etc/openldap</code>. - </p></li><li class="step" title="Step 2"><p> - <a class="indexterm" name="id2580366"></a> - <a class="indexterm" name="id2580373"></a> - <a class="indexterm" name="id2580380"></a> + </p></li><li><p> + <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"> @@ -891,19 +891,19 @@ They could just as well be located under the rdn <code class="constant">cn=NextF 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 class="step" title="Step 3"><p> - <a class="indexterm" name="id2580415"></a> + </p></li><li><p> + <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">“LDAP DB_CONFIG File”</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 class="step" title="Step 4"><p> - <a class="indexterm" name="id2580468"></a> + </p></li><li><p> + <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 - the <code class="filename">/etc/openldap/slapd.conf</code> shown as <span class="quote">“<span class="quote">loglevel 256</span>”</span>. + the <code class="filename">/etc/openldap/slapd.conf</code> shown as “<span class="quote">loglevel 256</span>”. </p><p> Edit the <code class="filename">/etc/syslog.conf</code> file to add the following at the end of the file: @@ -974,32 +974,32 @@ index sambaSID eq index sambaPrimaryGroupSID eq index sambaDomainName eq index default sub -</pre></div></div><br class="example-break"></div><div class="sect2" title="PAM and NSS Client Configuration"><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="id2580627"></a> - <a class="indexterm" name="id2580634"></a> - <a class="indexterm" name="id2580640"></a> +</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="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="id2580655"></a> - <a class="indexterm" name="id2580664"></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="id2580693"></a> - <a class="indexterm" name="id2580699"></a> - <a class="indexterm" name="id2580706"></a> - <a class="indexterm" name="id2580713"></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> → <span class="guimenuitem">system</span> → <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" title="Procedure 5.3. PAM and NSS Client Configuration Steps"><a name="id2580753"></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 @@ -1041,23 +1041,23 @@ nss_base_shadow ou=People,dc=abmas,dc=biz?one nss_base_group ou=Groups,dc=abmas,dc=biz?one ssl off -</pre></div></div><br class="example-break"><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2580764"></a> - <a class="indexterm" name="id2580772"></a> - <a class="indexterm" name="id2580778"></a> +</pre></div></div><br class="example-break"><ol type="1"><li><p> + <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"> <code class="prompt">root# </code> strings /lib/libnss_ldap.so.2 | grep conf </pre><p> The preferred and usual location is <code class="filename">/etc/ldap.conf</code>. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> On the server <code class="constant">MASSIVE</code>, install the file shown in <a class="link" href="happy.html#sbehap-nss01" title="Example 5.4. Configuration File for NSS LDAP Support /etc/ldap.conf">“Configuration File for NSS LDAP Support /etc/ldap.conf”</a> into the path that was obtained from the step above. 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">“Configuration File for NSS LDAP Clients Support /etc/ldap.conf”</a> into the path that was obtained from the step above. - </p></li><li class="step" title="Step 3"><p> - <a class="indexterm" name="id2580912"></a> + </p></li><li><p> + <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>: @@ -1071,7 +1071,7 @@ hosts: files dns wins added, you can validate resolution of the LDAP resolver process. The inclusion of WINS-based hostname resolution is deliberate so that all MS Windows client hostnames can be resolved to their IP addresses, whether or not they are DHCP clients. - </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Some Linux systems (Novell SUSE Linux in particular) add entries to the <code class="filename">nsswitch.conf</code> file that may cause operational problems with the configuration methods adopted in this book. It is advisable to comment out the entries <code class="constant">passwd_compat</code> and <code class="constant">group_compat</code> @@ -1079,8 +1079,8 @@ hosts: files dns wins </p></div><p> 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 class="step" title="Step 4"><p> - <a class="indexterm" name="id2580988"></a> + </p></li><li><p> + <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="id2581067"></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"> @@ -1125,15 +1125,15 @@ session optional pam_mail.so demonstrates the use of the <code class="literal">pam_ldap.so</code> module. You can use either 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" title="Samba-3 PDC Configuration"><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="id2581150"></a> + </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="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" title="Procedure 5.4. Configuration of PDC Called MASSIVE"><a name="id2581166"></a><p class="title"><b>Procedure 5.4. Configuration of PDC Called <code class="constant">MASSIVE</code></b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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">“LDAP Based smb.conf File, Server: MASSIVE global Section: Part A”</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">“LDAP Based smb.conf File, Server: MASSIVE global Section: Part B”</a>, <a class="link" href="happy.html#sbehap-shareconfa" title="Example 5.10. LDAP Based smb.conf File, Shares Section Part A">“LDAP Based smb.conf File, Shares Section Part A”</a>, and <a class="link" href="happy.html#sbehap-shareconfb" title="Example 5.11. LDAP Based smb.conf File, Shares Section Part B">“LDAP Based smb.conf File, Shares Section Part B”</a> into the <code class="filename">/etc/samba/</code> @@ -1142,8 +1142,8 @@ session optional pam_mail.so <code class="filename">smb.conf.master</code> and then to perform all file edits on the master file. The operational <code class="filename">smb.conf</code> is then generated as shown in the next step. - </p></li><li class="step" title="Step 2"><p> - <a class="indexterm" name="id2581242"></a> + </p></li><li><p> + <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 > smb.conf @@ -1170,7 +1170,7 @@ Loaded services file OK. Server role: ROLE_DOMAIN_PDC Press enter to see a dump of your service definitions </pre><p> - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Delete all runtime files from prior Samba operation by executing (for SUSE Linux): </p><pre class="screen"> @@ -1179,9 +1179,9 @@ Press enter to see a dump of your service definitions <code class="prompt">root# </code> rm /var/lib/samba/*dat <code class="prompt">root# </code> rm /var/log/samba/* </pre><p> - </p></li><li class="step" title="Step 4"><p> - <a class="indexterm" name="id2581342"></a> - <a class="indexterm" name="id2581348"></a> + </p></li><li><p> + <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 @@ -1193,9 +1193,9 @@ Press enter to see a dump of your service definitions </p><pre class="screen"> Setting stored password for "cn=Manager,dc=abmas,dc=biz" in secrets.tdb </pre><p> - </p></li><li class="step" title="Step 5"><p> - <a class="indexterm" name="id2581397"></a> - <a class="indexterm" name="id2581404"></a> + </p></li><li><p> + <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: @@ -1226,13 +1226,13 @@ SID for domain MASSIVE is: S-1-5-21-3504140859-1010554828-2431957765 may be misconfigured. In this case, carefully check the <code class="filename">smb.conf</code> file for typographical errors (the most common problem). The use of the <code class="literal">testparm</code> is highly recommended to validate the contents of this file. - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> When a positive domain SID has been reported, stop Samba. - </p></li><li class="step" title="Step 7"><p> - <a class="indexterm" name="id2581516"></a> - <a class="indexterm" name="id2581523"></a> - <a class="indexterm" name="id2581530"></a> - <a class="indexterm" name="id2581536"></a> + </p></li><li><p> + <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 border="0" summary="Simple list" class="simplelist"><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="id2581623"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2581635"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2581646"></a><em class="parameter"><code>netbios name = MASSIVE</code></em></td></tr><tr><td><a class="indexterm" name="id2581658"></a><em class="parameter"><code>interfaces = eth1, lo</code></em></td></tr><tr><td><a class="indexterm" name="id2581670"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2581682"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2581694"></a><em class="parameter"><code>enable privileges = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2581706"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2581718"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2581730"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2581741"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2581753"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2581765"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2581776"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2581788"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2581800"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2581812"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2581824"></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="id2581836"></a><em class="parameter"><code>delete user script = /opt/IDEALX/sbin/smbldap-userdel "%u"</code></em></td></tr><tr><td><a class="indexterm" name="id2581849"></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="id2581861"></a><em class="parameter"><code>delete group script = /opt/IDEALX/sbin/smbldap-groupdel "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2581874"></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="id2581887"></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="id2581900"></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="id2581913"></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 border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id2581950"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2581962"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2581974"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2581986"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2581997"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2582009"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2582021"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2582033"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2582045"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2582057"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2582069"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2582081"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2582093"></a><em class="parameter"><code>idmap backend = ldap:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2582105"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2582117"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2582129"></a><em class="parameter"><code>map acl inherit = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2582141"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2582152"></a><em class="parameter"><code>printer admin = root, chrisr</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" title="Install and Configure Idealx smbldap-tools Scripts"><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="id2582178"></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 @@ -1261,16 +1261,16 @@ SID for domain MASSIVE is: S-1-5-21-3504140859-1010554828-2431957765 from this site also. Alternatively, you may obtain the <a class="ulink" href="http://samba.idealx.org/dist/smbldap-tools-0.9.1-1.src.rpm" target="_top">smbldap-tools-0.9.1-1.src.rpm</a> file that may be used to build an installable RPM package for your Linux system. - </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The smbldap-tools scripts can be installed in any convenient directory of your choice, in which case you must change the path to them in your <code class="filename">smb.conf</code> file on the PDC (<code class="constant">MASSIVE</code>). </p></div><p> 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" title="Installation of smbldap-tools from the Tarball"><div class="titlepage"><div><div><h4 class="title"><a name="id2582245"></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" title="Procedure 5.5. Unpacking and Installation Steps for the smbldap-tools Tarball"><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 class="procedure" type="1"><li class="step" title="Step 1"><p> + </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 and ownership as shown here: </p><pre class="screen"> @@ -1281,11 +1281,11 @@ change the path to them in your <code class="filename">smb.conf</code> file on t <code class="prompt">root# </code> chown root:root /etc/smbldap-tools <code class="prompt">root# </code> chmod 755 /etc/smbldap-tools </pre><p> - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> If you wish to use the downloaded tarball, unpack the smbldap-tools in a suitable temporary location. Change into either the directory extracted from the tarball or the smbldap-tools directory in your <code class="filename">/usr/share/doc/packages</code> directory tree. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Copy all the <code class="filename">smbldap-*</code> and the <code class="filename">configure.pl</code> files into the <code class="filename">/opt/IDEALX/sbin</code> directory, as shown here: </p><pre class="screen"> @@ -1297,7 +1297,7 @@ change the path to them in your <code class="filename">smb.conf</code> file on t <code class="prompt">root# </code> chmod 640 /etc/smbldap-tools/smbldap.conf <code class="prompt">root# </code> chmod 600 /etc/smbldap-tools/smbldap_bind.conf </pre><p> - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> The smbldap-tools scripts master control file must now be configured. Change to the <code class="filename">/opt/IDEALX/sbin</code> directory, then edit the <code class="filename">smbldap_tools.pm</code> to affect the changes @@ -1310,7 +1310,7 @@ my $smbldap_conf="/etc/smbldap-tools/smbldap.conf"; my $smbldap_bind_conf="/etc/smbldap-tools/smbldap_bind.conf"; ... </pre><p> - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> To complete the configuration of the smbldap-tools, set the permissions and ownership by executing the following commands: </p><pre class="screen"> @@ -1320,15 +1320,15 @@ 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">“Configuration of smbldap-tools”</a>. - </p></li></ol></div></div><div class="sect3" title="Installing smbldap-tools from the RPM Package"><div class="titlepage"><div><div><h4 class="title"><a name="id2582498"></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" title="Procedure 5.6. Installation Steps for smbldap-tools RPM's"><a name="id2582516"></a><p class="title"><b>Procedure 5.6. Installation Steps for <code class="constant">smbldap-tools</code> RPM's</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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 </pre><p> - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Change into the directory in which the SPEC files are located. On SUSE Linux: </p><pre class="screen"> <code class="prompt">root# </code> cd /usr/src/packages/SPECS @@ -1337,7 +1337,7 @@ my $smbldap_bind_conf="/etc/smbldap-tools/smbldap_bind.conf"; </p><pre class="screen"> <code class="prompt">root# </code> cd /usr/src/redhat/SPECS </pre><p> - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Edit the <code class="filename">smbldap-tools.spec</code> file to change the value of the <code class="constant">_sysconfig</code> macro as shown here: </p><pre class="screen"> @@ -1345,14 +1345,14 @@ my $smbldap_bind_conf="/etc/smbldap-tools/smbldap_bind.conf"; %define _sysconfdir /etc </pre><p> Note: Any suitable directory can be specified. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Build the package by executing: </p><pre class="screen"> <code class="prompt">root# </code> rpmbuild -ba -v smbldap-tools.spec </pre><p> A build process that has completed without error will place the installable binary files in the directory <code class="filename">../RPMS/noarch</code>. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> Install the binary package by executing: </p><pre class="screen"> <code class="prompt">root# </code> rpm -Uvh ../RPMS/noarch/smbldap-tools-0.9.1-1.noarch.rpm @@ -1360,7 +1360,7 @@ my $smbldap_bind_conf="/etc/smbldap-tools/smbldap_bind.conf"; </p></li></ol></div><p> The Idealx scripts should now be ready for configuration using the steps outlined in <a class="link" href="happy.html#smbldap-init" title="Configuration of smbldap-tools">Configuration of smbldap-tools</a>. - </p></div><div class="sect3" title="Configuration of smbldap-tools"><div class="titlepage"><div><div><h4 class="title"><a name="smbldap-init"></a>Configuration of smbldap-tools</h4></div></div></div><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="smbldap-init"></a>Configuration of smbldap-tools</h4></div></div></div><p> Prior to use, the smbldap-tools must be configured to match the settings in the <code class="filename">smb.conf</code> file and to match the settings in the <code class="filename">/etc/openldap/slapd.conf</code> file. The assumption is made that the <code class="filename">smb.conf</code> file has correct contents. The following procedure ensures that @@ -1368,12 +1368,12 @@ 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" title="Procedure 5.7. Configuration Steps for smbldap-tools to Enable Use"><a name="id2582711"></a><p class="title"><b>Procedure 5.7. Configuration Steps for <code class="constant">smbldap-tools</code> to Enable Use</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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 </pre><p> - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Execute the <code class="filename">configure.pl</code> script as follows: </p><pre class="screen"> <code class="prompt">root# </code> ./configure.pl @@ -1469,12 +1469,12 @@ writing new configuration file: Since a slave LDAP server has not been configured, it is necessary to specify the IP address of the master LDAP server for both the master and the slave configuration prompts. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Change to the directory that contains the <code class="filename">smbldap.conf</code> file, then verify its contents. </p></li></ol></div><p> The smbldap-tools are now ready for use. - </p></div></div><div class="sect2" title="LDAP Initialization and Creation of User and Group Accounts"><div class="titlepage"><div><div><h3 class="title"><a name="id2582912"></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> @@ -1486,13 +1486,13 @@ writing new configuration file: does not need to ask LDAP. </p><p> Addition of an account to the LDAP backend can be done in two ways: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> - <a class="indexterm" name="id2582946"></a> - <a class="indexterm" name="id2582953"></a> - <a class="indexterm" name="id2582960"></a> - <a class="indexterm" name="id2582966"></a> - <a class="indexterm" name="id2582973"></a> - <a class="indexterm" name="id2582980"></a> + </p><div class="itemizedlist"><ul type="disc"><li><p> + <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 @@ -1503,27 +1503,27 @@ writing new configuration file: expects the POSIX account to be in LDAP also. It is possible to use the PADL account migration tool to migrate all system accounts from either the <code class="filename">/etc/passwd</code> files, or from NIS, to LDAP. - </p></li><li class="listitem"><p> + </p></li><li><p> If you decide that it is probably a good idea to add both the PosixAccount attributes as well as the SambaSamAccount attributes for each user, then a suitable script is needed. In the example system you are installing in this exercise, you are making use of the 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="id2583040"></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">“A Collection of Useful Tidbits”</a>, <a class="link" href="appendix.html#altldapcfg" title="Alternative LDAP Database Initialization">“Alternative LDAP Database Initialization”</a>. </p><p> - <a class="indexterm" name="id2583067"></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">“Abmas Network Users and Groups”</a>. The list of users does not cover all 500 network users; it provides examples only. - </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - <a class="indexterm" name="id2583097"></a> - <a class="indexterm" name="id2583106"></a> - <a class="indexterm" name="id2583115"></a> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + <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 @@ -1540,15 +1540,15 @@ writing new configuration file: can be found. Alternatively, by placing all machine accounts in the People container, we are able to sidestep this limitation. This is the simpler solution that has been adopted in this chapter. - </p></div><div class="table"><a name="sbehap-bigacct"></a><p class="title"><b>Table 5.3. Abmas Network Users and Groups</b></p><div class="table-contents"><table summary="Abmas Network Users and Groups" border="1"><colgroup><col align="left"><col align="left"><col align="left"><col align="left"></colgroup><thead><tr><th align="center">Account Name</th><th align="center">Type</th><th align="center">ID</th><th align="center">Password</th></tr></thead><tbody><tr><td align="left">Robert Jordan</td><td align="left">User</td><td align="left">bobj</td><td align="left">n3v3r2l8</td></tr><tr><td align="left">Stanley Soroka</td><td align="left">User</td><td align="left">stans</td><td align="left">impl13dst4r</td></tr><tr><td align="left">Christine Roberson</td><td align="left">User</td><td align="left">chrisr</td><td align="left">S9n0nw4ll</td></tr><tr><td align="left">Mary Vortexis</td><td align="left">User</td><td align="left">maryv</td><td align="left">kw13t0n3</td></tr><tr><td align="left">Accounts</td><td align="left">Group</td><td align="left">Accounts</td><td align="left"> </td></tr><tr><td align="left">Finances</td><td align="left">Group</td><td align="left">Finances</td><td align="left"> </td></tr><tr><td align="left">Insurance</td><td align="left">Group</td><td align="left">PIOps</td><td align="left"> </td></tr></tbody></table></div></div><br class="table-break"><div class="procedure" title="Procedure 5.8. LDAP Directory Initialization Steps"><a name="creatacc"></a><p class="title"><b>Procedure 5.8. LDAP Directory Initialization Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> + </p></div><div class="table"><a name="sbehap-bigacct"></a><p class="title"><b>Table 5.3. Abmas Network Users and Groups</b></p><div class="table-contents"><table summary="Abmas Network Users and Groups" border="1"><colgroup><col align="left"><col align="left"><col align="left"><col align="left"></colgroup><thead><tr><th align="center">Account Name</th><th align="center">Type</th><th align="center">ID</th><th align="center">Password</th></tr></thead><tbody><tr><td align="left">Robert Jordan</td><td align="left">User</td><td align="left">bobj</td><td align="left">n3v3r2l8</td></tr><tr><td align="left">Stanley Soroka</td><td align="left">User</td><td align="left">stans</td><td align="left">impl13dst4r</td></tr><tr><td align="left">Christine Roberson</td><td align="left">User</td><td align="left">chrisr</td><td align="left">S9n0nw4ll</td></tr><tr><td align="left">Mary Vortexis</td><td align="left">User</td><td align="left">maryv</td><td align="left">kw13t0n3</td></tr><tr><td align="left">Accounts</td><td align="left">Group</td><td align="left">Accounts</td><td align="left"> </td></tr><tr><td align="left">Finances</td><td align="left">Group</td><td align="left">Finances</td><td align="left"> </td></tr><tr><td align="left">Insurance</td><td align="left">Group</td><td align="left">PIOps</td><td align="left"> </td></tr></tbody></table></div></div><br class="table-break"><div class="procedure"><a name="creatacc"></a><p class="title"><b>Procedure 5.8. LDAP Directory Initialization Steps</b></p><ol type="1"><li><p> Start the LDAP server by executing: </p><pre class="screen"> <code class="prompt">root# </code> rcldap start Starting ldap-server done </pre><p> - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Change to the <code class="filename">/opt/IDEALX/sbin</code> directory. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Execute the script that will populate the LDAP database as shown here: </p><pre class="screen"> <code class="prompt">root# </code> ./smbldap-populate -a root -k 0 -m 0 @@ -1579,7 +1579,7 @@ adding new entry: cn=Print Operators,ou=Groups,dc=abmas,dc=biz adding new entry: cn=Backup Operators,ou=Groups,dc=abmas,dc=biz adding new entry: cn=Replicators,ou=Groups,dc=abmas,dc=biz </pre><p> - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Edit the <code class="filename">/etc/smbldap-tools/smbldap.conf</code> file so that the following information is changed from: </p><pre class="screen"> @@ -1592,15 +1592,15 @@ sambaUnixIdPooldn="cn=NextFreeUnixId,${suffix}" #sambaUnixIdPooldn="cn=NextFreeUnixId,${suffix}" sambaUnixIdPooldn="sambaDomainName=MEGANET2,dc=abmas,dc=biz" </pre><p> - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> It is necessary to restart the LDAP server as shown here: </p><pre class="screen"> <code class="prompt">root# </code> rcldap restart Shutting down ldap-server done Starting ldap-server done </pre><p> - </p></li><li class="step" title="Step 6"><p> - <a class="indexterm" name="id2583535"></a> + </p></li><li><p> + <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="id2583558"></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">“LDIF IDMAP Add-On Load File File: /etc/openldap/idmap.LDIF”</a>). You can add the required entries using the following command: @@ -1618,8 +1618,8 @@ ou: idmap -w not24get < /etc/openldap/idmap.LDIF </pre><p> Samba automatically populates this LDAP directory container when it needs to. - </p></li><li class="step" title="Step 7"><p> - <a class="indexterm" name="id2583598"></a> + </p></li><li><p> + <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): @@ -1656,8 +1656,8 @@ modifiersName: cn=Manager,dc=abmas,dc=biz modifyTimestamp: 20031217234206Z </pre><p> This looks good so far. - </p></li><li class="step" title="Step 8"><p> - <a class="indexterm" name="id2583649"></a> + </p></li><li><p> + <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"> @@ -1701,8 +1701,8 @@ result: 0 Success # numEntries: 19 </pre><p> Good. It is all working just fine. - </p></li><li class="step" title="Step 9"><p> - <a class="indexterm" name="id2583706"></a> + </p></li><li><p> + <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="id2583736"></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">“Avoiding Failures: Solving Problems Before They Happen”</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 class="step" title="Step 10"><p> - <a class="indexterm" name="id2583766"></a> - <a class="indexterm" name="id2583773"></a> - <a class="indexterm" name="id2583780"></a> + </p></li><li><p> + <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"> @@ -1739,8 +1739,8 @@ New SMB password: XXXXXXXX Retype new SMB password: XXXXXXXX </pre><p> where <code class="constant">username</code> is the login ID for each user. - </p></li><li class="step" title="Step 11"><p> - <a class="indexterm" name="id2583841"></a> + </p></li><li><p> + <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"> @@ -1756,7 +1756,7 @@ chrisr:x:1002:513:System User:/home/chrisr:/bin/bash maryv:x:1003:513:System User:/home/maryv:/bin/bash </pre><p> This demonstrates that user account resolution via LDAP is working. - </p></li><li class="step" title="Step 12"><p> + </p></li><li><p> This step will determine whether or not identity resolution is working correctly. Do not procede is this step fails, rather find the cause of the failure. The <code class="literal">id</code> command may be used to validate your configuration so far, @@ -1767,8 +1767,8 @@ uid=1002(chrisr) gid=513(Domain Users) groups=513(Domain Users) </pre><p> 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 class="step" title="Step 13"><p> - <a class="indexterm" name="id2583907"></a> + </p></li><li><p> + <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 @@ -1779,7 +1779,7 @@ uid=1002(chrisr) gid=513(Domain Users) groups=513(Domain Users) <code class="prompt">root# </code> cd /opt/IDEALX/sbin <code class="prompt">root# </code> ./smbldap-usermod -u 0 -d /root -s /bin/bash root </pre><p> - </p></li><li class="step" title="Step 14"><p> + </p></li><li><p> Verify that the changes just made to the <code class="constant">root</code> account were accepted by executing: </p><pre class="screen"> @@ -1788,7 +1788,7 @@ root:x:0:0:root:/root:/bin/bash root:x:0:512:Netbios Domain Administrator:/root:/bin/bash </pre><p> This demonstrates that the changes were accepted. - </p></li><li class="step" title="Step 15"><p> + </p></li><li><p> Make certain that a home directory has been created for every user by listing the directories in <code class="filename">/home</code> as follows: </p><pre class="screen"> @@ -1801,9 +1801,9 @@ drwx------ 7 maryv Domain Users 568 Dec 17 01:27 maryv/ drwx------ 7 stans Domain Users 568 Dec 17 01:43 stans/ </pre><p> This is precisely what we want to see. - </p></li><li class="step" title="Step 16"><p> - <a class="indexterm" name="id2584006"></a> - <a class="indexterm" name="id2584013"></a> + </p></li><li><p> + <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"> @@ -1833,8 +1833,8 @@ Bad password count : 0 Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF </pre><p> This looks good. Of course, you fully expected that it would all work, didn't you? - </p></li><li class="step" title="Step 17"><p> - <a class="indexterm" name="id2584058"></a> + </p></li><li><p> + <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"> @@ -1844,8 +1844,8 @@ Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF </pre><p> The addition of groups does not involve keyboard interaction, so the lack of console output is of no concern. - </p></li><li class="step" title="Step 18"><p> - <a class="indexterm" name="id2584100"></a> + </p></li><li><p> + <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"> @@ -1861,8 +1861,8 @@ PIOps:x:1002: </pre><p> 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 class="step" title="Step 19"><p> - <a class="indexterm" name="id2584133"></a> + </p></li><li><p> + <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: @@ -1879,7 +1879,7 @@ PIOps (S-1-5-21-3504140859-1010554828-2431957765-3005) -> PIOps This is looking good. Congratulations it works! Note that in the above output the lines were shortened by replacing the middle value (1010554828) of the SID with the ellipsis (...). - </p></li><li class="step" title="Step 20"><p> + </p></li><li><p> The server you have so carefully built is now ready for another important step. You start the Samba-3 server and validate its operation. Execute the following to render all the processes needed fully operative so that, on system reboot, they are automatically @@ -1895,7 +1895,7 @@ PIOps (S-1-5-21-3504140859-1010554828-2431957765-3005) -> PIOps <code class="prompt">root# </code> rcsmb start <code class="prompt">root# </code> rcwinbind start </pre><p> - </p></li><li class="step" title="Step 21"><p> + </p></li><li><p> The next step might seem a little odd at this point, but take note that you are about to start <code class="literal">winbindd</code>, which must be able to authenticate to the PDC via the localhost interface with the <code class="literal">smbd</code> process. This account can be @@ -1910,14 +1910,14 @@ PIOps (S-1-5-21-3504140859-1010554828-2431957765-3005) -> PIOps Joined domain MEGANET2. </pre><p> This indicates that the domain security account for the PDC has been correctly created. - </p></li><li class="step" title="Step 22"><p> + </p></li><li><p> At this time it is necessary to restart <code class="literal">winbindd</code> so that it can correctly authenticate to the PDC. The following command achieves that: </p><pre class="screen"> <code class="prompt">root# </code> rcwinbind restart </pre><p> - </p></li><li class="step" title="Step 23"><p> - <a class="indexterm" name="id2584348"></a> + </p></li><li><p> + <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% @@ -1943,7 +1943,7 @@ Joined domain MEGANET2. MEGANET2 MASSIVE </pre><p> This shows that an anonymous connection is working. - </p></li><li class="step" title="Step 24"><p> + </p></li><li><p> For your finale, let's try an authenticated connection: </p><pre class="screen"> <code class="prompt">root# </code> smbclient //massive/bobj -Ubobj%n3v3r2l8 @@ -1962,47 +1962,47 @@ smb: \> q Well done. All is working fine. </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" title="Printer Configuration"><div class="titlepage"><div><div><h3 class="title"><a name="sbehap-ptrcfg"></a>Printer Configuration</h3></div></div></div><p> - <a class="indexterm" name="id2584459"></a> + </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="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" title="Procedure 5.9. Printer Configuration Steps"><a name="id2584481"></a><p class="title"><b>Procedure 5.9. Printer Configuration Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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 class="step" title="Step 2"><p> + </p></li><li><p> Create an entry in the DNS database on the server <code class="constant">MASSIVE</code> in both the forward lookup database for the zone <code class="constant">abmas.biz.hosts</code> and in the reverse lookup database for the network segment that the printer is to be located in. Example configuration files for similar zones were presented in <a class="link" href="secure.html" title="Chapter 3. Secure Office Networking">“Secure Office Networking”</a>, <a class="link" href="secure.html#abmasbiz" title="Example 3.14. DNS Abmas.biz Forward Zone File">“DNS Abmas.biz Forward Zone File”</a> and in <a class="link" href="secure.html#eth2zone" title="Example 3.13. DNS 192.168.2 Reverse Zone File">“DNS 192.168.2 Reverse Zone File”</a>. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> 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="id2584542"></a> - <a class="indexterm" name="id2584549"></a> - </p></li><li class="step" title="Step 4"><p> - <a class="indexterm" name="id2584563"></a> - <a class="indexterm" name="id2584569"></a> + <a class="indexterm" name="id2578457"></a> + <a class="indexterm" name="id2578464"></a> + </p></li><li><p> + <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="id2584605"></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 the particular printer. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> Print queues may not be enabled at creation. Make certain that the queues you have just created are enabled by executing the following: </p><pre class="screen"> <code class="prompt">root# </code> /usr/bin/enable <em class="parameter"><code>printque</code></em> </pre><p> - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> Even though your print queue may be enabled, it is still possible that it may not accept print jobs. A print queue will service incoming printing requests only when configured to do so. Ensure that your print queue is @@ -2010,27 +2010,27 @@ smb: \> q </p><pre class="screen"> <code class="prompt">root# </code> /usr/bin/accept <em class="parameter"><code>printque</code></em> </pre><p> - </p></li><li class="step" title="Step 7"><p> - <a class="indexterm" name="id2584686"></a> - <a class="indexterm" name="id2584693"></a> - <a class="indexterm" name="id2584700"></a> + </p></li><li><p> + <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 class="step" title="Step 8"><p> - <a class="indexterm" name="id2584729"></a> + </p></li><li><p> + <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 </pre><p> - </p></li><li class="step" title="Step 9"><p> + </p></li><li><p> Refer to the CUPS printing manual for instructions regarding how to configure CUPS so that print queues that reside on CUPS servers on remote networks route print jobs to the print server that owns that queue. The default setting on your CUPS server may automatically discover remotely installed printers and may permit this functionality without requiring specific configuration. - </p></li><li class="step" title="Step 10"><p> + </p></li><li><p> The following action creates the necessary directory subsystem. Follow these steps to printing heaven: </p><pre class="screen"> @@ -2038,17 +2038,17 @@ 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" title="Samba-3 BDC Configuration"><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" title="Procedure 5.10. Configuration of BDC Called: BLDG1"><a name="id2584812"></a><p class="title"><b>Procedure 5.10. Configuration of BDC Called: <code class="constant">BLDG1</code></b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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">“LDAP Based smb.conf File, Server: BLDG1”</a>, <a class="link" href="happy.html#sbehap-shareconfa" title="Example 5.10. LDAP Based smb.conf File, Shares Section Part A">“LDAP Based smb.conf File, Shares Section Part A”</a>, and <a class="link" href="happy.html#sbehap-shareconfb" title="Example 5.11. LDAP Based smb.conf File, Shares Section Part B">“LDAP Based smb.conf File, Shares Section Part B”</a> into the <code class="filename">/etc/samba/</code> directory. The three files should be added together to form the <code class="filename">smb.conf</code> file. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Verify the <code class="filename">smb.conf</code> file as in step 2 of <a class="link" href="happy.html#sbehap-massive" title="Samba-3 PDC Configuration">“Samba-3 PDC Configuration”</a>. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Carefully follow the steps outlined in <a class="link" href="happy.html#sbehap-PAM-NSS" title="PAM and NSS Client Configuration">“PAM and NSS Client Configuration”</a>, taking particular note to install the correct <code class="filename">ldap.conf</code>. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Verify that the NSS resolver is working. You may need to cycle the run level to 1 and back to 5 before the NSS LDAP resolver functions. Follow these commands: @@ -2080,8 +2080,8 @@ vaioboss$:x:1005:553:vaioboss$:/dev/null:/bin/false 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 class="step" title="Step 5"><p> - <a class="indexterm" name="id2584972"></a> + </p></li><li><p> + <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"> @@ -2110,15 +2110,15 @@ PIOps:x:1002: </pre><p> 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 class="step" title="Step 6"><p> - <a class="indexterm" name="id2585013"></a> + </p></li><li><p> + <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"> <code class="prompt">root# </code> smbpasswd -w not24get Setting stored password for "cn=Manager,dc=abmas,dc=biz" in secrets.tdb </pre><p> - </p></li><li class="step" title="Step 7"><p> + </p></li><li><p> Now you must obtain the domain SID from the PDC and store it into the <code class="filename">secrets.tdb</code> file also. This step is not necessary with an LDAP passdb backend because Samba-3 obtains the domain SID from the @@ -2135,15 +2135,15 @@ Storing SID S-1-5-21-3504140859-1010554828-2431957765 \ domain controller that is running on the localhost and must be able to authenticate, thus requiring that the BDC should be joined to the domain. The process of joining the domain creates the necessary authentication accounts. - </p></li><li class="step" title="Step 8"><p> + </p></li><li><p> To join the Samba BDC to the domain, execute the following: </p><pre class="screen"> <code class="prompt">root# </code> net rpc join -U root%not24get Joined domain MEGANET2. </pre><p> This indicates that the domain security account for the BDC has been correctly created. - </p></li><li class="step" title="Step 9"><p> - <a class="indexterm" name="id2585114"></a> + </p></li><li><p> + <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 @@ -2169,7 +2169,7 @@ Finances (S-1-5-21-3504140859-1010554828-2431957765-3003) -> Finances PIOps (S-1-5-21-3504140859-1010554828-2431957765-3005) -> PIOps </pre><p> These results show that all things are in order. - </p></li><li class="step" title="Step 10"><p> + </p></li><li><p> The server you have so carefully built is now ready for another important step. Now start the Samba-3 server and validate its operation. Execute the following to render all the processes needed fully operative so that, upon system reboot, they are automatically @@ -2185,7 +2185,7 @@ PIOps (S-1-5-21-3504140859-1010554828-2431957765-3005) -> PIOps <code class="prompt">root# </code> rcwinbind start </pre><p> Samba-3 should now be running and is ready for a quick test. But not quite yet! - </p></li><li class="step" title="Step 11"><p> + </p></li><li><p> Your new <code class="constant">BLDG1, BLDG2</code> servers do not have home directories for users. To rectify this using the SUSE yast2 utility or by manually editing the <code class="filename">/etc/fstab</code> file, add a mount entry to mount the <code class="constant">home</code> directory that has been exported @@ -2205,7 +2205,7 @@ massive.abmas.biz:/home /home nfs rw 0 0 <code class="prompt">root# </code> df | grep home massive:/home 29532988 283388 29249600 1% /home </pre><p> - </p></li><li class="step" title="Step 12"><p> + </p></li><li><p> Implement a quick check using one of the users that is in the LDAP database. Here you go: </p><pre class="screen"> <code class="prompt">root# </code> smbclient //bldg1/bobj -Ubobj%n3v3r2l8 @@ -2224,26 +2224,26 @@ smb: \> q </p></li></ol></div><p> Now that the first BDC (<code class="constant">BDLG1</code>) has been configured it is time to build and configure the second BDC server (<code class="constant">BLDG2</code>) as follows: - </p><div class="procedure" title="Procedure 5.11. Configuration of BDC Called BLDG2"><a name="sbehap-bldg2"></a><p class="title"><b>Procedure 5.11. Configuration of BDC Called <code class="constant">BLDG2</code></b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> + </p><div class="procedure"><a name="sbehap-bldg2"></a><p class="title"><b>Procedure 5.11. Configuration of BDC Called <code class="constant">BLDG2</code></b></p><ol type="1"><li><p> Install the files in <a class="link" href="happy.html#sbehap-bldg2-smbconf" title="Example 5.9. LDAP Based smb.conf File, Server: BLDG2">“LDAP Based smb.conf File, Server: BLDG2”</a>, <a class="link" href="happy.html#sbehap-shareconfa" title="Example 5.10. LDAP Based smb.conf File, Shares Section Part A">“LDAP Based smb.conf File, Shares Section Part A”</a>, and <a class="link" href="happy.html#sbehap-shareconfb" title="Example 5.11. LDAP Based smb.conf File, Shares Section Part B">“LDAP Based smb.conf File, Shares Section Part B”</a> into the <code class="filename">/etc/samba/</code> directory. The three files should be added together to form the <code class="filename">smb.conf</code> file. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Follow carefully the steps shown in <a class="link" href="happy.html#sbehap-bldg1" title="Samba-3 BDC Configuration">“Samba-3 BDC Configuration”</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 border="0" summary="Simple list" class="simplelist"><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="id2585460"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2585472"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2585484"></a><em class="parameter"><code>netbios name = BLDG1</code></em></td></tr><tr><td><a class="indexterm" name="id2585496"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2585508"></a><em class="parameter"><code>enable privileges = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2585520"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2585532"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2585543"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2585555"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2585567"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2585578"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2585590"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2585602"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2585614"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2585626"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2585638"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2585650"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2585662"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2585673"></a><em class="parameter"><code>domain master = No</code></em></td></tr><tr><td><a class="indexterm" name="id2585685"></a><em class="parameter"><code>wins server = 172.16.0.1</code></em></td></tr><tr><td><a class="indexterm" name="id2585697"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2585709"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2585721"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2585733"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2585745"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2585757"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2585769"></a><em class="parameter"><code>idmap backend = ldap:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2585781"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2585793"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2585804"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2585816"></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 border="0" summary="Simple list" class="simplelist"><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="id2585863"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2585874"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2585886"></a><em class="parameter"><code>netbios name = BLDG2</code></em></td></tr><tr><td><a class="indexterm" name="id2585898"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2585910"></a><em class="parameter"><code>enable privileges = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2585922"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2585934"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2585946"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2585957"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2585969"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2585981"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2585992"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2586005"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2586016"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2586029"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2586041"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2586052"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2586064"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586076"></a><em class="parameter"><code>domain master = No</code></em></td></tr><tr><td><a class="indexterm" name="id2586088"></a><em class="parameter"><code>wins server = 172.16.0.1</code></em></td></tr><tr><td><a class="indexterm" name="id2586099"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2586111"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2586123"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2586135"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2586147"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2586159"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2586171"></a><em class="parameter"><code>idmap backend = ldap:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2586184"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2586195"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2586207"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2586219"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[accounts]</code></em></td></tr><tr><td><a class="indexterm" name="id2586265"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2586277"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2586288"></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="id2586309"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2586320"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2586332"></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="id2586353"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2586365"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2586376"></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="id2586397"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2586408"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2586420"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2586432"></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="id2586452"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2586464"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2586476"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586487"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586499"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2586545"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2586557"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2586568"></a><em class="parameter"><code>admin users = bjordan</code></em></td></tr><tr><td><a class="indexterm" name="id2586580"></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="id2586600"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2586612"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2586624"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586635"></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="id2586656"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2586668"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2586680"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2586691"></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="id2586712"></a><em class="parameter"><code>comment = Profile Data Share</code></em></td></tr><tr><td><a class="indexterm" name="id2586724"></a><em class="parameter"><code>path = /var/lib/samba/profdata</code></em></td></tr><tr><td><a class="indexterm" name="id2586736"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2586747"></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="id2586768"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2586780"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2586791"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586803"></a><em class="parameter"><code>guest ok = no</code></em></td></tr><tr><td><a class="indexterm" name="id2586815"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586826"></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" title="Miscellaneous Server Preparation Tasks"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2586862"></a>Miscellaneous Server Preparation Tasks</h2></div></div></div><p> - My father would say, <span class="quote">“<span class="quote">Dinner is not over until the dishes have been done.</span>”</span> +</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, “<span class="quote">Dinner is not over until the dishes have been done.</span>” 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" title="Configuring Directory Share Point Roots"><div class="titlepage"><div><div><h3 class="title"><a name="id2586882"></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" title="Configuring Profile Directories"><div class="titlepage"><div><div><h3 class="title"><a name="id2586977"></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,17 +2286,17 @@ 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="id2587093"></a> - <a class="indexterm" name="id2587100"></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 class="itemizedlist" type="disc"><li class="listitem"><p>You may permit the user to obtain a default profile.</p></li><li class="listitem"><p>You can create a mandatory profile.</p></li><li class="listitem"><p>You can create a group profile (which is almost always a mandatory profile).</p></li></ul></div><p> + </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> Mandatory profiles cannot be overwritten by a user. The change from a user profile to a mandatory 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="id2587150"></a> - <a class="indexterm" name="id2587156"></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" title="Preparation of Logon Scripts"><div class="titlepage"><div><div><h3 class="title"><a name="id2587221"></a>Preparation of Logon Scripts</h3></div></div></div><p> - <a class="indexterm" name="id2587229"></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" title="Assigning User Rights and Privileges"><div class="titlepage"><div><div><h3 class="title"><a name="id2587332"></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,9 +2347,9 @@ 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" title="Procedure 5.12. Steps for Assignment of User Rights and Privileges"><a name="id2587368"></a><p class="title"><b>Procedure 5.12. Steps for Assignment of User Rights and Privileges</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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 class="step" title="Step 2"><p> + </p></li><li><p> Execute the following command to grant the <code class="constant">Domain Admins</code> group all rights and privileges: </p><pre class="screen"> @@ -2361,7 +2361,7 @@ Successfully granted rights. </pre><p> Repeat this step on each domain controller, in each case substituting the name of the server (e.g., BLDG1, BLDG2) in place of the PDC called MASSIVE. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> In this step the privilege will be granted to Bob Jordan (bobj) to add Windows workstations to the domain. Execute the following only on the PDC. It is not necessary to do this on BDCs or on DMS machines because machine accounts are only ever added by the PDC: @@ -2370,7 +2370,7 @@ Successfully granted rights. "MEGANET2\bobj" SeMachineAccountPrivilege Successfully granted rights. </pre><p> - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Verify that privilege assignments have been correctly applied by executing: </p><pre class="screen"> net rpc rights list accounts -Uroot%not24get @@ -2405,8 +2405,8 @@ SeAddUsersPrivilege SeRemoteShutdownPrivilege SeDiskOperatorPrivilege </pre><p> - </p></li></ol></div></div></div><div class="sect1" title="Windows Client Configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2587466"></a>Windows Client Configuration</h2></div></div></div><p> - <a class="indexterm" name="id2587474"></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 @@ -2418,60 +2418,60 @@ SeDiskOperatorPrivilege "<a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;EN-US;168475" target="_top">How to Create a Base Profile for All Users."</a> - </p><div class="sect2" title="Configuration of Default Profile with Folder Redirection"><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="id2587524"></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="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" title="Procedure 5.13. Expose Hidden Folders"><a name="id2587542"></a><p class="title"><b>Procedure 5.13. Expose Hidden Folders</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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> → <span class="guimenuitem">My Computer</span> → <span class="guimenuitem">Tools</span> → <span class="guimenuitem">Folder Options</span> → <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 class="step" title="Step 2"><p> - <a class="indexterm" name="id2587609"></a> + </p></li><li><p> + <a class="indexterm" name="id2581523"></a> Launch the Registry Editor. Click <span class="guimenu">Start</span> → <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" title="Procedure 5.14. Redirect Folders in Default System User Profile"><a name="sbehap-rdrfldr"></a><p class="title"><b>Procedure 5.14. Redirect Folders in Default System User Profile</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2587667"></a> - <a class="indexterm" name="id2587673"></a> + </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="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> → <span class="guimenuitem">Load Hive...</span> → <span class="guimenuitem">Documents and Settings</span> → <span class="guimenuitem">Default User</span> → <span class="guimenuitem">NTUSER</span> → <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>. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Browse inside the newly loaded Default folder to: </p><pre class="screen"> HKEY_LOCAL_MACHINE\Default\Software\Microsoft\Windows\ CurrentVersion\Explorer\User Shell Folders\ </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">“Windows XP Professional User Shared Folders”</a>. - </p></li><li class="step" title="Step 3"><p> - <a class="indexterm" name="id2587766"></a> - <a class="indexterm" name="id2587773"></a> + </p></li><li><p> + <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 class="itemizedlist" type="disc"><li class="listitem"><p>A drive letter such as <code class="constant">U:</code></p></li><li class="listitem"><p>A direct network path such as - <code class="constant">\\MASSIVE\profdata</code></p></li><li class="listitem"><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 class="step" title="Step 4"><p> - <a class="indexterm" name="id2587820"></a> + </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="id2581735"></a> Set the registry keys as shown in <a class="link" href="happy.html#proffold" title="Table 5.4. Default Profile Redirections">“Default Profile Redirections”</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. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> Click back to the root of the loaded hive <code class="constant">Default</code>. Click <span class="guimenu">File</span> → <span class="guimenuitem">Unload Hive...</span> → <span class="guimenuitem">Yes</span>. - </p></li><li class="step" title="Step 6"><p> - <a class="indexterm" name="id2587875"></a> + </p></li><li><p> + <a class="indexterm" name="id2581790"></a> Click <span class="guimenu">File</span> → <span class="guimenuitem">Exit</span>. This exits the Registry Editor. - </p></li><li class="step" title="Step 7"><p> + </p></li><li><p> Now follow the procedure given in <a class="link" href="happy.html#sbehap-locgrppol" title="The Local Group Policy">“The Local Group Policy”</a>. Make sure that each folder you have redirected is in the exclusion list. - </p></li><li class="step" title="Step 8"><p> - You are now ready to copy<sup>[<a name="id2587919" href="#ftn.id2587919" class="footnote">11</a>]</sup> + </p></li><li><p> + 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" title="Procedure 5.15. Reset Folder Display to Original Behavior"><a name="id2587986"></a><p class="title"><b>Procedure 5.15. Reset Folder Display to Original Behavior</b></p><ul class="procedure"><li class="step" title="Step 1"><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> → <span class="guimenuitem">My Computer</span> → <span class="guimenuitem">Tools</span> → <span class="guimenuitem">Folder Options</span> → <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" title="Configuration of MS Outlook to Relocate PST File"><div class="titlepage"><div><div><h3 class="title"><a name="id2588220"></a>Configuration of MS Outlook to Relocate PST File</h3></div></div></div><p> - <a class="indexterm" name="id2588229"></a> - <a class="indexterm" name="id2588238"></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,19 +2498,19 @@ 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" title="Procedure 5.16. Outlook PST File Relocation"><a name="id2588260"></a><p class="title"><b>Procedure 5.16. Outlook PST File Relocation</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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 class="step" title="Step 2"><p> + </p></li><li><p> From the <span class="guimenu">Control Panel</span>, launch the Mail icon. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Click <span class="guimenu">Email Accounts.</span> - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Make a note of the location of the PST file(s). From this location, move the files to the desired new target location. The most desired new target location may well be the users' home directory. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> Add a new data file, selecting the PST file in the new desired target location. - Give this entry (not the filename) a new name such as <span class="quote">“<span class="quote">Personal Mail Folders.</span>”</span> + Give this entry (not the filename) a new name such as “<span class="quote">Personal Mail Folders.</span>” </p><p> Note: If MS Outlook has been configured to use an IMAP account configuration there may be problems following these instructions. Feedback from users suggests that where IMAP is used the PST @@ -2518,21 +2518,21 @@ HKEY_LOCAL_MACHINE\Default\Software\Microsoft\Windows\ MS Outlook's Send/Receive button. If anyone has sucessfully relocated PST files where IMAP is used please email <code class="literal">jht@samba.org</code> with useful tips and suggestions so that this warning can be removed or modified. - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> Close the <span class="guimenu">Date Files</span> windows, then click <span class="guimenu">Email Accounts</span>. - </p></li><li class="step" title="Step 7"><p> + </p></li><li><p> Select <span class="guimenu">View of Change</span> exiting email accounts, click <span class="guibutton">Next.</span> - </p></li><li class="step" title="Step 8"><p> + </p></li><li><p> Change the <span class="guimenu">Mail Delivery Location</span> so as to use the data file in the new target location. - </p></li><li class="step" title="Step 9"><p> + </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" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - <a class="indexterm" name="id2588410"></a> + </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="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" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - <a class="indexterm" name="id2588425"></a> + </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + <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="id2588448"></a> - <a class="indexterm" name="id2588454"></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="id2588470"></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="id2588491"></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="id2588511"></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" title="Configure Delete Cached Profiles on Logout"><div class="titlepage"><div><div><h3 class="title"><a name="id2588536"></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="id2588549"></a> + <a class="indexterm" name="id2582464"></a> Click <span class="guimenu">Start</span> → <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,94 +2576,94 @@ veto oplock files = /*.pdf/*.PST/ profiles are deleted as network users log out of the system. Click <span class="guimenu">File</span> → <span class="guimenuitem">Add/Remove Snap-in</span> → <span class="guimenuitem">Add</span> → <span class="guimenuitem">Group Policy</span> → <span class="guimenuitem">Add</span> → <span class="guimenuitem">Finish</span> → <span class="guimenuitem">Close</span> → <span class="guimenuitem">OK</span>. </p><p> - <a class="indexterm" name="id2588645"></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> → <span class="guimenuitem">Administrative Templates</span> → <span class="guimenuitem">System</span> → <span class="guimenuitem">User Profiles</span>. In the right panel, set the properties shown here by double-clicking on each item as shown: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Do not check for user ownership of Roaming Profile Folders = Enabled</p></li><li class="listitem"><p>Delete cached copies of roaming profiles = Enabled</p></li></ul></div><p> + </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" title="Uploading Printer Drivers to Samba Servers"><div class="titlepage"><div><div><h3 class="title"><a name="id2588716"></a>Uploading Printer Drivers to Samba Servers</h3></div></div></div><p> - <a class="indexterm" name="id2588724"></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" title="Procedure 5.17. Steps to Install Printer Drivers on the Samba Servers"><a name="id2588742"></a><p class="title"><b>Procedure 5.17. Steps to Install Printer Drivers on the Samba Servers</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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">“A Collection of Useful Tidbits”</a>, <a class="link" href="appendix.html#domjoin" title="Joining a Domain: Windows 200x/XP Professional">“Joining a Domain: Windows 200x/XP Professional”</a>. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> After the machine has rebooted, log onto the workstation as the domain <code class="constant">root</code> (this is the Administrator account for the operating system that is the host platform for this implementation of Samba. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Launch MS Windows Explorer. Navigate in the left panel. Click <span class="guimenu">My Network Places</span> → <span class="guimenuitem">Entire Network</span> → <span class="guimenuitem">Microsoft Windows Network</span> → <span class="guimenuitem">Meganet2</span> → <span class="guimenuitem">Massive</span>. Click on <span class="guimenu">Massive</span> <span class="guimenu">Printers and Faxes</span>. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Identify a printer that is shown in the right panel. Let us assume the printer is called <code class="constant">ps01-color</code>. Right-click on the <span class="guimenu">ps01-color</span> icon and select the <span class="guimenu">Properties</span> entry. This opens a dialog box that indicates - that <span class="quote">“<span class="quote">The printer driver is not installed on this computer. Some printer properties + that “<span class="quote">The printer driver is not installed on this computer. Some printer properties will not be accessible unless you install the printer driver. Do you want to install the - driver now?</span>”</span> It is important at this point you answer <span class="guimenu">No</span>. - </p></li><li class="step" title="Step 5"><p> + driver now?</span>” It is important at this point you answer <span class="guimenu">No</span>. + </p></li><li><p> The printer properties panel for the <span class="guimenu">ps01-color</span> printer on the server <code class="constant">MASSIVE</code> is displayed. Click the <span class="guimenu">Advanced</span> tab. 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 <span class="quote">“<span class="quote">Add Printer Wizard</span>”</span>. - </p></li><li class="step" title="Step 6"><p> - <a class="indexterm" name="id2588931"></a> - <a class="indexterm" name="id2588940"></a> - The <span class="quote">“<span class="quote">Add Printer Driver Wizard on <code class="constant">MASSIVE</code></span>”</span> panel + button that is next to the <span class="guimenu">Driver</span> box. This launches the “<span class="quote">Add Printer Wizard</span>”. + </p></li><li><p> + <a class="indexterm" name="id2582846"></a> + <a class="indexterm" name="id2582855"></a> + The “<span class="quote">Add Printer Driver Wizard on <code class="constant">MASSIVE</code></span>” 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 Lexmark. In the right panel, select the printer (Lexmark Optra Color 40 PS). Click <span class="guimenu">Next</span>, and then <span class="guimenu">Finish</span> to commence driver upload. A 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 class="step" title="Step 7"><p> - <a class="indexterm" name="id2588989"></a> - <a class="indexterm" name="id2588998"></a> - <a class="indexterm" name="id2589007"></a> - <a class="indexterm" name="id2589016"></a> - <a class="indexterm" name="id2589025"></a> - <a class="indexterm" name="id2589035"></a> + </p></li><li><p> + <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 the <span class="guimenu">Security</span> tab). Under the <span class="guimenu">Sharing</span> tab it is possible to - load additional printer drivers; there is also a check-box in this tab called <span class="quote">“<span class="quote">List in the - directory</span>”</span>. When this box is checked, the printer will be published in Active Directory + load additional printer drivers; there is also a check-box in this tab called “<span class="quote">List in the + directory</span>”. When this box is checked, the printer will be published in Active Directory (Applicable to Active Directory use only.) - </p></li><li class="step" title="Step 8"><p> - <a class="indexterm" name="id2589090"></a> + </p></li><li><p> + <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> → <span class="guimenuitem">Device Settings</span>. Now change the settings to suit your requirements. BE CERTAIN TO CHANGE AT LEAST ONE SETTING and apply the changes even if you need to reverse the changes back to their original settings. - </p></li><li class="step" title="Step 9"><p> + </p></li><li><p> This is necessary so that the printer settings are initialized in the Samba printers database. Click <span class="guimenu">Apply</span> to commit your settings. Revert any settings you changed 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 class="step" title="Step 10"><p> - <a class="indexterm" name="id2589163"></a> + </p></li><li><p> + <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> in the panel that is newly presented. Click <span class="guimenu">OK</span> on the <span class="guimenu">ps01-color on massive Properties</span> panel. - </p></li><li class="step" title="Step 11"><p> + </p></li><li><p> 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" title="Software Installation"><div class="titlepage"><div><div><h3 class="title"><a name="id2589218"></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" title="Roll-out Image Creation"><div class="titlepage"><div><div><h3 class="title"><a name="id2589254"></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" title="Key Points Learned"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2589288"></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="id2589309"></a> - <a class="indexterm" name="id2589319"></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 @@ -2708,53 +2708,53 @@ veto oplock files = /*.pdf/*.PST/ as well as security considerations. </p><p> The substance of this chapter that has been deserving of particular attention includes: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> Implementation of an OpenLDAP-based passwd backend, necessary to support distributed domain control. - </p></li><li class="listitem"><p> + </p></li><li><p> Implementation of Samba primary and secondary domain controllers with a common LDAP backend for user and group accounts that is shared with the UNIX system through the PADL nss_ldap and pam_ldap tool-sets. - </p></li><li class="listitem"><p> + </p></li><li><p> Use of the Idealx smbldap-tools scripts for UNIX (POSIX) account management as well as to manage Samba Windows user and group accounts. - </p></li><li class="listitem"><p> + </p></li><li><p> The basics of implementation of Group Policy controls for Windows network clients. - </p></li><li class="listitem"><p> + </p></li><li><p> Control over roaming profiles, with particular focus on folder redirection to network drives. - </p></li><li class="listitem"><p> + </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" title="Questions and Answers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2589403"></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" title="Frequently Asked Questions"><a name="id2589415"></a><dl><dt> <a href="happy.html#id2589422"> + </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#id2589466"> + </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#id2589527"> + </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#id2589566"> + </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#id2589591"> + </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#id2589618"> + </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#id2589643"> + </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#id2589678"> + </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#id2589708"> + </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#id2589735"> + </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" width="100%" summary="Q and A Set"><col align="left" width="1%"><col><tbody><tr class="question"><td align="left" valign="top"><a name="id2589422"></a><a name="id2589424"></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="id2589466"></a><a name="id2589468"></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="id2589527"></a><a name="id2589529"></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="id2589566"></a><a name="id2589568"></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="id2589591"></a><a name="id2589593"></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="id2589618"></a><a name="id2589620"></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="id2589643"></a><a name="id2589645"></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="id2589678"></a><a name="id2589681"></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="id2589708"></a><a name="id2589710"></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,13 +2863,13 @@ 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="id2589735"></a><a name="id2589737"></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.id2587919" href="#id2587919" 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 diff --git a/docs/htmldocs/Samba3-ByExample/images/AccountingNetwork.png b/docs/htmldocs/Samba3-ByExample/images/AccountingNetwork.png Binary files differindex 8594d85d54..cf6bf8ba12 100644 --- a/docs/htmldocs/Samba3-ByExample/images/AccountingNetwork.png +++ 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 Binary files differindex b6acf4e69c..eaabea6169 100644 --- a/docs/htmldocs/Samba3-ByExample/images/Charity-Network.png +++ b/docs/htmldocs/Samba3-ByExample/images/Charity-Network.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 Binary files differindex cf6d1580e7..8b6e86dde1 100644 --- a/docs/htmldocs/Samba3-ByExample/images/UNIX-Samba-and-LDAP.png +++ b/docs/htmldocs/Samba3-ByExample/images/UNIX-Samba-and-LDAP.png diff --git a/docs/htmldocs/Samba3-ByExample/images/acct2net.png b/docs/htmldocs/Samba3-ByExample/images/acct2net.png Binary files differindex d11096654f..2c1cd6c558 100644 --- a/docs/htmldocs/Samba3-ByExample/images/acct2net.png +++ 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 Binary files differindex 09b79e0c3f..b10f33ff24 100644 --- a/docs/htmldocs/Samba3-ByExample/images/ch7-dual-additive-LDAP-Ok.png +++ 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 Binary files differindex 0704332e67..9b5b15beae 100644 --- a/docs/htmldocs/Samba3-ByExample/images/ch7-dual-additive-LDAP.png +++ 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 Binary files differindex 2a6d8dc915..7c407e13b7 100644 --- a/docs/htmldocs/Samba3-ByExample/images/ch7-fail-overLDAP.png +++ 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 Binary files differindex 5bb21c0f90..ccbf65095a 100644 --- a/docs/htmldocs/Samba3-ByExample/images/ch7-singleLDAP.png +++ 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 Binary files differindex 0b6b8e2a84..b0e449cac4 100644 --- a/docs/htmldocs/Samba3-ByExample/images/ch8-migration.png +++ 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 Binary files differindex 7bcf9f1f19..e6c5a77fc0 100644 --- a/docs/htmldocs/Samba3-ByExample/images/chap4-net.png +++ 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 Binary files differindex 31d5815844..163f9fafb4 100644 --- a/docs/htmldocs/Samba3-ByExample/images/chap5-net.png +++ 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 Binary files differindex 4d482b42f9..cd7fcc9fbf 100644 --- a/docs/htmldocs/Samba3-ByExample/images/chap6-net.png +++ 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 Binary files differindex 439a528601..43a317db2b 100644 --- a/docs/htmldocs/Samba3-ByExample/images/chap7-idresol.png +++ b/docs/htmldocs/Samba3-ByExample/images/chap7-idresol.png diff --git a/docs/htmldocs/Samba3-ByExample/images/chap9-ADSDC.png b/docs/htmldocs/Samba3-ByExample/images/chap9-ADSDC.png Binary files differindex b5ba5c34c3..a82ac485a7 100644 --- a/docs/htmldocs/Samba3-ByExample/images/chap9-ADSDC.png +++ 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 Binary files differindex b7ac7d7a87..d487d17ec0 100644 --- a/docs/htmldocs/Samba3-ByExample/images/chap9-SambaDC.png +++ b/docs/htmldocs/Samba3-ByExample/images/chap9-SambaDC.png diff --git a/docs/htmldocs/Samba3-ByExample/index.html b/docs/htmldocs/Samba3-ByExample/index.html index d458771fd0..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.75.2"><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" title="Samba-3 by Example"><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="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></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#id2507144">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#id2507332">Why Is This Book Necessary?</a></span></dt><dd><dl><dt><span class="sect2"><a href="preface.html#id2505043">Samba 3.0.20 Update Edition</a></span></dt></dl></dd><dt><span class="sect1"><a href="preface.html#id2504930">Prerequisites</a></span></dt><dt><span class="sect1"><a href="preface.html#id2504961">Approach</a></span></dt><dt><span class="sect1"><a href="preface.html#id2505027">Summary of Topics</a></span></dt><dt><span class="sect1"><a href="preface.html#id2556726">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#id2556922">Introduction</a></span></dt><dt><span class="sect1"><a href="simple.html#id2556963">Assignment Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="simple.html#id2557004">Drafting Office</a></span></dt><dt><span class="sect2"><a href="simple.html#id2557714">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#id2561049">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#id2561519">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2561542">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2561602">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2561650">Technical Issues</a></span></dt><dt><span class="sect2"><a href="small.html#id2561848">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2561869">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2563413">Validation</a></span></dt><dt><span class="sect2"><a href="small.html#id2564061">Notebook Computers: A Special Case</a></span></dt><dt><span class="sect2"><a href="small.html#id2564087">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2564161">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#id2564639">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2564691">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2564924">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2564939">Technical Issues</a></span></dt><dt><span class="sect2"><a href="secure.html#id2565367">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2565406">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#id2566260">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#id2570721">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2570783">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#id2571305">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2571350">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2571456">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2571492">Technical Issues</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2571695">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2571718">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#id2572445">Server Preparation: All Servers</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2573010">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#id2576210">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2576268">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#id2577106">Regarding LDAP Directories and Windows Computer Accounts</a></span></dt><dt><span class="sect1"><a href="happy.html#id2577248">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2577346">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2577483">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2577941">Technical Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2579819">Political Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2579834">Installation Checklist</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2580015">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#id2582912">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#id2586862">Miscellaneous Server Preparation Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2586882">Configuring Directory Share Point Roots</a></span></dt><dt><span class="sect2"><a href="happy.html#id2586977">Configuring Profile Directories</a></span></dt><dt><span class="sect2"><a href="happy.html#id2587221">Preparation of Logon Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2587332">Assigning User Rights and Privileges</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2587466">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#id2588220">Configuration of MS Outlook to Relocate PST File</a></span></dt><dt><span class="sect2"><a href="happy.html#id2588536">Configure Delete Cached Profiles on Logout</a></span></dt><dt><span class="sect2"><a href="happy.html#id2588716">Uploading Printer Drivers to Samba Servers</a></span></dt><dt><span class="sect2"><a href="happy.html#id2589218">Software Installation</a></span></dt><dt><span class="sect2"><a href="happy.html#id2589254">Roll-out Image Creation</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2589288">Key Points Learned</a></span></dt><dt><span class="sect1"><a href="happy.html#id2589403">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#id2589825">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2589856">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2589924">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2590197">Technical Issues</a></span></dt><dt><span class="sect2"><a href="2000users.html#id2591142">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2591160">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2594319">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2594466">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#id2595324">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2595378">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2595413">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2595441">Technical Issues</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596090">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2596190">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#id2602396">UNIX/Linux Client Domain Member</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2602971">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2603025">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#id2604185">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2604281">Cautions and Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2605610">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#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2606312">Samba-2.x with LDAP Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2606494">Updating a Samba-3 Installation</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2606604">Samba-3 to Samba-3 Updates on the Same Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2606808">Migrating Samba-3 to a New Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2607222">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#id2607394">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2607479">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2607534">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2607720">Technical Issues</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2608043">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2608069">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2610669">NT4 Migration Using tdbsam Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2611075">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2611114">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#id2612089">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2612206">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2612318">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2612395">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2612585">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2612594">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#id2616672">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2617322">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2617338">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2617736">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#id2619366">Share Access Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2619714">Share Definition Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2620328">Share Point Directory and File Permissions</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2620740">Managing Windows 200x ACLs</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2621467">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2621601">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#id2622230">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2622261">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2622372">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2622405">Technical Issues</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2622561">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2622578">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#id2624430">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2624491">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#id2625018">Introduction</a></span></dt><dt><span class="sect1"><a href="HA.html#id2625115">Dissection and Discussion</a></span></dt><dt><span class="sect1"><a href="HA.html#id2625588">Guidelines for Reliable Samba Operation</a></span></dt><dd><dl><dt><span class="sect2"><a href="HA.html#id2625615">Name Resolution</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626091">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626419">Use and Location of BDCs</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626494">Use One Consistent Version of MS Windows Client</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626516">For Scalability, Use SAN-Based Storage on Samba Servers</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626565">Distribute Network Load with MSDFS</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626620">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626666">Hardware Problems</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626814">Large Directories</a></span></dt></dl></dd><dt><span class="sect1"><a href="HA.html#id2626917">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#id2627087">Free Support</a></span></dt><dt><span class="sect1"><a href="ch14.html#id2627306">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#id2628013">Samba System File Location</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2628434">Starting Samba</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2628774">DNS Configuration Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2628786">The Forward Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2628834">The Reverse Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2628974">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#id2629033">Initialization of the LDAP Database</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#id2629619">The LDAP Account Manager</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2630616">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#id2631091">Microsoft Access</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2631238">Act! Database Sharing</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2631322">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#id2631489">Requirements and Notes</a></span></dt><dt><span class="sect1"><a href="primer.html#id2631650">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2631710">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#id2631827">Exercises</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2631953">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#id2633100">Simple Windows Client Connection Characteristics</a></span></dt><dt><span class="sect2"><a href="primer.html#id2633603">Windows 200x/XP Client Interaction with Samba-3</a></span></dt><dt><span class="sect2"><a href="primer.html#id2634171">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#id2634286">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. - <acronym class="acronym">GNU</acronym> General Public License version 3 - </a></span></dt><dd><dl><dt><span class="bridgehead"><a href="apa.html#id2634952">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"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></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#id2628866">A. Preamble - </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2635097">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#id2635101">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#id2635193">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#id2635291">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#id2635331">A. + </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629246">A. 3. Protecting Users’ Legal Rights From Anti-Circumvention Law. - </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2635367">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#id2635394">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#id2635489">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#id2635679">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#id2635814">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#id2635858">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#id2635878">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#id2635930">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#id2636075">A. + </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629990">A. 12. No Surrender of Others’ Freedom. - </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2636097">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#id2636126">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#id2636188">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#id2636214">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#id2636235">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#id2636251">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#id2636255">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="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 <code class="literal">net rpc vampire</code> 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: <code class="constant">MEGANET</code>, 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 <code class="filename">smb.conf</code> 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 <code class="filename">smb.conf</code> File</a></dt><dt>1.2. <a href="simple.html#charity-smbconfnew">Charity Administration Office <code class="filename">smb.conf</code> New-style File</a></dt><dt>1.3. <a href="simple.html#charity-smbconf">Charity Administration Office <code class="filename">smb.conf</code> 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 <code class="filename">smb.conf</code> 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 <code class="filename">/etc/dhcpd.conf</code></a></dt><dt>2.3. <a href="small.html#acct2conf">Accounting Office Network <code class="filename">smb.conf</code> File [globals] Section</a></dt><dt>2.4. <a href="small.html#acct3conf">Accounting Office Network <code class="filename">smb.conf</code> 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 <span class="emphasis"><em>tdbsam</em></span> [globals] Section</a></dt><dt>3.5. <a href="secure.html#promisnetsvca">130 User Network with <span class="emphasis"><em>tdbsam</em></span> Services Section Part A</a></dt><dt>3.6. <a href="secure.html#promisnetsvcb">130 User Network with <span class="emphasis"><em>tdbsam</em></span> 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 <code class="filename">/etc/dhcpd.conf</code></a></dt><dt>3.9. <a href="secure.html#ch4namedcfg">DNS Master Configuration File <code class="filename">/etc/named.conf</code> Master Section</a></dt><dt>3.10. <a href="secure.html#ch4namedvarfwd">DNS Master Configuration File <code class="filename">/etc/named.conf</code> Forward Lookup Definition Section</a></dt><dt>3.11. <a href="secure.html#ch4namedvarrev">DNS Master Configuration File <code class="filename">/etc/named.conf</code> 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: <code class="filename">/etc/samba/smb.conf</code></a></dt><dt>4.2. <a href="Big500users.html#ch5-dc-common">Server: MASSIVE (PDC), File: <code class="filename">/etc/samba/dc-common.conf</code></a></dt><dt>4.3. <a href="Big500users.html#ch5-commonsmb">Common Samba Configuration File: <code class="filename">/etc/samba/common.conf</code></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 <code class="filename">/etc/openldap/slapd.conf</code> Part A</a></dt><dt>5.3. <a href="happy.html#sbehap-slapdconf2">LDAP Master Configuration File <code class="filename">/etc/openldap/slapd.conf</code> Part B</a></dt><dt>5.4. <a href="happy.html#sbehap-nss01">Configuration File for NSS LDAP Support <code class="filename">/etc/ldap.conf</code></a></dt><dt>5.5. <a href="happy.html#sbehap-nss02">Configuration File for NSS LDAP Clients Support <code class="filename">/etc/ldap.conf</code></a></dt><dt>5.6. <a href="happy.html#sbehap-massive-smbconfa">LDAP Based <code class="filename">smb.conf</code> File, Server: MASSIVE global Section: Part A</a></dt><dt>5.7. <a href="happy.html#sbehap-massive-smbconfb">LDAP Based <code class="filename">smb.conf</code> File, Server: MASSIVE global Section: Part B</a></dt><dt>5.8. <a href="happy.html#sbehap-bldg1-smbconf">LDAP Based <code class="filename">smb.conf</code> File, Server: BLDG1</a></dt><dt>5.9. <a href="happy.html#sbehap-bldg2-smbconf">LDAP Based <code class="filename">smb.conf</code> File, Server: BLDG2</a></dt><dt>5.10. <a href="happy.html#sbehap-shareconfa">LDAP Based <code class="filename">smb.conf</code> File, Shares Section Part A</a></dt><dt>5.11. <a href="happy.html#sbehap-shareconfb">LDAP Based <code class="filename">smb.conf</code> 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 <code class="filename">/etc/openldap/slapd.conf</code></a></dt><dt>6.2. <a href="2000users.html#ch7-LDAP-slave">LDAP Slave Configuration File <code class="filename">/etc/openldap/slapd.conf</code></a></dt><dt>6.3. <a href="2000users.html#ch7-massmbconfA">Primary Domain Controller <code class="filename">smb.conf</code> File Part A</a></dt><dt>6.4. <a href="2000users.html#ch7-massmbconfB">Primary Domain Controller <code class="filename">smb.conf</code> File Part B</a></dt><dt>6.5. <a href="2000users.html#ch7-massmbconfC">Primary Domain Controller <code class="filename">smb.conf</code> File Part C</a></dt><dt>6.6. <a href="2000users.html#ch7-slvsmbocnfA">Backup Domain Controller <code class="filename">smb.conf</code> File Part A</a></dt><dt>6.7. <a href="2000users.html#ch7-slvsmbocnfB">Backup Domain Controller <code class="filename">smb.conf</code> File Part B</a></dt><dt>7.1. <a href="unixclients.html#ch9-sdmsdc">Samba Domain Member in Samba Domain Using LDAP <code class="filename">smb.conf</code> 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 <code class="filename">/etc/ldap.conf</code></a></dt><dt>7.4. <a href="unixclients.html#ch9-sdmnss">NSS using LDAP for Identity Resolution File: <code class="filename">/etc/nsswitch.conf</code></a></dt><dt>7.5. <a href="unixclients.html#ch0-NT4DSDM">Samba Domain Member Server Using Winbind <code class="filename">smb.conf</code> File for NT4 Domain</a></dt><dt>7.6. <a href="unixclients.html#ch0-NT4DSCM">Samba Domain Member Server Using Local Accounts <code class="filename">smb.conf</code> File for NT4 Domain</a></dt><dt>7.7. <a href="unixclients.html#ch9-adssdm">Samba Domain Member <code class="filename">smb.conf</code> File for Active Directory Membership</a></dt><dt>7.8. <a href="unixclients.html#sbe-idmapridex">Example <code class="filename">smb.conf</code> File Using <code class="constant">idmap_rid</code></a></dt><dt>7.9. <a href="unixclients.html#sbeunxa">Typical ADS Style Domain <code class="filename">smb.conf</code> File</a></dt><dt>7.10. <a href="unixclients.html#sbewinbindex">ADS Membership Using RFC2307bis Identity Resolution <code class="filename">smb.conf</code> File</a></dt><dt>7.11. <a href="unixclients.html#ch9-pamwnbdlogin">SUSE: PAM <code class="filename">login</code> Module Using Winbind</a></dt><dt>7.12. <a href="unixclients.html#ch9-pamwbndxdm">SUSE: PAM <code class="filename">xdm</code> Module Using Winbind</a></dt><dt>7.13. <a href="unixclients.html#ch9-rhsysauth">Red Hat 9: PAM System Authentication File: <code class="filename">/etc/pam.d/system-auth</code> Module Using Winbind</a></dt><dt>9.1. <a href="ntmigration.html#sbent4smb">NT4 Migration Samba-3 Server <code class="filename">smb.conf</code> Part: A</a></dt><dt>9.2. <a href="ntmigration.html#sbent4smb2">NT4 Migration Samba-3 Server <code class="filename">smb.conf</code> Part: B</a></dt><dt>9.3. <a href="ntmigration.html#sbentslapd">NT4 Migration LDAP Server Configuration File: <code class="filename">/etc/openldap/slapd.conf</code> Part A</a></dt><dt>9.4. <a href="ntmigration.html#sbentslapd2">NT4 Migration LDAP Server Configuration File: <code class="filename">/etc/openldap/slapd.conf</code> Part B</a></dt><dt>9.5. <a href="ntmigration.html#sbrntldapconf">NT4 Migration NSS LDAP File: <code class="filename">/etc/ldap.conf</code></a></dt><dt>9.6. <a href="ntmigration.html#sbentnss">NT4 Migration NSS Control File: <code class="filename">/etc/nsswitch.conf</code> (Stage:1)</a></dt><dt>9.7. <a href="ntmigration.html#sbentnss2">NT4 Migration NSS Control File: <code class="filename">/etc/nsswitch.conf</code> (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 <code class="filename">/etc/security/pam_unix2.conf</code></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 <code class="filename">/root/excludes.txt</code></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: <code class="filename">/etc/krb5.conf</code></a></dt><dt>12.2. <a href="DomApps.html#ch10-smbconf">Samba Configuration File: <code class="filename">/etc/samba/smb.conf</code></a></dt><dt>12.3. <a href="DomApps.html#ch10-etcnsscfg">NSS Configuration File Extract File: <code class="filename">/etc/nsswitch.conf</code></a></dt><dt>12.4. <a href="DomApps.html#etcsquidcfg">Squid Configuration File Extract <code class="filename">/etc/squid.conf</code> [ADMINISTRATIVE PARAMETERS Section]</a></dt><dt>12.5. <a href="DomApps.html#etcsquid2">Squid Configuration File extract File: <code class="filename">/etc/squid.conf</code> [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: <code class="filename">/var/lib/named/localhost.zone</code></a></dt><dt>15.4. <a href="appendix.html#dnsloopy">DNS Localhost Reverse Zone File: <code class="filename">/var/lib/named/127.0.0.zone</code></a></dt><dt>15.5. <a href="appendix.html#roothint">DNS Root Name Server Hint File: <code class="filename">/var/lib/named/root.hint</code></a></dt><dt>15.6. <a href="appendix.html#sbehap-ldapreconfa">LDAP Pre-configuration Script: <code class="filename">SMBLDAP-ldif-preconfig.sh</code> Part A</a></dt><dt>15.7. <a href="appendix.html#sbehap-ldapreconfb">LDAP Pre-configuration Script: <code class="filename">SMBLDAP-ldif-preconfig.sh</code> Part B</a></dt><dt>15.8. <a href="appendix.html#sbehap-ldapreconfc">LDAP Pre-configuration Script: <code class="filename">SMBLDAP-ldif-preconfig.sh</code> 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 <code class="filename">config.cfg</code></a></dt><dt>15.12. <a href="appendix.html#lamconf">LAM Profile Control File <code class="filename">lam.conf</code></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 cc26f16c1d..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.75.2"><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" title="Index"><div class="titlepage"><div><div><h2 class="title"><a name="id2636953"></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#id2578452">Roaming Profile Background</a>, <a class="indexterm" href="happy.html#id2578753">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#id2558033">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a></dt><dt>/etc/cups/mime.types, <a class="indexterm" href="simple.html#id2558033">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a></dt><dt>/etc/dhcpd.conf, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="small.html#id2563413">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#id2577941">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#id2606820">Replacing a Domain Member Server</a>, <a class="indexterm" href="ntmigration.html#id2611114">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#id2557141">Implementation</a>, <a class="indexterm" href="small.html#id2561869">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#id2572445">Server Preparation: All Servers</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="DomApps.html#id2622828">Kerberos Configuration</a>, <a class="indexterm" href="HA.html#id2625627">Bad Hostnames</a></dt><dt>/etc/krb5.conf, <a class="indexterm" href="unixclients.html#id2601464">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="DomApps.html#id2622828">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#id2601464">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="unixclients.html#id2602059">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>/etc/mime.convs, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2572445">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#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2572445">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#id2561869">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#id2573023">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#id2600860">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2602059">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a></dt><dt>/etc/openldap/slapd.conf, <a class="indexterm" href="happy.html#id2579330">Debugging LDAP</a>, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a>, <a class="indexterm" href="2000users.html#id2591160">Implementation</a></dt><dt>/etc/passwd, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2573023">Configuration for Server: MASSIVE</a>, <a class="indexterm" href="happy.html#id2582912">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#id2603025">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2606820">Replacing a Domain Member Server</a>, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2612395">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2620328">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#id2633338">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#id2573023">Configuration for Server: MASSIVE</a></dt><dt>/etc/rc.d/rc.local, <a class="indexterm" href="small.html#id2561869">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#id2572445">Server Preparation: All Servers</a></dt><dt>/etc/samba, <a class="indexterm" href="appendix.html#id2628013">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#id2572445">Server Preparation: All Servers</a></dt><dt>/etc/shadow, <a class="indexterm" href="upgrades.html#id2606820">Replacing a Domain Member Server</a>, <a class="indexterm" href="nw4migration.html#id2612395">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#id2579330">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#id2608210">NT4 Migration Using LDAP Backend</a></dt><dt>/proc/sys/net/ipv4/ip_forward, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a></dt><dt>/usr/bin, <a class="indexterm" href="appendix.html#id2628013">Samba System File Location</a></dt><dt>/usr/lib/samba, <a class="indexterm" href="appendix.html#id2628013">Samba System File Location</a></dt><dt>/usr/local, <a class="indexterm" href="appendix.html#id2628013">Samba System File Location</a></dt><dt>/usr/local/samba, <a class="indexterm" href="appendix.html#id2628013">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#id2628013">Samba System File Location</a></dt><dt>/usr/share, <a class="indexterm" href="appendix.html#id2628013">Samba System File Location</a></dt><dt>/usr/share/samba/swat, <a class="indexterm" href="appendix.html#id2628013">Samba System File Location</a></dt><dt>/usr/share/swat, <a class="indexterm" href="appendix.html#id2628013">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#id2628013">Samba System File Location</a></dt><dt>/var/log/ldaplogs, <a class="indexterm" href="happy.html#id2579330">Debugging LDAP</a></dt><dt>/var/log/samba, <a class="indexterm" href="appendix.html#id2628013">Samba System File Location</a></dt><dt>8-bit, <a class="indexterm" href="upgrades.html#id2605445">International Language Support</a></dt></dl></div><div class="indexdiv"><h3></h3><dl><dt>, <a class="indexterm" href="simple.html#id2557141">Implementation</a>, <a class="indexterm" href="simple.html#id2558033">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a>, <a class="indexterm" href="secure.html#ch4appscfg">Application Share Configuration</a>, <a class="indexterm" href="Big500users.html#id2571718">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#id2591160">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#id2600860">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2601464">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="unixclients.html#id2602059">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#id2608210">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a>, <a class="indexterm" href="DomApps.html#id2623769">NSS Configuration</a></dt><dd><dl><dt>Domain account, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>liability, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>logon, <a class="indexterm" href="simple.html#id2558033">Implementation</a></dt><dt>problem, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>transparent inter-operability, <a class="indexterm" href="DomApps.html#id2624491">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#id2617338">Dissection and Discussion</a></dt><dt>access, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2619854">Checkpoint Controls</a></dt><dt>access control, <a class="indexterm" href="kerberos.html#id2619019">Kerberos Exposed</a>, <a class="indexterm" href="kerberos.html#id2620795">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#id2619366">Share Access Controls</a></dt><dt>access controls, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2619714">Share Definition Controls</a></dt><dt>accessible, <a class="indexterm" href="kerberos.html#id2620328">Share Point Directory and File Permissions</a></dt><dt>account, <a class="indexterm" href="happy.html#id2577106">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="kerberos.html#id2619366">Share Access Controls</a></dt><dd><dl><dt>ADS Domain, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt></dl></dd><dt>account credentials, <a class="indexterm" href="primer.html#id2633338">Findings and Comments</a></dt><dt>account information, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>account names, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>account policies, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>accountable, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a>, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>accounts</dt><dd><dl><dt>authoritative, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>Domain, <a class="indexterm" href="ntmigration.html#id2607394">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>group, <a class="indexterm" href="ntmigration.html#id2607394">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>machine, <a class="indexterm" href="ntmigration.html#id2607394">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>manage, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>user, <a class="indexterm" href="ntmigration.html#id2607394">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt></dl></dd><dt>ACL, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a>, <a class="indexterm" href="kerberos.html#id2619854">Checkpoint Controls</a></dt><dt>ACLs, <a class="indexterm" href="happy.html#id2589288">Key Points Learned</a>, <a class="indexterm" href="kerberos.html#id2619366">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2619714">Share Definition Controls</a></dt><dt>acquisitions, <a class="indexterm" href="kerberos.html#id2616672">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#id2631238">Act! Database Sharing</a></dt><dt>Act!Diag, <a class="indexterm" href="appendix.html#id2631238">Act! Database Sharing</a></dt><dt>Active Directory, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#sbehap-locgrppol">The Local Group Policy</a>, <a class="indexterm" href="2000users.html#id2589924">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#id2595378">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#id2600860">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a>, <a class="indexterm" href="kerberos.html#id2621467">Key Points Learned</a>, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a>, <a class="indexterm" href="DomApps.html">Integrating Additional Services</a>, <a class="indexterm" href="DomApps.html#id2622261">Assignment Tasks</a>, <a class="indexterm" href="DomApps.html#id2622405">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2623217">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#id2624034">Squid Configuration</a></dt><dt>domain, <a class="indexterm" href="DomApps.html#id2623217">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#id2617736">Technical Issues</a></dt><dt>realm, <a class="indexterm" href="HA.html#id2625627">Bad Hostnames</a></dt><dt>Replacement, <a class="indexterm" href="kerberos.html#id2617736">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#id2622828">Kerberos Configuration</a></dt><dt>Server, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>tree, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a></dt></dl></dd><dt>active directory, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a></dt><dt>AD printer publishing, <a class="indexterm" href="happy.html#id2588716">Uploading Printer Drivers to Samba Servers</a></dt><dt>ADAM, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#id2601464">IDMAP Storage in LDAP using Winbind</a></dt><dt>add group script, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>add machine script, <a class="indexterm" href="upgrades.html#id2605979">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#id2588716">Uploading Printer Drivers to Samba Servers</a></dt></dl></dd><dt>add user script, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>add user to group script, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>adduser, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2573023">Configuration for Server: MASSIVE</a></dt><dt>adequate precautions, <a class="indexterm" href="upgrades.html#id2604185">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#id2619854">Checkpoint Controls</a></dt><dt>administrator, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2572445">Server Preparation: All Servers</a></dt><dt>ADMT, <a class="indexterm" href="upgrades.html#id2607222">Migration of Samba Accounts to Active Directory</a></dt><dt>ADS, <a class="indexterm" href="unixclients.html#id2601464">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2622828">Kerberos Configuration</a>, <a class="indexterm" href="HA.html#id2625627">Bad Hostnames</a></dt><dd><dl><dt>server, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt></dl></dd><dt>ADS Domain, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>affordability, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a></dt><dt>alarm, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>algorithm, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>allow trusted domains, <a class="indexterm" href="unixclients.html#id2600860">IDMAP_RID with Winbind</a></dt><dt>alternative, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>analysis, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>anonymous connection, <a class="indexterm" href="small.html#id2563413">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>Apache Web server, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dt>appliance mode, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>application server, <a class="indexterm" href="secure.html#id2564939">Technical Issues</a>, <a class="indexterm" href="secure.html#ch4appscfg">Application Share Configuration</a></dt><dt>application servers, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a></dt><dt>application/octet-stream, <a class="indexterm" href="simple.html#id2558033">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2572445">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#id2588716">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#id2616672">Introduction</a></dt><dt>assistance, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt><dt>assumptions, <a class="indexterm" href="HA.html#id2626917">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#id2612670">LDAP Server Configuration</a>, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a></dt><dt>authenticated, <a class="indexterm" href="DomApps.html#id2622261">Assignment Tasks</a></dt><dt>authenticated connection, <a class="indexterm" href="small.html#id2563413">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>authentication, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2612318">Dissection and Discussion</a>, <a class="indexterm" href="DomApps.html">Integrating Additional Services</a>, <a class="indexterm" href="DomApps.html#id2622405">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2623769">NSS Configuration</a>, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dd><dl><dt>plain-text, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt></dl></dd><dt>authentication process, <a class="indexterm" href="unixclients.html#id2596190">Implementation</a></dt><dt>authentication protocols, <a class="indexterm" href="DomApps.html#id2624430">Key Points Learned</a></dt><dt>authoritative, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>authorized location, <a class="indexterm" href="kerberos.html#id2619019">Kerberos Exposed</a></dt><dt>auto-generated SID, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>automatically allocate, <a class="indexterm" href="unixclients.html#id2595441">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#id2594466">Questions and Answers</a></dt><dt>Backup, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>Backup Domain Controller (see BDC)</dt><dt>bandwidth, <a class="indexterm" href="DomApps.html#id2622261">Assignment Tasks</a></dt><dd><dl><dt>requirements, <a class="indexterm" href="2000users.html#id2590236">User Needs</a></dt></dl></dd><dt>bandwidth calculations, <a class="indexterm" href="secure.html#id2565213">Hardware Requirements</a></dt><dt>BDC, <a class="indexterm" href="Big500users.html#id2571492">Technical Issues</a>, <a class="indexterm" href="happy.html">Making Happy Users</a>, <a class="indexterm" href="happy.html#id2577346">Assignment Tasks</a>, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2580015">Samba Server Implementation</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="2000users.html#id2594319">Key Points Learned</a>, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a>, <a class="indexterm" href="ntmigration.html#id2610669">NT4 Migration Using tdbsam Backend</a>, <a class="indexterm" href="HA.html#id2626419">Use and Location of BDCs</a></dt><dt>benefit, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>best practices, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>bias, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>binary database, <a class="indexterm" href="secure.html#id2565406">Implementation</a></dt><dt>binary files, <a class="indexterm" href="upgrades.html#id2606494">Updating a Samba-3 Installation</a></dt><dt>binary package, <a class="indexterm" href="upgrades.html#id2606494">Updating a Samba-3 Installation</a></dt><dt>bind interfaces only, <a class="indexterm" href="secure.html#id2565406">Implementation</a></dt><dt>broadcast, <a class="indexterm" href="HA.html#id2625819">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#id2590330">The Nature of Windows Networking Protocols</a></dt><dt>mailslot, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a></dt></dl></dd><dt>broadcast messages, <a class="indexterm" href="secure.html#id2565406">Implementation</a></dt><dt>broadcast storms, <a class="indexterm" href="HA.html#id2625992">Network Collisions</a></dt><dt>broken, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>broken behavior, <a class="indexterm" href="HA.html#id2625115">Dissection and Discussion</a></dt><dt>browse, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>browse master, <a class="indexterm" href="primer.html#id2632087">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#id2606820">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#id2617736">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2622405">Technical Issues</a>, <a class="indexterm" href="primer.html#id2631710">Assignment Tasks</a></dt><dt>budgetted, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>bug fixes, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>bug report, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>cache, <a class="indexterm" href="appendix.html#id2631322">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#id2626091">Samba Configuration</a></dt><dt>case-sensitive, <a class="indexterm" href="DomApps.html#id2622828">Kerberos Configuration</a></dt><dt>centralized storage, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>character set, <a class="indexterm" href="upgrades.html#id2605445">International Language Support</a></dt><dt>check samba daemons, <a class="indexterm" href="small.html#id2563413">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>check-point, <a class="indexterm" href="kerberos.html#id2619714">Share Definition Controls</a></dt><dt>check-point controls, <a class="indexterm" href="kerberos.html#id2619854">Checkpoint Controls</a></dt><dt>Checkpoint Controls, <a class="indexterm" href="kerberos.html#id2619854">Checkpoint Controls</a></dt><dt>chgrp, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a></dt><dt>chkconfig, <a class="indexterm" href="simple.html#id2557141">Implementation</a>, <a class="indexterm" href="simple.html#id2558033">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2561869">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#id2591160">Implementation</a></dt><dt>chmod, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a></dt><dt>choice, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2617736">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#id2604385">Security Identifiers (SIDs)</a>, <a class="indexterm" href="primer.html#id2632087">Findings</a></dt><dt>cifsfs, <a class="indexterm" href="HA.html#id2625115">Dissection and Discussion</a></dt><dt>clean database, <a class="indexterm" href="ntmigration.html#id2611114">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#id2622828">Kerberos Configuration</a></dt><dt>cluster, <a class="indexterm" href="HA.html#id2625018">Introduction</a></dt><dt>clustering, <a class="indexterm" href="HA.html#id2625018">Introduction</a>, <a class="indexterm" href="HA.html#id2626516">For Scalability, Use SAN-Based Storage on Samba Servers</a></dt><dt>code maintainer, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt><dt>codepage, <a class="indexterm" href="upgrades.html#id2605445">International Language Support</a></dt><dt>collision rates, <a class="indexterm" href="HA.html#id2625992">Network Collisions</a></dt><dt>commercial, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>commercial software, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>commercial support, <a class="indexterm" href="ch14.html">Samba Support</a>, <a class="indexterm" href="ch14.html#id2627306">Commercial Support</a></dt><dt>Common Internet File System (see CIFS)</dt><dt>comparison</dt><dd><dl><dt>Active Directory & OpenLDAP, <a class="indexterm" href="happy.html#id2577483">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#id2617736">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#id2625115">Dissection and Discussion</a></dt><dt>compromise, <a class="indexterm" href="happy.html#id2577248">Introduction</a>, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>computer account, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a></dt><dt>Computer Management, <a class="indexterm" href="kerberos.html#id2619366">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>computer name, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>condemns, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>conferences, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>configuration files, <a class="indexterm" href="upgrades.html#id2604185">Introduction</a></dt><dt>configure.pl, <a class="indexterm" href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a></dt><dt>connection, <a class="indexterm" href="kerberos.html#id2619366">Share Access Controls</a></dt><dt>connectivity, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>consequential risk, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>consultant, <a class="indexterm" href="simple.html#id2557004">Drafting Office</a>, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a>, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>consumer, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2617736">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#id2591160">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#id2606494">Updating a Samba-3 Installation</a></dt><dt>convmv, <a class="indexterm" href="upgrades.html#id2605445">International Language Support</a></dt><dt>copy, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>corrective action, <a class="indexterm" href="HA.html#id2626666">Hardware Problems</a></dt><dt>cost, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>cost-benefit, <a class="indexterm" href="nw4migration.html#id2612206">Assignment Tasks</a></dt><dt>country of origin, <a class="indexterm" href="ch14.html#id2627306">Commercial Support</a></dt><dt>Courier-IMAP, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>credential, <a class="indexterm" href="kerberos.html#id2619714">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#id2617736">Technical Issues</a></dt><dt>crippled, <a class="indexterm" href="ntmigration.html#id2607534">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#id2616672">Introduction</a></dt><dt>Critics, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>Cryptographic, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>CUPS, <a class="indexterm" href="simple.html#id2557838">Dissection and Discussion</a>, <a class="indexterm" href="small.html#id2561650">Technical Issues</a>, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="small.html#id2564087">Key Points Learned</a>, <a class="indexterm" href="secure.html#id2565406">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2572445">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#id2577346">Assignment Tasks</a>, <a class="indexterm" href="happy.html#id2578906">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#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2572445">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#id2604385">Security Identifiers (SIDs)</a>, <a class="indexterm" href="DomApps.html#id2622405">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2628434">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#id2603025">Questions and Answers</a></dt></dl></dd><dt>data corruption, <a class="indexterm" href="HA.html#id2626666">Hardware Problems</a>, <a class="indexterm" href="appendix.html#id2631238">Act! Database Sharing</a></dt><dt>data integrity, <a class="indexterm" href="HA.html#id2626666">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#id2589924">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2612318">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#id2619019">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#id2628013">Samba System File Location</a></dt><dt>default password, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>default profile, <a class="indexterm" href="happy.html#id2577346">Assignment Tasks</a>, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a></dt><dt>Default User, <a class="indexterm" href="happy.html#id2578753">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#id2626666">Hardware Problems</a></dt><dt>HUBs, <a class="indexterm" href="HA.html#id2626666">Hardware Problems</a></dt><dt>switches, <a class="indexterm" href="HA.html#id2626666">Hardware Problems</a></dt></dl></dd><dt>defects, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>defensible standards, <a class="indexterm" href="kerberos.html#id2617736">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#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>delete user from group script, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>delimiter, <a class="indexterm" href="kerberos.html#id2619854">Checkpoint Controls</a></dt><dt>dependability, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>deployment, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt><dt>desired security setting, <a class="indexterm" href="kerberos.html#id2621257">Setting Posix ACLs in UNIX/Linux</a></dt><dt>development, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>DHCP, <a class="indexterm" href="small.html#id2561650">Technical Issues</a>, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="small.html#id2564087">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#id2590330">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt><dd><dl><dt>client, <a class="indexterm" href="HA.html#id2625627">Bad Hostnames</a></dt><dt>relay, <a class="indexterm" href="Big500users.html#id2571492">Technical Issues</a></dt><dt>Relay Agent, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt><dt>request, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt><dt>requests, <a class="indexterm" href="Big500users.html#id2571492">Technical Issues</a></dt><dt>servers, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt><dt>traffic, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt></dl></dd><dt>dhcp client validation, <a class="indexterm" href="small.html#id2563413">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>DHCP Server, <a class="indexterm" href="small.html#id2561869">Implementation</a></dt><dt>DHCP server, <a class="indexterm" href="secure.html#id2564939">Technical Issues</a></dt><dt>diagnostic, <a class="indexterm" href="unixclients.html#id2601464">IDMAP Storage in LDAP using Winbind</a></dt><dt>diffusion, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>digital rights, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>digital sign'n'seal, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>digits, <a class="indexterm" href="HA.html#id2625627">Bad Hostnames</a></dt><dt>diligence, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>directory, <a class="indexterm" href="2000users.html#id2589924">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#id2596090">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#id2582912">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>management, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a></dt><dt>People container, <a class="indexterm" href="happy.html#id2582912">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>replication, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a></dt><dt>schema, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a></dt><dt>server, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a></dt><dt>synchronization, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a></dt></dl></dd><dt>directory tree, <a class="indexterm" href="kerberos.html#id2621257">Setting Posix ACLs in UNIX/Linux</a></dt><dt>disable, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>disaster recovery, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>disk image, <a class="indexterm" href="happy.html#id2577346">Assignment Tasks</a></dt><dt>disruptive, <a class="indexterm" href="ntmigration.html#id2607534">Dissection and Discussion</a></dt><dt>distributed, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2591160">Implementation</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="HA.html#id2626565">Distribute Network Load with MSDFS</a></dt><dt>distributed domain, <a class="indexterm" href="2000users.html#id2590677">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#id2604385">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2606820">Replacing a Domain Member Server</a></dt><dt>DNS, <a class="indexterm" href="small.html#id2561650">Technical Issues</a>, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#id2564939">Technical Issues</a>, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a>, <a class="indexterm" href="HA.html#id2625627">Bad Hostnames</a>, <a class="indexterm" href="HA.html#id2625819">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#id2603025">Questions and Answers</a></dt><dt>Dynamic, <a class="indexterm" href="2000users.html#id2594466">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#id2603025">Questions and Answers</a>, <a class="indexterm" href="DomApps.html#id2622828">Kerberos Configuration</a></dt><dt>name lookup, <a class="indexterm" href="HA.html#id2625627">Bad Hostnames</a></dt><dt>SRV records, <a class="indexterm" href="DomApps.html#id2622828">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#id2561869">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#id2626091">Samba Configuration</a></dt><dt>documentation, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>documented, <a class="indexterm" href="HA.html#id2626091">Samba Configuration</a></dt><dt>Domain, <a class="indexterm" href="small.html#id2561650">Technical Issues</a></dt><dd><dl><dt>groups, <a class="indexterm" href="small.html#id2561650">Technical Issues</a></dt></dl></dd><dt>domain</dt><dd><dl><dt>Active Directory, <a class="indexterm" href="DomApps.html#id2622405">Technical Issues</a></dt><dt>controller, <a class="indexterm" href="upgrades.html#id2607022">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#id2603025">Questions and Answers</a></dt></dl></dd><dt>Domain accounts, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>Domain Administrator, <a class="indexterm" href="kerberos.html#id2619366">Share Access Controls</a></dt><dt>Domain Controller, <a class="indexterm" href="small.html#id2564087">Key Points Learned</a>, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596190">Implementation</a>, <a class="indexterm" href="HA.html#id2626419">Use and Location of BDCs</a></dt><dd><dl><dt>closest, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a></dt></dl></dd><dt>domain controller, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>domain controllers, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>Domain Controllers, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>Domain Groups</dt><dd><dl><dt>well-known, <a class="indexterm" href="appendix.html#id2629033">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#id2608210">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="ntmigration.html#id2610669">NT4 Migration Using tdbsam Backend</a></dt><dt>Domain Master Browser (see DMB)</dt><dt>Domain Member, <a class="indexterm" href="HA.html#id2626419">Use and Location of BDCs</a></dt><dd><dl><dt>authoritative</dt><dd><dl><dt>local accounts, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt></dl></dd><dt>client, <a class="indexterm" href="unixclients.html#id2596190">Implementation</a></dt><dt>desktop, <a class="indexterm" href="unixclients.html#id2595324">Introduction</a></dt><dt>server, <a class="indexterm" href="unixclients.html#id2595324">Introduction</a>, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596190">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#id2603025">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2619854">Checkpoint Controls</a></dt><dt>workstations, <a class="indexterm" href="unixclients.html#id2596190">Implementation</a></dt></dl></dd><dt>domain member</dt><dd><dl><dt>servers, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt></dl></dd><dt>Domain Member server, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>Domain Member servers, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>domain members, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>domain name space, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a></dt><dt>domain replication, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt><dt>domain SID, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>Domain SID, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>domain tree, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a></dt><dt>Domain User Manager, <a class="indexterm" href="happy.html#id2586977">Configuring Profile Directories</a></dt><dt>Domain users, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>DOS, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>dos2unix, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2573023">Configuration for Server: MASSIVE</a></dt><dt>down-grade, <a class="indexterm" href="upgrades.html#id2604185">Introduction</a></dt><dt>drive letters, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>drive mapping, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>dumb printing, <a class="indexterm" href="happy.html#id2578906">Installation of Printer Driver Auto-Download</a></dt><dt>dump, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2611114">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#id2564939">Technical Issues</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>e-Directory, <a class="indexterm" href="nw4migration.html#id2612318">Dissection and Discussion</a></dt><dt>Easy Software Products, <a class="indexterm" href="happy.html#id2578906">Installation of Printer Driver Auto-Download</a></dt><dt>economically sustainable, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>eDirectory, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a></dt><dt>education, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a></dt><dt>election, <a class="indexterm" href="primer.html#id2632087">Findings</a></dt><dt>employment, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a>, <a class="indexterm" href="kerberos.html#id2617338">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#id2633338">Findings and Comments</a></dt><dt>encrypted password, <a class="indexterm" href="primer.html#id2633603">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>encrypted passwords, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>End User License Agreement (see EULA)</dt><dt>enumerating, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a></dt><dt>essential, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>ethereal, <a class="indexterm" href="primer.html#id2631827">Exercises</a></dt><dt>Ethernet switch, <a class="indexterm" href="small.html#id2561650">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#id2617338">Dissection and Discussion</a></dt><dt>Everyone, <a class="indexterm" href="kerberos.html#id2619366">Share Access Controls</a></dt><dt>Excel, <a class="indexterm" href="kerberos.html#id2620328">Share Point Directory and File Permissions</a></dt><dt>exclusive open, <a class="indexterm" href="appendix.html#id2631091">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#id2607720">Technical Issues</a></dt><dt>extent, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>External Domains, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>extreme demand, <a class="indexterm" href="HA.html#id2625588">Guidelines for Reliable Samba Operation</a></dt></dl></div><div class="indexdiv"><h3>F</h3><dl><dt>fail, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a></dt><dt>fail-over, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2591160">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#id2600860">IDMAP_RID with Winbind</a></dt><dt>failure, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a></dt><dt>familiar, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>fatal problem, <a class="indexterm" href="HA.html#id2626091">Samba Configuration</a></dt><dt>fear, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>fears, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>Fedora, <a class="indexterm" href="simple.html#id2557004">Drafting Office</a></dt><dt>FHS, <a class="indexterm" href="appendix.html#id2628013">Samba System File Location</a></dt><dt>file and print server, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dt>file and print service, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>file caching, <a class="indexterm" href="HA.html#id2626091">Samba Configuration</a>, <a class="indexterm" href="appendix.html#id2631322">Opportunistic Locking Controls</a></dt><dt>File Hierarchy System (see FHS)</dt><dt>file locations, <a class="indexterm" href="appendix.html#id2628013">Samba System File Location</a></dt><dt>file permissions, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>file server</dt><dd><dl><dt>read-only, <a class="indexterm" href="simple.html#id2557084">Dissection and Discussion</a></dt></dl></dd><dt>file servers, <a class="indexterm" href="happy.html#id2580015">Samba Server Implementation</a></dt><dt>file system, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dd><dl><dt>access control, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a></dt><dt>Ext3, <a class="indexterm" href="simple.html#id2557141">Implementation</a></dt><dt>permissions, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2573023">Configuration for Server: MASSIVE</a></dt></dl></dd><dt>file system security, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>filter, <a class="indexterm" href="kerberos.html#id2619366">Share Access Controls</a></dt><dt>financial responsibility, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>firewall, <a class="indexterm" href="secure.html#id2564939">Technical Issues</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>fix, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>flaws, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>flexibility, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>flush</dt><dd><dl><dt>cache memory, <a class="indexterm" href="appendix.html#id2631322">Opportunistic Locking Controls</a></dt></dl></dd><dt>folder redirection, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a>, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a>, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt><dt>force group, <a class="indexterm" href="kerberos.html#id2620166">Override Controls</a>, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>force user, <a class="indexterm" href="simple.html#id2557838">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2620166">Override Controls</a>, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>forced settings, <a class="indexterm" href="kerberos.html#id2620166">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#id2625819">Routed Networks</a></dt><dt>foundation members, <a class="indexterm" href="kerberos.html#id2617736">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#id2627087">Free Support</a></dt><dt>front-end, <a class="indexterm" href="HA.html#id2625115">Dissection and Discussion</a></dt><dd><dl><dt>server, <a class="indexterm" href="HA.html#id2626565">Distribute Network Load with MSDFS</a></dt></dl></dd><dt>frustration, <a class="indexterm" href="upgrades.html#id2604185">Introduction</a></dt><dt>FSG, <a class="indexterm" href="appendix.html#id2628013">Samba System File Location</a></dt><dt>FTP</dt><dd><dl><dt>proxy, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt></dl></dd><dt>full control, <a class="indexterm" href="kerberos.html#id2619366">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2621086">Using MS Windows Explorer (File Manager)</a></dt><dt>fully qualified, <a class="indexterm" href="kerberos.html#id2619854">Checkpoint Controls</a></dt><dt>functional differences, <a class="indexterm" href="upgrades.html#id2604281">Cautions and Notes</a></dt></dl></div><div class="indexdiv"><h3>G</h3><dl><dt>generation, <a class="indexterm" href="upgrades.html#id2604281">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#id2582912">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#id2600860">IDMAP_RID with Winbind</a></dt><dt>getfacl, <a class="indexterm" href="kerberos.html#id2621257">Setting Posix ACLs in UNIX/Linux</a></dt><dt>getgrnam, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>getpwnam, <a class="indexterm" href="unixclients.html#id2595441">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#id2603025">Questions and Answers</a></dt><dt>GID, <a class="indexterm" href="2000users.html#id2591160">Implementation</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>Goettingen, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dt>government, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a></dt><dt>GPL, <a class="indexterm" href="secure.html#id2570170">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#id2565406">Implementation</a></dt><dt>group mapping, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>group membership, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#id2566260">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#id2620328">Share Point Directory and File Permissions</a></dt><dt>group names, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>group policies, <a class="indexterm" href="ntmigration.html#id2607394">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#id2558033">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>groupdel, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>groupmem, <a class="indexterm" href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a></dt><dt>groupmod, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>GSS-API, <a class="indexterm" href="primer.html#id2633603">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>guest account, <a class="indexterm" href="primer.html#id2633338">Findings and Comments</a>, <a class="indexterm" href="primer.html#chap01conc">Dissection and Discussion</a>, <a class="indexterm" href="primer.html#id2634286">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#id2616672">Introduction</a></dt><dt>hardware prices, <a class="indexterm" href="HA.html#id2626666">Hardware Problems</a></dt><dt>hardware problems, <a class="indexterm" href="HA.html#id2626666">Hardware Problems</a></dt><dt>Heimdal, <a class="indexterm" href="DomApps.html#id2622578">Implementation</a>, <a class="indexterm" href="DomApps.html#id2622828">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#id2619019">Kerberos Exposed</a></dt><dt>Heimdal kerberos, <a class="indexterm" href="unixclients.html#id2601464">IDMAP Storage in LDAP using Winbind</a></dt><dt>help, <a class="indexterm" href="ch14.html#id2627087">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#id2619714">Share Definition Controls</a></dt><dt>high availability, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a></dt><dt>hire, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>HKEY_CURRENT_USER, <a class="indexterm" href="happy.html#id2578452">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#id2594466">Questions and Answers</a></dt><dt>host announcement, <a class="indexterm" href="primer.html#id2631710">Assignment Tasks</a>, <a class="indexterm" href="primer.html#id2632740">Findings</a></dt><dt>hostname, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>hosts, <a class="indexterm" href="unixclients.html#id2603025">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#id2616672">Introduction</a></dt></dl></div><div class="indexdiv"><h3>I</h3><dl><dt>Idealx, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2608210">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#id2582912">LDAP Initialization and Creation of User and Group Accounts</a></dt></dl></dd><dt>identifiers, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>identity, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2619019">Kerberos Exposed</a></dt><dd><dl><dt>management, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a></dt></dl></dd><dt>identity management, <a class="indexterm" href="Big500users.html#id2571492">Technical Issues</a>, <a class="indexterm" href="2000users.html#id2589924">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#id2596090">Political Issues</a>, <a class="indexterm" href="nw4migration.html#id2612318">Dissection and Discussion</a></dt><dt>Identity Management, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a></dt><dt>Identity management, <a class="indexterm" href="unixclients.html#id2602396">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#id2602396">UNIX/Linux Client Domain Member</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>Identity resolver, <a class="indexterm" href="DomApps.html#id2624491">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#id2600860">IDMAP_RID with Winbind</a></dt><dt>idmap backend, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>IDMAP backend, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>idmap gid, <a class="indexterm" href="unixclients.html#id2600860">IDMAP_RID with Winbind</a></dt><dt>idmap uid, <a class="indexterm" href="unixclients.html#id2600860">IDMAP_RID with Winbind</a></dt><dt>idmap_rid, <a class="indexterm" href="unixclients.html#id2600860">IDMAP_RID with Winbind</a></dt><dt>IMAP, <a class="indexterm" href="nw4migration.html#id2612395">Technical Issues</a></dt><dt>import, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a></dt><dt>income, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>independent expert, <a class="indexterm" href="kerberos.html#id2616672">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#id2612395">Technical Issues</a></dt><dt>inheritance, <a class="indexterm" href="kerberos.html#id2621257">Setting Posix ACLs in UNIX/Linux</a></dt><dt>initGrps.sh, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2573023">Configuration for Server: MASSIVE</a></dt><dt>initial credentials, <a class="indexterm" href="DomApps.html#id2622828">Kerberos Configuration</a></dt><dt>inoperative, <a class="indexterm" href="ntmigration.html#id2607534">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#id2617338">Dissection and Discussion</a></dt><dt>integrate, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>integrity, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a>, <a class="indexterm" href="kerberos.html#id2619019">Kerberos Exposed</a></dt><dt>inter-domain, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>inter-operability, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2621467">Key Points Learned</a>, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dt>interactive help, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt><dt>interdomain trusts, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a></dt><dt>interfaces, <a class="indexterm" href="secure.html#id2565406">Implementation</a></dt><dt>intermittent, <a class="indexterm" href="HA.html#id2626666">Hardware Problems</a></dt><dt>internationalization, <a class="indexterm" href="upgrades.html#id2605445">International Language Support</a></dt><dt>Internet Explorer, <a class="indexterm" href="DomApps.html#id2622405">Technical Issues</a></dt><dt>Internet Information Server, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dt>interoperability, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a></dt><dt>IP forwarding, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="Big500users.html#id2573023">Configuration for Server: MASSIVE</a></dt><dt>IPC$, <a class="indexterm" href="primer.html#id2633338">Findings and Comments</a></dt><dt>iptables, <a class="indexterm" href="secure.html#id2564939">Technical Issues</a></dt><dt>IRC, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt><dt>isolated, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>Italian, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt></dl></div><div class="indexdiv"><h3>J</h3><dl><dt>jobs, <a class="indexterm" href="kerberos.html#id2616672">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#id2622828">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#id2603025">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2621467">Key Points Learned</a>, <a class="indexterm" href="DomApps.html#id2622405">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2622578">Implementation</a>, <a class="indexterm" href="DomApps.html#id2622828">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#id2619019">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#id2619019">Kerberos Exposed</a></dt></dl></dd><dt>kerberos, <a class="indexterm" href="kerberos.html#id2619019">Kerberos Exposed</a></dt><dd><dl><dt>server, <a class="indexterm" href="kerberos.html#id2619019">Kerberos Exposed</a></dt></dl></dd><dt>Kerberos ticket, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a></dt><dt>kinit, <a class="indexterm" href="DomApps.html#id2622828">Kerberos Configuration</a></dt><dt>Kixtart, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>klist, <a class="indexterm" href="DomApps.html#id2622828">Kerberos Configuration</a></dt><dt>krb5, <a class="indexterm" href="DomApps.html#id2622578">Implementation</a></dt><dt>krb5.conf, <a class="indexterm" href="DomApps.html#id2622828">Kerberos Configuration</a></dt></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>LAM, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dd><dl><dt>configuration editor, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>configuration file, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>login screen, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>opening screen, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>profile, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>wizard, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt></dl></dd><dt>large domain, <a class="indexterm" href="unixclients.html#id2600860">IDMAP_RID with Winbind</a></dt><dt>LDAP, <a class="indexterm" href="Big500users.html#id2571492">Technical Issues</a>, <a class="indexterm" href="happy.html#id2577346">Assignment Tasks</a>, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a>, <a class="indexterm" href="happy.html#id2579096">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#id2589825">Introduction</a>, <a class="indexterm" href="2000users.html#id2589924">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2591160">Implementation</a>, <a class="indexterm" href="2000users.html#id2594319">Key Points Learned</a>, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a>, <a class="indexterm" href="unixclients.html#id2595441">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#id2603025">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2607479">Assignment Tasks</a>, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2612318">Dissection and Discussion</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dd><dl><dt>backend, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a></dt><dt>database, <a class="indexterm" href="happy.html#id2582912">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2594466">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#id2577106">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a></dt><dt>fail-over, <a class="indexterm" href="2000users.html#id2591160">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#id2590677">Identity Management Needs</a></dt><dt>master/slave</dt><dd><dl><dt>background communication, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt></dl></dd><dt>preload, <a class="indexterm" href="2000users.html#id2591160">Implementation</a></dt><dt>schema, <a class="indexterm" href="upgrades.html#id2606638">Updating from Samba Versions between 3.0.6 and 3.0.10</a></dt><dt>secure, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a></dt><dt>server, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>slave, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a></dt><dt>updates, <a class="indexterm" href="2000users.html#id2590677">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#id2607720">Technical Issues</a></dt><dt>LDAP database, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>LDAP Interchange Format (see LDIF)</dt><dt>LDAP server, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a></dt><dt>LDAP-transfer-LDIF.txt, <a class="indexterm" href="2000users.html#id2591160">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#id2582912">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#id2582912">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="2000users.html#id2589924">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#id2606638">Updating from Samba Versions between 3.0.6 and 3.0.10</a>, <a class="indexterm" href="ntmigration.html#id2607479">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#id2582912">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>LDIF, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a>, <a class="indexterm" href="2000users.html#id2591160">Implementation</a>, <a class="indexterm" href="nw4migration.html#id2612395">Technical Issues</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a>, <a class="indexterm" href="appendix.html#id2629033">Initialization of the LDAP Database</a></dt><dt>leadership, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>Lightweight Directory Access Protocol (see LDAP)</dt><dt>limit, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>Linux desktop, <a class="indexterm" href="unixclients.html#id2595324">Introduction</a></dt><dt>Linux Standards Base (see LSB)</dt><dt>LMB, <a class="indexterm" href="primer.html#id2632087">Findings</a>, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dt>LMHOSTS, <a class="indexterm" href="HA.html#id2625819">Routed Networks</a></dt><dt>load distribution, <a class="indexterm" href="HA.html#id2626516">For Scalability, Use SAN-Based Storage on Samba Servers</a></dt><dt>local accounts, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>Local Group Policy, <a class="indexterm" href="happy.html#id2578452">Roaming Profile Background</a></dt><dt>Local Master Announcement, <a class="indexterm" href="primer.html#id2632740">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#id2625627">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#id2564939">Technical Issues</a></dt><dt>loglevel, <a class="indexterm" href="happy.html#id2579330">Debugging LDAP</a></dt><dt>logon credentials, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dt>logon hours, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2621467">Key Points Learned</a></dt><dt>logon machines, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a></dt><dt>logon path, <a class="indexterm" href="secure.html#id2565406">Implementation</a></dt><dt>logon process, <a class="indexterm" href="unixclients.html#id2596190">Implementation</a></dt><dt>logon scrip, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a></dt><dt>logon script, <a class="indexterm" href="secure.html#id2565406">Implementation</a>, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a>, <a class="indexterm" href="happy.html#id2587221">Preparation of Logon Scripts</a>, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a></dt><dt>logon server, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a></dt><dt>logon services, <a class="indexterm" href="secure.html#id2565406">Implementation</a></dt><dt>logon time, <a class="indexterm" href="happy.html#id2577346">Assignment Tasks</a></dt><dt>logon traffic, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a></dt><dt>logon.kix, <a class="indexterm" href="nw4migration.html#id2612670">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#id2626666">Hardware Problems</a></dt><dt>lower-case, <a class="indexterm" href="ntmigration.html#id2608069">Implementation</a></dt><dt>lpadmin, <a class="indexterm" href="simple.html#id2558033">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2561869">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#id2628013">Samba System File Location</a></dt></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>machine, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>machine account, <a class="indexterm" href="happy.html#id2577106">Regarding LDAP Directories and Windows Computer Accounts</a></dt><dt>machine accounts, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>machine secret password, <a class="indexterm" href="Big500users.html#id2571492">Technical Issues</a></dt><dt>MACHINE.SID, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>mailing list, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt><dt>mailing lists, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt><dt>managed, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>management, <a class="indexterm" href="unixclients.html#id2596090">Political Issues</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dd><dl><dt>group, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>User, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt></dl></dd><dt>mandatory profile, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a>, <a class="indexterm" href="happy.html#id2586977">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#id2603025">Questions and Answers</a></dt><dt>mapping, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2622828">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#id2589924">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#id2612670">LDAP Server Configuration</a></dt><dt>memory requirements, <a class="indexterm" href="secure.html#id2565213">Hardware Requirements</a></dt><dt>merge, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>merged, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a></dt><dt>meta-directory, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt><dt>meta-service, <a class="indexterm" href="kerberos.html#id2621601">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#id2622261">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#id2620328">Share Point Directory and File Permissions</a></dt><dt>Microsoft Outlook</dt><dd><dl><dt>PST files, <a class="indexterm" href="2000users.html#id2594466">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#id2607720">Technical Issues</a></dt><dt>migration, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="happy.html#id2577346">Assignment Tasks</a>, <a class="indexterm" href="ntmigration.html#id2607394">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2611114">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#id2607534">Dissection and Discussion</a></dt></dl></dd><dt>Migration speed, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>mime type, <a class="indexterm" href="simple.html#id2558033">Implementation</a>, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2572445">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#id2617736">Technical Issues</a></dt><dt>MIT, <a class="indexterm" href="DomApps.html#id2622578">Implementation</a>, <a class="indexterm" href="DomApps.html#id2622828">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#id2619019">Kerberos Exposed</a></dt><dt>MIT kerberos, <a class="indexterm" href="unixclients.html#id2601464">IDMAP Storage in LDAP using Winbind</a></dt><dt>MIT KRB5, <a class="indexterm" href="DomApps.html#id2623217">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#id2621601">Questions and Answers</a></dt><dt>MMC, <a class="indexterm" href="happy.html#id2588536">Configure Delete Cached Profiles on Logout</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>mobile computing, <a class="indexterm" href="small.html#id2561602">Dissection and Discussion</a></dt><dt>mobility, <a class="indexterm" href="2000users.html#id2590197">Technical Issues</a></dt><dt>modularization, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>modules, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dt>MS Access</dt><dd><dl><dt>validate, <a class="indexterm" href="appendix.html#id2631091">Microsoft Access</a></dt></dl></dd><dt>MS Outlook, <a class="indexterm" href="happy.html#id2588220">Configuration of MS Outlook to Relocate PST File</a></dt><dd><dl><dt>PST, <a class="indexterm" href="happy.html#id2588220">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#id2622578">Implementation</a></dt><dt>MS Word, <a class="indexterm" href="kerberos.html#id2620328">Share Point Directory and File Permissions</a></dt><dt>MSDFS, <a class="indexterm" href="HA.html#id2626565">Distribute Network Load with MSDFS</a></dt><dt>multi-subnet, <a class="indexterm" href="HA.html#id2625819">Routed Networks</a></dt><dt>multi-user</dt><dd><dl><dt>access, <a class="indexterm" href="appendix.html#id2631091">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#id2590677">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#id2611114">Questions and Answers</a></dt><dt>mutual assistance, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt><dt>My Documents, <a class="indexterm" href="happy.html#id2578452">Roaming Profile Background</a></dt><dt>My Network Places, <a class="indexterm" href="simple.html#id2558033">Implementation</a></dt><dt>mysqlsam, <a class="indexterm" href="2000users.html#id2591160">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#id2603025">Questions and Answers</a>, <a class="indexterm" href="primer.html#id2631710">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#id2565406">Implementation</a></dt><dt>name service switch, <a class="indexterm" href="small.html#id2561869">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#id2572445">Server Preparation: All Servers</a></dt><dt>NAT, <a class="indexterm" href="secure.html#id2564939">Technical Issues</a></dt><dt>native, <a class="indexterm" href="kerberos.html#id2621601">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#id2603025">Questions and Answers</a>, <a class="indexterm" href="DomApps.html#id2623217">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#id2604385">Security Identifiers (SIDs)</a></dt><dt>group, <a class="indexterm" href="ntmigration.html#id2610669">NT4 Migration Using tdbsam Backend</a></dt><dt>groupmap</dt><dd><dl><dt>add, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a></dt><dt>list, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a>, <a class="indexterm" href="happy.html#id2582912">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>modify, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a></dt></dl></dd><dt>rpc</dt><dd><dl><dt>info, <a class="indexterm" href="upgrades.html#id2604385">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#id2603025">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2610669">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#id2610669">NT4 Migration Using tdbsam Backend</a></dt></dl></dd><dt>setlocalsid, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt></dl></dd><dt>NetBIOS, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="HA.html#id2625627">Bad Hostnames</a>, <a class="indexterm" href="HA.html#id2625819">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#id2594466">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#id2605113">Change of hostname</a></dt></dl></dd><dt>netbios forwarding, <a class="indexterm" href="HA.html#id2625992">Network Collisions</a></dt><dt>NetBIOS name, <a class="indexterm" href="DomApps.html#id2622828">Kerberos Configuration</a></dt><dd><dl><dt>aliases, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a></dt></dl></dd><dt>netbios name, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2605113">Change of hostname</a>, <a class="indexterm" href="HA.html#id2625627">Bad Hostnames</a></dt><dt>NETLOGON, <a class="indexterm" href="happy.html#id2578847">Using a Network Default User Profile</a>, <a class="indexterm" href="happy.html#id2587466">Windows Client Configuration</a></dt><dt>netlogon, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="nw4migration.html#id2612670">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#id2557141">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#id2612670">LDAP Server Configuration</a></dt><dt>network</dt><dd><dl><dt>administrators, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>analyzer, <a class="indexterm" href="primer.html#id2631710">Assignment Tasks</a></dt><dt>bandwidth, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt><dt>broadcast, <a class="indexterm" href="primer.html#id2631650">Introduction</a></dt><dt>captures, <a class="indexterm" href="primer.html#id2631489">Requirements and Notes</a></dt><dt>collisions, <a class="indexterm" href="HA.html#id2625992">Network Collisions</a></dt><dt>load, <a class="indexterm" href="HA.html#id2625992">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#id2607534">Dissection and Discussion</a></dt><dt>management, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>multi-segment, <a class="indexterm" href="happy.html#id2577248">Introduction</a></dt><dt>overload, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>performance, <a class="indexterm" href="HA.html#id2626091">Samba Configuration</a></dt><dt>routed, <a class="indexterm" href="2000users.html#id2589924">Dissection and Discussion</a></dt><dt>secure, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>segment, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a></dt><dt>services, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dt>sniffer, <a class="indexterm" href="primer.html#id2631489">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#id2625992">Network Collisions</a></dt><dt>trace, <a class="indexterm" href="primer.html#id2631710">Assignment Tasks</a></dt><dt>traffic</dt><dd><dl><dt>observation, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt></dl></dd><dt>wide-area, <a class="indexterm" href="happy.html#id2577483">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#id2617736">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#id2578452">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#id2625115">Dissection and Discussion</a></dt><dt>network Identities, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>network load factors, <a class="indexterm" href="Big500users.html#id2571456">Dissection and Discussion</a></dt><dt>Network Neighborhood, <a class="indexterm" href="simple.html#validate1">Validation</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>network segment, <a class="indexterm" href="HA.html#id2626419">Use and Location of BDCs</a></dt><dt>network segments, <a class="indexterm" href="secure.html#id2565213">Hardware Requirements</a></dt><dt>network share, <a class="indexterm" href="happy.html#id2577346">Assignment Tasks</a></dt><dt>networking</dt><dd><dl><dt>client, <a class="indexterm" href="upgrades.html#id2604385">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#id2617736">Technical Issues</a></dt><dt>next generation, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>NextFreeUnixId, <a class="indexterm" href="ntmigration.html#id2608210">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#id2626666">Hardware Problems</a></dt><dt>NIS, <a class="indexterm" href="happy.html#id2582912">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a>, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596090">Political Issues</a>, <a class="indexterm" href="unixclients.html#id2603025">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#id2594466">Questions and Answers</a></dt><dt>NIS server, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt><dt>NIS+, <a class="indexterm" href="2000users.html#id2590677">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#id2563413">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#id2606820">Replacing a Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a>, <a class="indexterm" href="appendix.html#id2628434">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#id2633338">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#id2612089">Introduction</a></dt><dt>Novell SUSE SLES 9, <a class="indexterm" href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a></dt><dt>NSS, <a class="indexterm" href="happy.html#id2577106">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a>, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="unixclients.html#id2595441">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#id2600860">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2602396">UNIX/Linux Client Domain Member</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a>, <a class="indexterm" href="DomApps.html#id2623769">NSS Configuration</a> (see same service switch)</dt><dt>nss_ldap, <a class="indexterm" href="happy.html#id2577106">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="happy.html#id2577941">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#id2582912">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="unixclients.html#id2595441">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#id2602059">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="upgrades.html#id2606820">Replacing a Domain Member Server</a>, <a class="indexterm" href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a></dt><dt>nt acl support, <a class="indexterm" href="simple.html#id2557838">Dissection and Discussion</a></dt><dt>NT4 registry, <a class="indexterm" href="ntmigration.html#id2607534">Dissection and Discussion</a></dt><dt>NTLM, <a class="indexterm" href="DomApps.html#id2622405">Technical Issues</a></dt><dt>NTLM authentication daemon, <a class="indexterm" href="DomApps.html#id2622405">Technical Issues</a></dt><dt>NTLMSSP, <a class="indexterm" href="DomApps.html#id2624430">Key Points Learned</a>, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a>, <a class="indexterm" href="primer.html#id2633603">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>NTLMSSP_AUTH, <a class="indexterm" href="primer.html#id2633603">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>ntlm_auth, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dt>NTP, <a class="indexterm" href="DomApps.html#id2622828">Kerberos Configuration</a></dt><dt>NTUSER.DAT, <a class="indexterm" href="happy.html#id2578452">Roaming Profile Background</a>, <a class="indexterm" href="happy.html#id2578753">Profile Changes</a>, <a class="indexterm" href="happy.html#id2578847">Using a Network Default User Profile</a>, <a class="indexterm" href="2000users.html#id2594466">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#id2633338">Findings and Comments</a></dt><dt>NULL-Session, <a class="indexterm" href="primer.html#id2634140">Discussion</a></dt></dl></div><div class="indexdiv"><h3>O</h3><dl><dt>objectClass, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>off-site storage, <a class="indexterm" href="kerberos.html#id2616672">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#id2617338">Dissection and Discussion</a></dt><dt>OpenLDAP, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2589924">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a>, <a class="indexterm" href="unixclients.html#id2596090">Political Issues</a>, <a class="indexterm" href="nw4migration.html#id2612395">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2621467">Key Points Learned</a>, <a class="indexterm" href="appendix.html#id2629619">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#id2629619">The LDAP Account Manager</a></dt><dt>oplock break, <a class="indexterm" href="kerberos.html#id2620166">Override Controls</a></dt><dt>oplocks, <a class="indexterm" href="HA.html#id2626091">Samba Configuration</a></dt><dt>Oplocks</dt><dd><dl><dt>disabled, <a class="indexterm" href="appendix.html#id2631322">Opportunistic Locking Controls</a></dt></dl></dd><dt>opportunistic</dt><dd><dl><dt>locking, <a class="indexterm" href="kerberos.html#id2620166">Override Controls</a></dt></dl></dd><dt>opportunistic locking, <a class="indexterm" href="secure.html#id2565406">Implementation</a>, <a class="indexterm" href="HA.html#id2626091">Samba Configuration</a>, <a class="indexterm" href="appendix.html#id2631238">Act! Database Sharing</a></dt><dt>optimized, <a class="indexterm" href="HA.html#id2626091">Samba Configuration</a></dt><dt>organizational units, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>OS/2, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>Outlook</dt><dd><dl><dt>PST, <a class="indexterm" href="happy.html#id2588220">Configuration of MS Outlook to Relocate PST File</a></dt></dl></dd><dt>Outlook Address Book, <a class="indexterm" href="happy.html#id2588220">Configuration of MS Outlook to Relocate PST File</a></dt><dt>Outlook Express, <a class="indexterm" href="secure.html#id2565367">Political Issues</a>, <a class="indexterm" href="happy.html#id2588220">Configuration of MS Outlook to Relocate PST File</a></dt><dt>over-ride, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>over-ride controls, <a class="indexterm" href="kerberos.html#id2620166">Override Controls</a></dt><dt>over-rule, <a class="indexterm" href="kerberos.html#id2619366">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2621086">Using MS Windows Explorer (File Manager)</a></dt><dt>overheads, <a class="indexterm" href="kerberos.html#id2620166">Override Controls</a></dt><dt>ownership, <a class="indexterm" href="kerberos.html#id2620328">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#id2557141">Implementation</a></dt><dt>package names, <a class="indexterm" href="appendix.html#id2628013">Samba System File Location</a></dt><dt>packages, <a class="indexterm" href="upgrades.html#id2606494">Updating a Samba-3 Installation</a></dt><dt>PADL, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2601464">IDMAP Storage in LDAP using Winbind</a></dt><dt>PADL LDAP tools, <a class="indexterm" href="happy.html#id2577941">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#id2602396">UNIX/Linux Client Domain Member</a>, <a class="indexterm" href="nw4migration.html#id2612670">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#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>passdb backend, <a class="indexterm" href="secure.html#id2565406">Implementation</a>, <a class="indexterm" href="Big500users.html">The 500-User Office</a>, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2589924">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2591160">Implementation</a>, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="upgrades.html">Updating Samba-3</a>, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="upgrades.html#id2606638">Updating from Samba Versions between 3.0.6 and 3.0.10</a>, <a class="indexterm" href="ntmigration.html#id2607479">Assignment Tasks</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>passdb.tdb, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a></dt><dt>passwd, <a class="indexterm" href="simple.html#id2558033">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a></dt><dt>password</dt><dd><dl><dt>backend, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2573023">Configuration for Server: MASSIVE</a></dt></dl></dd><dt>password caching, <a class="indexterm" href="simple.html#id2558033">Implementation</a></dt><dt>password change, <a class="indexterm" href="kerberos.html#id2621467">Key Points Learned</a></dt><dt>password length, <a class="indexterm" href="primer.html#id2633100">Simple Windows Client Connection Characteristics</a>, <a class="indexterm" href="primer.html#id2633603">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>payroll, <a class="indexterm" href="nw4migration.html#id2612089">Introduction</a></dt><dt>pdbedit, <a class="indexterm" href="happy.html#id2582912">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#id2610669">NT4 Migration Using tdbsam Backend</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>PDC, <a class="indexterm" href="Big500users.html#id2571350">Assignment Tasks</a>, <a class="indexterm" href="Big500users.html#id2571492">Technical Issues</a>, <a class="indexterm" href="happy.html">Making Happy Users</a>, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a>, <a class="indexterm" href="happy.html#sbehap-locgrppol">The Local Group Policy</a>, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2608069">Implementation</a>, <a class="indexterm" href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="ntmigration.html#id2610669">NT4 Migration Using tdbsam Backend</a>, <a class="indexterm" href="HA.html#id2626419">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#id2629619">The LDAP Account Manager</a></dt><dt>performance, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a>, <a class="indexterm" href="HA.html">Performance, Reliability, and Availability</a>, <a class="indexterm" href="HA.html#id2625018">Introduction</a>, <a class="indexterm" href="HA.html#id2625992">Network Collisions</a></dt><dt>performance degradation, <a class="indexterm" href="kerberos.html#id2620166">Override Controls</a>, <a class="indexterm" href="HA.html#id2626091">Samba Configuration</a></dt><dt>Perl, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a>, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>permission, <a class="indexterm" href="kerberos.html#id2620328">Share Point Directory and File Permissions</a></dt><dt>permissions, <a class="indexterm" href="simple.html#id2558033">Implementation</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2619366">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2619854">Checkpoint Controls</a>, <a class="indexterm" href="kerberos.html#id2620328">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#id2617736">Technical Issues</a></dt><dt>group, <a class="indexterm" href="kerberos.html#id2620328">Share Point Directory and File Permissions</a></dt><dt>user, <a class="indexterm" href="kerberos.html#id2620328">Share Point Directory and File Permissions</a></dt></dl></dd><dt>Permissions, <a class="indexterm" href="kerberos.html#id2620795">Using the MMC Computer Management Interface</a></dt><dt>permits, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>permitted group, <a class="indexterm" href="kerberos.html#id2620795">Using the MMC Computer Management Interface</a></dt><dt>PHP, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>PHP4, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>pile-driver, <a class="indexterm" href="kerberos.html#id2619714">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#id2629619">The LDAP Account Manager</a></dt><dt>plain-text, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dt>Pluggable Authentication Modules (see PAM)</dt><dt>policy, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>poor performance, <a class="indexterm" href="HA.html#id2625115">Dissection and Discussion</a></dt><dt>POP3, <a class="indexterm" href="nw4migration.html#id2612395">Technical Issues</a></dt><dt>Posix, <a class="indexterm" href="simple.html#id2557838">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2608069">Implementation</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>POSIX, <a class="indexterm" href="happy.html#id2577106">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>Posix accounts, <a class="indexterm" href="happy.html#id2582912">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>Posix ACLs, <a class="indexterm" href="kerberos.html#id2620740">Managing Windows 200x ACLs</a></dt><dt>PosixAccount, <a class="indexterm" href="happy.html#id2582912">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>posixAccount, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>Postfix, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>Postscript, <a class="indexterm" href="happy.html#id2578906">Installation of Printer Driver Auto-Download</a></dt><dt>powers, <a class="indexterm" href="kerberos.html#id2619714">Share Definition Controls</a></dt><dt>practices, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>precaution, <a class="indexterm" href="upgrades.html#id2604185">Introduction</a></dt><dt>presence and leadership, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>price paid, <a class="indexterm" href="kerberos.html#id2617338">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#id2620328">Share Point Directory and File Permissions</a></dt><dt>principals, <a class="indexterm" href="kerberos.html#id2619019">Kerberos Exposed</a></dt><dt>print filter, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2572445">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#id2557714">Charity Administration Office</a>, <a class="indexterm" href="simple.html#id2557838">Dissection and Discussion</a></dt><dt>print spooler, <a class="indexterm" href="simple.html#id2557714">Charity Administration Office</a></dt><dt>Print Test Page, <a class="indexterm" href="happy.html#id2588716">Uploading Printer Drivers to Samba Servers</a></dt><dt>printcap name, <a class="indexterm" href="secure.html#id2565406">Implementation</a></dt><dt>printer validation, <a class="indexterm" href="small.html#id2563413">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#id2588716">Uploading Printer Drivers to Samba Servers</a></dt><dt>Default Settings, <a class="indexterm" href="happy.html#id2588716">Uploading Printer Drivers to Samba Servers</a></dt><dt>General, <a class="indexterm" href="happy.html#id2588716">Uploading Printer Drivers to Samba Servers</a></dt><dt>Properties, <a class="indexterm" href="happy.html#id2588716">Uploading Printer Drivers to Samba Servers</a></dt><dt>Security, <a class="indexterm" href="happy.html#id2588716">Uploading Printer Drivers to Samba Servers</a></dt><dt>Sharing, <a class="indexterm" href="happy.html#id2588716">Uploading Printer Drivers to Samba Servers</a></dt></dl></dd><dt>printing, <a class="indexterm" href="secure.html#id2565406">Implementation</a></dt><dd><dl><dt>drag-and-drop, <a class="indexterm" href="happy.html#id2578906">Installation of Printer Driver Auto-Download</a>, <a class="indexterm" href="happy.html#id2588716">Uploading Printer Drivers to Samba Servers</a></dt><dt>dumb, <a class="indexterm" href="happy.html#id2578906">Installation of Printer Driver Auto-Download</a></dt><dt>point-n-click, <a class="indexterm" href="happy.html#id2578906">Installation of Printer Driver Auto-Download</a></dt><dt>raw, <a class="indexterm" href="simple.html#id2557838">Dissection and Discussion</a></dt></dl></dd><dt>privacy, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a></dt><dt>Privilege Attribute Certificates (see PAC)</dt><dt>privilege controls, <a class="indexterm" href="kerberos.html#id2620328">Share Point Directory and File Permissions</a></dt><dt>privileged pipe, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a></dt><dt>privileges, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a>, <a class="indexterm" href="upgrades.html#id2606717">Updating from Samba Versions after 3.0.6 to a Current Release</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2619714">Share Definition Controls</a></dt><dt>problem report, <a class="indexterm" href="ch14.html#id2627087">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#id2617338">Dissection and Discussion</a></dt><dt>professional support, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt><dt>profile</dt><dd><dl><dt>default, <a class="indexterm" href="happy.html#id2577346">Assignment Tasks</a></dt><dt>mandatory, <a class="indexterm" href="2000users.html#id2590330">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#id2607720">Technical Issues</a></dt><dt>profile share, <a class="indexterm" href="secure.html#id2565406">Implementation</a></dt><dt>profiles, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>profiles share, <a class="indexterm" href="ntmigration.html#id2607534">Dissection and Discussion</a></dt><dt>programmer, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>project, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt><dt>project maintainers, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>Properties, <a class="indexterm" href="kerberos.html#id2620795">Using the MMC Computer Management Interface</a></dt><dt>proprietary, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>protected, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>protection, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>protocol</dt><dd><dl><dt>negotiation, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a></dt></dl></dd><dt>protocol analysis, <a class="indexterm" href="primer.html#id2631489">Requirements and Notes</a></dt><dt>protocols, <a class="indexterm" href="kerberos.html#id2617736">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#id2622261">Assignment Tasks</a>, <a class="indexterm" href="DomApps.html#id2622405">Technical Issues</a></dt><dt>PST file, <a class="indexterm" href="happy.html#id2588220">Configuration of MS Outlook to Relocate PST File</a></dt><dt>public specifications, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>purchase support, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt></dl></div><div class="indexdiv"><h3>Q</h3><dl><dt>Qbasic, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>qualified problem, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>RAID, <a class="indexterm" href="secure.html#id2565213">Hardware Requirements</a></dt><dt>RAID controllers, <a class="indexterm" href="HA.html#id2626666">Hardware Problems</a></dt><dt>Raw Print Through, <a class="indexterm" href="happy.html#id2578906">Installation of Printer Driver Auto-Download</a></dt><dt>raw printing, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2572445">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#id2612670">LDAP Server Configuration</a></dt><dt>rcldap, <a class="indexterm" href="2000users.html#id2591160">Implementation</a></dt><dt>realm, <a class="indexterm" href="unixclients.html#id2600860">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2601464">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="DomApps.html#id2622828">Kerberos Configuration</a></dt><dt>recognize, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>record locking, <a class="indexterm" href="appendix.html#id2631091">Microsoft Access</a></dt><dt>recursively, <a class="indexterm" href="kerberos.html#id2621257">Setting Posix ACLs in UNIX/Linux</a></dt><dt>Red Hat, <a class="indexterm" href="simple.html#id2557004">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#id2623217">Samba Configuration</a></dt><dt>Red Hat Linux, <a class="indexterm" href="simple.html#id2557838">Dissection and Discussion</a>, <a class="indexterm" href="simple.html#AccountingOffice">Accounting Office</a>, <a class="indexterm" href="happy.html#id2580015">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#id2591160">Implementation</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2622578">Implementation</a>, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a></dt><dt>redirected folders, <a class="indexterm" href="happy.html#id2578452">Roaming Profile Background</a>, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a></dt><dt>refereed standards, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>regedit, <a class="indexterm" href="simple.html#id2558033">Implementation</a></dt><dt>regedt32, <a class="indexterm" href="happy.html#id2578753">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#id2611114">Questions and Answers</a></dt><dd><dl><dt>keys</dt><dd><dl><dt>SAM, <a class="indexterm" href="ntmigration.html#id2607534">Dissection and Discussion</a></dt><dt>SECURITY, <a class="indexterm" href="ntmigration.html#id2607534">Dissection and Discussion</a></dt></dl></dd></dl></dd><dt>registry change, <a class="indexterm" href="kerberos.html#id2621601">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#id2621601">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#id2617338">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#id2619366">Share Access Controls</a></dt><dt>rejoin, <a class="indexterm" href="ntmigration.html#id2611114">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#id2625819">Routed Networks</a></dt><dt>remote browse sync, <a class="indexterm" href="HA.html#id2625819">Routed Networks</a></dt><dt>remote procedure call (see RPC)</dt><dt>replicate, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="HA.html#id2626620">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></dt><dt>replicated, <a class="indexterm" href="2000users.html#id2589924">Dissection and Discussion</a></dt><dt>requesting payment, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt><dt>resilient, <a class="indexterm" href="HA.html#id2625588">Guidelines for Reliable Samba Operation</a></dt><dt>resolution, <a class="indexterm" href="upgrades.html#id2606820">Replacing a Domain Member Server</a></dt><dt>resolve, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a>, <a class="indexterm" href="HA.html#id2625627">Bad Hostnames</a></dt><dt>response, <a class="indexterm" href="unixclients.html#id2600860">IDMAP_RID with Winbind</a></dt><dt>responsibility, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>responsible, <a class="indexterm" href="kerberos.html#id2617736">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#id2619019">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#id2622828">Kerberos Configuration</a></dt><dt>rfc2307bis, <a class="indexterm" href="unixclients.html#id2602059">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></dt><dt>RID, <a class="indexterm" href="unixclients.html#id2600860">IDMAP_RID with Winbind</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>risk, <a class="indexterm" href="secure.html#id2564939">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>road-map, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dd><dl><dt>published, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt></dl></dd><dt>roaming profile, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a>, <a class="indexterm" href="happy.html#id2578452">Roaming Profile Background</a>, <a class="indexterm" href="happy.html#id2586977">Configuring Profile Directories</a>, <a class="indexterm" href="2000users.html#id2590236">User Needs</a>, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt><dt>roaming profiles, <a class="indexterm" href="secure.html#id2564939">Technical Issues</a>, <a class="indexterm" href="secure.html#id2565406">Implementation</a>, <a class="indexterm" href="happy.html#id2578452">Roaming Profile Background</a></dt><dt>routed network, <a class="indexterm" href="HA.html#id2626419">Use and Location of BDCs</a></dt><dt>router, <a class="indexterm" href="small.html#id2561869">Implementation</a></dt><dt>routers, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a>, <a class="indexterm" href="HA.html#id2625819">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#id2619019">Kerberos Exposed</a></dt><dt>rpc, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>rpcclient, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>RPM, <a class="indexterm" href="upgrades.html#id2604385">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#id2612318">Dissection and Discussion</a></dt><dd><dl><dt>install, <a class="indexterm" href="simple.html#id2557141">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#id2628013">Samba System File Location</a></dt><dt>RPMs, <a class="indexterm" href="DomApps.html#id2623217">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#id2603025">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a>, <a class="indexterm" href="HA.html#id2626620">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></dt><dt>rsyncd.conf, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>run-time control files, <a class="indexterm" href="appendix.html#id2628013">Samba System File Location</a></dt></dl></div><div class="indexdiv"><h3>S</h3><dl><dt>safe-guards, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>SAM, <a class="indexterm" href="ntmigration.html#id2607534">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#id2557141">Implementation</a></dt></dl></dd><dt>Samba, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a></dt><dt>Samba accounts, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>samba cluster, <a class="indexterm" href="HA.html#id2625018">Introduction</a></dt><dt>samba control script, <a class="indexterm" href="appendix.html#id2628434">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#id2611114">Questions and Answers</a></dt><dt>Samba Domain server, <a class="indexterm" href="kerberos.html#id2620795">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#id2623217">Samba Configuration</a></dt><dt>sambaDomainName, <a class="indexterm" href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a></dt><dt>sambaGroupMapping, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>SambaSAMAccount, <a class="indexterm" href="happy.html#id2577106">Regarding LDAP Directories and Windows Computer Accounts</a></dt><dt>SambaSamAccount, <a class="indexterm" href="happy.html#id2582912">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>sambaSamAccount, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>SambaXP conference, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dt>SAN, <a class="indexterm" href="HA.html#id2626516">For Scalability, Use SAN-Based Storage on Samba Servers</a></dt><dt>SAS, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>scalability, <a class="indexterm" href="HA.html#id2625018">Introduction</a></dt><dt>scalable, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a></dt><dt>schannel, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2621467">Key Points Learned</a>, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>schema, <a class="indexterm" href="unixclients.html#id2602059">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2606312">Samba-2.x with LDAP Support</a>, <a class="indexterm" href="upgrades.html#id2606638">Updating from Samba Versions between 3.0.6 and 3.0.10</a></dt><dt>scripts, <a class="indexterm" href="appendix.html#id2629619">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#id2619019">Kerberos Exposed</a></dt><dt>secrets.tdb, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="upgrades.html#id2604385">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#id2616672">Introduction</a></dt><dt>secure account password, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>secure connections, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>secure networking, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>secure networking protocols, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>security, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a>, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2620328">Share Point Directory and File Permissions</a>, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dd><dl><dt>identifier, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>share mode, <a class="indexterm" href="simple.html#id2557838">Dissection and Discussion</a></dt><dt>user mode, <a class="indexterm" href="simple.html#id2559880">Dissection and Discussion</a></dt></dl></dd><dt>Security, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2620795">Using the MMC Computer Management Interface</a></dt><dt>Security Account Manager (see SAM)</dt><dt>security controls, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>security descriptors, <a class="indexterm" href="ntmigration.html#id2607534">Dissection and Discussion</a></dt><dt>security fixes, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>security updates, <a class="indexterm" href="kerberos.html#id2617736">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#id2623217">Samba Configuration</a></dt><dt>server</dt><dd><dl><dt>domain member, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>stand-alone, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt></dl></dd><dt>service, <a class="indexterm" href="2000users.html#id2591160">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#id2624430">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#id2633100">Simple Windows Client Connection Characteristics</a>, <a class="indexterm" href="primer.html#id2633603">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>Session Setup, <a class="indexterm" href="primer.html#id2633100">Simple Windows Client Connection Characteristics</a></dt><dt>SessionSetUpAndX, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>set primary group script, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>setfacl, <a class="indexterm" href="kerberos.html#id2621257">Setting Posix ACLs in UNIX/Linux</a></dt><dt>severely degrade, <a class="indexterm" href="HA.html#id2626091">Samba Configuration</a></dt><dt>SFU, <a class="indexterm" href="unixclients.html#id2602345">IDMAP, Active Directory, and MS Services for UNIX 3.5</a></dt><dt>SGID, <a class="indexterm" href="simple.html#id2557838">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2620328">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#id2611114">Questions and Answers</a></dt><dt>Share Access Controls, <a class="indexterm" href="kerberos.html#id2619366">Share Access Controls</a></dt><dt>share ACLs, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>share definition, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>Share Definition</dt><dd><dl><dt>Controls, <a class="indexterm" href="kerberos.html#id2619714">Share Definition Controls</a></dt></dl></dd><dt>share definition controls, <a class="indexterm" href="kerberos.html#id2619714">Share Definition Controls</a>, <a class="indexterm" href="kerberos.html#id2619854">Checkpoint Controls</a>, <a class="indexterm" href="kerberos.html#id2620328">Share Point Directory and File Permissions</a>, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>share level access controls, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>share level ACL, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>Share Permissions, <a class="indexterm" href="kerberos.html#id2619366">Share Access Controls</a></dt><dt>shared resource, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2621257">Setting Posix ACLs in UNIX/Linux</a></dt><dt>shares, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>SID, <a class="indexterm" href="secure.html#ch4wincfg">Windows Client Configuration</a>, <a class="indexterm" href="happy.html#id2577106">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a>, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2600860">IDMAP_RID with Winbind</a>, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2605179">Change of Workgroup (Domain) Name</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2629033">Initialization of the LDAP Database</a></dt><dt>side effects, <a class="indexterm" href="kerberos.html#id2620740">Managing Windows 200x ACLs</a></dt><dt>Sign'n'seal, <a class="indexterm" href="kerberos.html#id2621467">Key Points Learned</a>, <a class="indexterm" href="kerberos.html#id2621601">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#id2625115">Dissection and Discussion</a></dt><dt>Single Sign-On (see SSO)</dt><dt>slapcat, <a class="indexterm" href="happy.html#id2582912">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#id2612670">LDAP Server Configuration</a></dt><dt>slapd, <a class="indexterm" href="happy.html#id2579330">Debugging LDAP</a></dt><dt>slapd.conf, <a class="indexterm" href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a></dt><dt>slave, <a class="indexterm" href="2000users.html#id2589924">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#id2626666">Hardware Problems</a></dt><dt>slurpd, <a class="indexterm" href="2000users.html#id2591160">Implementation</a>, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt><dt>smart printing, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a></dt><dt>SMB, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>SMB passwords, <a class="indexterm" href="2000users.html#id2591160">Implementation</a></dt><dt>SMB/CIFS, <a class="indexterm" href="DomApps.html#id2624491">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#id2582912">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dt>smbd, <a class="indexterm" href="simple.html#validate1">Validation</a>, <a class="indexterm" href="simple.html#id2558033">Implementation</a>, <a class="indexterm" href="small.html#id2563413">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#id2595441">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#id2604385">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#id2606820">Replacing a Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2628434">Starting Samba</a></dt><dd><dl><dt>location of files, <a class="indexterm" href="appendix.html#id2628013">Samba System File Location</a></dt></dl></dd><dt>smbfs, <a class="indexterm" href="HA.html#id2625115">Dissection and Discussion</a></dt><dt>smbldap-groupadd, <a class="indexterm" href="happy.html#id2582912">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>smbldap-groupmod, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>smbldap-passwd, <a class="indexterm" href="happy.html#id2582912">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>smbldap-populate, <a class="indexterm" href="happy.html#id2582912">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>smbldap-tools, <a class="indexterm" href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a>, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>smbldap-tools updating, <a class="indexterm" href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a></dt><dt>smbldap-useradd, <a class="indexterm" href="happy.html#id2582912">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="2000users.html#id2591160">Implementation</a></dt><dt>smbldap-usermod, <a class="indexterm" href="happy.html#id2582912">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>smbmnt, <a class="indexterm" href="HA.html#id2625115">Dissection and Discussion</a></dt><dt>smbmount, <a class="indexterm" href="HA.html#id2625115">Dissection and Discussion</a></dt><dt>smbpasswd, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2561650">Technical Issues</a>, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#id2564939">Technical Issues</a>, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2572445">Server Preparation: All Servers</a>, <a class="indexterm" href="Big500users.html#id2573023">Configuration for Server: MASSIVE</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="happy.html#id2582912">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#id2589924">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2591160">Implementation</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="upgrades.html">Updating Samba-3</a>, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a>, <a class="indexterm" href="DomApps.html">Integrating Additional Services</a></dt><dt>smbumnt, <a class="indexterm" href="HA.html#id2625115">Dissection and Discussion</a></dt><dt>smbumount, <a class="indexterm" href="HA.html#id2625115">Dissection and Discussion</a></dt><dt>SMTP, <a class="indexterm" href="nw4migration.html#id2612395">Technical Issues</a></dt><dt>snap-shot, <a class="indexterm" href="ntmigration.html#id2607534">Dissection and Discussion</a></dt><dt>socket address, <a class="indexterm" href="HA.html#id2626091">Samba Configuration</a></dt><dt>socket options, <a class="indexterm" href="HA.html#id2626091">Samba Configuration</a></dt><dt>software, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>solve, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>source code, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>SPNEGO, <a class="indexterm" href="primer.html#id2633603">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>SQL, <a class="indexterm" href="2000users.html#id2589924">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt><dt>Squid, <a class="indexterm" href="DomApps.html#id2622578">Implementation</a>, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a>, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2624034">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#id2623217">Samba Configuration</a></dt><dt>Squid proxy, <a class="indexterm" href="DomApps.html#id2622405">Technical Issues</a></dt><dt>SRVTOOLS.EXE, <a class="indexterm" href="secure.html#id2565406">Implementation</a>, <a class="indexterm" href="happy.html#id2586977">Configuring Profile Directories</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>SSL, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>stand-alone server, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>starting CUPS, <a class="indexterm" href="simple.html#id2558033">Implementation</a>, <a class="indexterm" href="small.html#id2561869">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#id2561869">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#id2557141">Implementation</a>, <a class="indexterm" href="simple.html#id2558033">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2561869">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#id2628434">Starting Samba</a></dt><dt>smbd, <a class="indexterm" href="appendix.html#id2628434">Starting Samba</a></dt><dt>winbindd, <a class="indexterm" href="appendix.html#id2628434">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#id2628434">Starting Samba</a></dt><dt>sticky bit, <a class="indexterm" href="small.html#id2561869">Implementation</a></dt><dt>storage capacity, <a class="indexterm" href="secure.html#id2565213">Hardware Requirements</a></dt><dt>strategic, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a></dt><dt>strategy, <a class="indexterm" href="unixclients.html#id2603025">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#id2626091">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#id2619019">Kerberos Exposed</a></dt><dt>subscription, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt><dt>SUID, <a class="indexterm" href="simple.html#id2557838">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2621601">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#id2577483">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#id2617338">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#id2557714">Charity Administration Office</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="DomApps.html#id2622578">Implementation</a></dt><dt>SUSE Linux, <a class="indexterm" href="simple.html#id2557838">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2580015">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#id2591160">Implementation</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2622578">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#id2628013">Samba System File Location</a></dt><dt>sync always, <a class="indexterm" href="HA.html#id2626091">Samba Configuration</a></dt><dt>synchronization, <a class="indexterm" href="DomApps.html#id2622828">Kerberos Configuration</a>, <a class="indexterm" href="HA.html#id2626516">For Scalability, Use SAN-Based Storage on Samba Servers</a></dt><dt>synchronize, <a class="indexterm" href="2000users.html#id2590236">User Needs</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>synchronized, <a class="indexterm" href="unixclients.html#id2603025">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#id2603025">Questions and Answers</a></dt><dt>system security, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt></dl></div><div class="indexdiv"><h3>T</h3><dl><dt>tattooing, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>TCP/IP, <a class="indexterm" href="unixclients.html#id2603025">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#id2608210">NT4 Migration Using LDAP Backend</a></dt><dt>tdbsam, <a class="indexterm" href="secure.html#id2564939">Technical Issues</a>, <a class="indexterm" href="secure.html#id2565406">Implementation</a>, <a class="indexterm" href="Big500users.html">The 500-User Office</a>, <a class="indexterm" href="happy.html#id2577346">Assignment Tasks</a>, <a class="indexterm" href="2000users.html#id2589924">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2591160">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#id2603025">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="upgrades.html#id2606638">Updating from Samba Versions between 3.0.6 and 3.0.10</a>, <a class="indexterm" href="ntmigration.html#id2607720">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>testparm, <a class="indexterm" href="small.html#id2563413">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#id2626091">Samba Configuration</a></dt><dt>ticket, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a></dt><dt>time server, <a class="indexterm" href="secure.html#id2565406">Implementation</a></dt><dt>Tivoli Directory Server, <a class="indexterm" href="happy.html#id2577483">Dissection and Discussion</a></dt><dt>TLS, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>token, <a class="indexterm" href="DomApps.html#id2622405">Technical Issues</a></dt><dt>tool, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>TOSHARG2, <a class="indexterm" href="simple.html#id2558033">Implementation</a></dt><dt>track record, <a class="indexterm" href="kerberos.html#id2617338">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#id2589924">Dissection and Discussion</a></dt><dt>transactional, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt><dt>transfer, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>translate, <a class="indexterm" href="kerberos.html#id2620740">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#id2612318">Dissection and Discussion</a></dt><dt>Tree Connect, <a class="indexterm" href="primer.html#id2633100">Simple Windows Client Connection Characteristics</a></dt><dt>trust account, <a class="indexterm" href="happy.html#id2577106">Regarding LDAP Directories and Windows Computer Accounts</a></dt><dt>trusted computing, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>Trusted Domains, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>trusted domains, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>trusted third-party, <a class="indexterm" href="kerberos.html#id2619019">Kerberos Exposed</a></dt><dt>trusting, <a class="indexterm" href="kerberos.html#id2619019">Kerberos Exposed</a></dt><dt>turn-around time, <a class="indexterm" href="kerberos.html#id2617736">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#id2625819">Routed Networks</a></dt></dl></dd><dt>UID, <a class="indexterm" href="simple.html#id2557838">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2577106">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a>, <a class="indexterm" href="2000users.html#id2591160">Implementation</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>un-join, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>unauthorized activities, <a class="indexterm" href="kerberos.html#id2619019">Kerberos Exposed</a></dt><dt>UNC name, <a class="indexterm" href="2000users.html#id2594466">Questions and Answers</a></dt><dt>unencrypted, <a class="indexterm" href="appendix.html#id2629619">The LDAP Account Manager</a></dt><dt>Unicast, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a></dt><dt>unicode, <a class="indexterm" href="upgrades.html#id2605445">International Language Support</a></dt><dt>Universal Naming Convention (see UNC name)</dt><dt>UNIX, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dd><dl><dt>groups, <a class="indexterm" href="small.html#id2561650">Technical Issues</a>, <a class="indexterm" href="small.html#id2561869">Implementation</a></dt></dl></dd><dt>UNIX accounts, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a></dt><dt>UNIX/Linux server, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>unix2dos, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2573023">Configuration for Server: MASSIVE</a></dt><dt>unknown, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>unsupported software, <a class="indexterm" href="ch14.html#id2627306">Commercial Support</a></dt><dt>update, <a class="indexterm" href="upgrades.html#id2604185">Introduction</a>, <a class="indexterm" href="upgrades.html#id2604281">Cautions and Notes</a></dt><dt>updates, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>updating smbldap-tools, <a class="indexterm" href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a></dt><dt>upgrade, <a class="indexterm" href="upgrades.html#id2604185">Introduction</a>, <a class="indexterm" href="upgrades.html#id2604281">Cautions and Notes</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>uppercase, <a class="indexterm" href="ntmigration.html#id2608069">Implementation</a></dt><dt>user</dt><dd><dl><dt>management, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2573023">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#id2617736">Technical Issues</a></dt><dt>user credentials, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a>, <a class="indexterm" href="unixclients.html#id2602396">UNIX/Linux Client Domain Member</a></dt><dt>user errors, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>user groups, <a class="indexterm" href="ch14.html#id2627087">Free Support</a></dt><dt>user identities, <a class="indexterm" href="unixclients.html#id2596190">Implementation</a></dt><dt>user logins, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>user management, <a class="indexterm" href="secure.html#id2565406">Implementation</a></dt><dt>User Manager, <a class="indexterm" href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a></dt><dt>User Mode, <a class="indexterm" href="secure.html#id2565406">Implementation</a>, <a class="indexterm" href="primer.html#id2633100">Simple Windows Client Connection Characteristics</a>, <a class="indexterm" href="primer.html#id2633603">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>useradd, <a class="indexterm" href="simple.html#id2558033">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2573023">Configuration for Server: MASSIVE</a>, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>userdel, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>usermod, <a class="indexterm" href="upgrades.html#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a></dt><dt>username, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>username map, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#id2566260">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2572445">Server Preparation: All Servers</a></dt><dt>UTF-8, <a class="indexterm" href="upgrades.html#id2605445">International Language Support</a></dt><dt>utilities, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>valid users, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2619854">Checkpoint Controls</a>, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>validate, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2619854">Checkpoint Controls</a></dt><dt>validated, <a class="indexterm" href="2000users.html#id2590677">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#id2616672">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#id2624491">Questions and Answers</a></dt><dt>vampire, <a class="indexterm" href="ntmigration.html#id2611114">Questions and Answers</a></dt><dt>vendor, <a class="indexterm" href="kerberos.html#id2617338">Dissection and Discussion</a></dt><dt>vendors, <a class="indexterm" href="upgrades.html#id2606494">Updating a Samba-3 Installation</a></dt><dt>VFS modules, <a class="indexterm" href="appendix.html#id2628013">Samba System File Location</a></dt><dt>virus, <a class="indexterm" href="secure.html#id2565406">Implementation</a></dt><dt>VPN, <a class="indexterm" href="2000users.html#id2589856">Assignment Tasks</a></dt><dt>vulnerabilities, <a class="indexterm" href="kerberos.html#id2616672">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#id2623217">Samba Configuration</a></dt><dt>weakness, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a></dt><dt>web</dt><dd><dl><dt>caching, <a class="indexterm" href="DomApps.html#id2622261">Assignment Tasks</a></dt><dt>proxying, <a class="indexterm" href="DomApps.html#id2622261">Assignment Tasks</a></dt></dl></dd><dt>Web</dt><dd><dl><dt>proxy, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dd><dl><dt>access, <a class="indexterm" href="DomApps.html#id2624430">Key Points Learned</a></dt></dl></dd></dl></dd><dt>Web browsers, <a class="indexterm" href="DomApps.html#id2624430">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#id2606312">Samba-2.x with LDAP Support</a></dt><dt>white-pages, <a class="indexterm" href="nw4migration.html#id2612395">Technical Issues</a>, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dt>wide-area, <a class="indexterm" href="2000users.html#id2590236">User Needs</a>, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2594319">Key Points Learned</a>, <a class="indexterm" href="2000users.html#id2594466">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#id2626419">Use and Location of BDCs</a>, <a class="indexterm" href="HA.html#id2626620">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></dt><dt>winbind, <a class="indexterm" href="2000users.html#id2591160">Implementation</a>, <a class="indexterm" href="unixclients.html#id2595413">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#id2603025">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2622405">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2623769">NSS Configuration</a></dt><dt>Winbind, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2617736">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2621467">Key Points Learned</a></dt><dt>winbind trusted domains only, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2603025">Questions and Answers</a></dt><dt>winbind use default domain, <a class="indexterm" href="kerberos.html#id2619854">Checkpoint Controls</a></dt><dt>winbindd, <a class="indexterm" href="small.html#id2563413">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="Big500users.html#id2571492">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2595441">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#id2603025">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#id2606717">Updating from Samba Versions after 3.0.6 to a Current Release</a>, <a class="indexterm" href="upgrades.html#id2606820">Replacing a Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2623217">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2628434">Starting Samba</a></dt><dt>winbindd_cache.tdb, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>winbindd_idmap.tdb, <a class="indexterm" href="unixclients.html#id2595441">Technical Issues</a></dt><dt>Windows, <a class="indexterm" href="nw4migration.html#id2612670">LDAP Server Configuration</a></dt><dd><dl><dt>client, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt><dt>NT, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a></dt></dl></dd><dt>Windows 2000 ACLs, <a class="indexterm" href="kerberos.html#id2620740">Managing Windows 200x ACLs</a></dt><dt>Windows 2003 Serve, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>Windows 200x ACLs, <a class="indexterm" href="kerberos.html#id2621601">Questions and Answers</a></dt><dt>Windows accounts, <a class="indexterm" href="happy.html#id2577941">Technical Issues</a></dt><dt>Windows ACLs, <a class="indexterm" href="kerberos.html#id2621257">Setting Posix ACLs in UNIX/Linux</a></dt><dt>Windows Address Book, <a class="indexterm" href="nw4migration.html#id2612670">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#id2624491">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#id2624491">Questions and Answers</a></dt><dt>Windows security identifier (see SID)</dt><dt>Windows Servers, <a class="indexterm" href="kerberos.html#id2616672">Introduction</a></dt><dt>Windows Services for UNIX (see SUS)</dt><dt>Windows XP, <a class="indexterm" href="small.html#id2561542">Assignment Tasks</a></dt><dt>WINS, <a class="indexterm" href="simple.html#id2558033">Implementation</a>, <a class="indexterm" href="small.html#id2561650">Technical Issues</a>, <a class="indexterm" href="small.html#id2561869">Implementation</a>, <a class="indexterm" href="secure.html#ch4wincfg">Windows Client Configuration</a>, <a class="indexterm" href="Big500users.html#id2571492">Technical Issues</a>, <a class="indexterm" href="Big500users.html#ch5wincfg">Windows Client Configuration</a>, <a class="indexterm" href="2000users.html#id2590330">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2594466">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#id2603025">Questions and Answers</a></dt><dt>name resolution, <a class="indexterm" href="HA.html#id2625819">Routed Networks</a></dt><dt>server, <a class="indexterm" href="happy.html">Making Happy Users</a>, <a class="indexterm" href="HA.html#id2625819">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#id2594466">Questions and Answers</a></dt><dt>WINS serving, <a class="indexterm" href="secure.html#id2565406">Implementation</a></dt><dt>wins support, <a class="indexterm" href="secure.html#id2565406">Implementation</a></dt><dt>wins.dat, <a class="indexterm" href="2000users.html#id2590677">Identity Management Needs</a>, <a class="indexterm" href="upgrades.html#id2606820">Replacing a Domain Member Server</a></dt><dt>Wireshark, <a class="indexterm" href="primer.html#id2631489">Requirements and Notes</a></dt><dt>wireshark, <a class="indexterm" href="primer.html#id2631827">Exercises</a></dt><dt>Word, <a class="indexterm" href="kerberos.html#id2620328">Share Point Directory and File Permissions</a></dt><dt>workgroup, <a class="indexterm" href="simple.html#id2557141">Implementation</a>, <a class="indexterm" href="upgrades.html#id2604385">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2605179">Change of Workgroup (Domain) Name</a></dt><dt>Workgroup Announcement, <a class="indexterm" href="primer.html#id2632740">Findings</a></dt><dt>workstation, <a class="indexterm" href="unixclients.html#id2596190">Implementation</a></dt><dt>wrapper, <a class="indexterm" href="DomApps.html#id2624491">Questions and Answers</a></dt><dt>write lock, <a class="indexterm" href="appendix.html#id2631322">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#id2589924">Dissection and Discussion</a></dt><dt>xmlsam, <a class="indexterm" href="2000users.html#id2591160">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#id2590677">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 & 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 801e9016be..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.75.2"><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" title="Chapter 11. Active Directory, Kerberos, and Security"><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#id2616672">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2617322">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2617338">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2617736">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#id2619366">Share Access Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2619714">Share Definition Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2620328">Share Point Directory and File Permissions</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2620740">Managing Windows 200x ACLs</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2621467">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2621601">Questions and Answers</a></span></dt></dl></div><p><a class="indexterm" name="id2616607"></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="id2616626"></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="id2616654"></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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2616672"></a>Introduction</h2></div></div></div><p><a class="indexterm" name="id2616678"></a><a class="indexterm" name="id2616686"></a><a class="indexterm" name="id2616694"></a><a class="indexterm" name="id2616702"></a><a class="indexterm" name="id2616710"></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="id2616734"></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 <span class="quote">“<span class="quote">an island of broken - technologies.</span>”</span> This comment was made by one of Christine's staff as they were installing a new + operate with a solution that is viewed by Christine and her group as “<span class="quote">an island of broken + technologies.</span>” 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="id2616757"></a><a class="indexterm" name="id2616765"></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="id2616780" href="#ftn.id2616780" 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="id2616791"></a><a class="indexterm" name="id2616799"></a><a class="indexterm" name="id2616807"></a><a class="indexterm" name="id2616814"></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="id2616836"></a><a class="indexterm" name="id2616847"></a><a class="indexterm" name="id2616858"></a><a class="indexterm" name="id2616866"></a><a class="indexterm" name="id2616874"></a><a class="indexterm" name="id2616882"></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="id2616898"></a><a class="indexterm" name="id2616906"></a><a class="indexterm" name="id2616914"></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="id2616931"></a><a class="indexterm" name="id2616939"></a><a class="indexterm" name="id2616946"></a><a class="indexterm" name="id2616954"></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="id2616994"></a><a class="indexterm" name="id2617002"></a><a class="indexterm" name="id2617010"></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="id2617035"></a><a class="indexterm" name="id2617042"></a><a class="indexterm" name="id2617050"></a><a class="indexterm" name="id2617058"></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="id2617082"></a><a class="indexterm" name="id2617089"></a><a class="indexterm" name="id2617097"></a><a class="indexterm" name="id2617105"></a><a class="indexterm" name="id2617113"></a><a class="indexterm" name="id2617121"></a><a class="indexterm" name="id2617129"></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="id2617144"></a><a class="indexterm" name="id2617152"></a><a class="indexterm" name="id2617160"></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="id2617175"></a><a class="indexterm" name="id2617183"></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="id2617219"></a><a class="indexterm" name="id2617227"></a><a class="indexterm" name="id2617235"></a><a class="indexterm" name="id2617243"></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="id2617261"></a><a class="indexterm" name="id2617269"></a><a class="indexterm" name="id2617277"></a><a class="indexterm" name="id2617285"></a><a class="indexterm" name="id2617293"></a><a class="indexterm" name="id2617301"></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" title="Assignment Tasks"><div class="titlepage"><div><div><h3 class="title"><a name="id2617322"></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" title="Dissection and Discussion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2617338"></a>Dissection and Discussion</h2></div></div></div><p><a class="indexterm" name="id2617345"></a><a class="indexterm" name="id2617353"></a><a class="indexterm" name="id2617361"></a><a class="indexterm" name="id2617369"></a><a class="indexterm" name="id2617377"></a><a class="indexterm" name="id2617385"></a><a class="indexterm" name="id2617392"></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="id2617414"></a><a class="indexterm" name="id2617422"></a><a class="indexterm" name="id2617430"></a><a class="indexterm" name="id2617438"></a><a class="indexterm" name="id2617446"></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="id2617466"></a><a class="indexterm" name="id2617474"></a><a class="indexterm" name="id2617482"></a><a class="indexterm" name="id2617490"></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="id2617506"></a><a class="indexterm" name="id2617514"></a><a class="indexterm" name="id2617522"></a><a class="indexterm" name="id2617530"></a><a class="indexterm" name="id2617542"></a><a class="indexterm" name="id2617550"></a><a class="indexterm" name="id2617557"></a><a class="indexterm" name="id2617565"></a><a class="indexterm" name="id2617573"></a><a class="indexterm" name="id2617581"></a><a class="indexterm" name="id2617589"></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,49 +143,49 @@ 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="id2617611"></a><a class="indexterm" name="id2617619"></a><a class="indexterm" name="id2617627"></a><a class="indexterm" name="id2617635"></a><a class="indexterm" name="id2617643"></a><a class="indexterm" name="id2617651"></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="id2617676"></a><a class="indexterm" name="id2617684"></a><a class="indexterm" name="id2617692"></a><a class="indexterm" name="id2617699"></a><a class="indexterm" name="id2617707"></a><a class="indexterm" name="id2617715"></a><a class="indexterm" name="id2617723"></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" title="Technical Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2617736"></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="id2617756"></a><a class="indexterm" name="id2617764"></a><a class="indexterm" name="id2617772"></a><a class="indexterm" name="id2617784"></a><a class="indexterm" name="id2617792"></a><a class="indexterm" name="id2617800"></a><a class="indexterm" name="id2617808"></a><a class="indexterm" name="id2617816"></a><a class="indexterm" name="id2617824"></a><a class="indexterm" name="id2617832"></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="id2617855"></a><a class="indexterm" name="id2617863"></a><a class="indexterm" name="id2617871"></a><a class="indexterm" name="id2617879"></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="id2617902"></a><a class="indexterm" name="id2617910"></a><a class="indexterm" name="id2617918"></a><a class="indexterm" name="id2617926"></a><a class="indexterm" name="id2617934"></a><a class="indexterm" name="id2617945"></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="id2617966"></a><a class="indexterm" name="id2617974"></a><a class="indexterm" name="id2617985"></a><a class="indexterm" name="id2617993"></a><a class="indexterm" name="id2618001"></a><a class="indexterm" name="id2618009"></a><a class="indexterm" name="id2618016"></a><a class="indexterm" name="id2618024"></a><a class="indexterm" name="id2618032"></a><a class="indexterm" name="id2618040"></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 controls have not been properly implemented. Samba permits access controls to be set on: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Shares themselves (i.e., the logical share itself)</p></li><li class="listitem"><p>The share definition in <code class="filename">smb.conf</code></p></li><li class="listitem"><p>The shared directories and files using UNIX permissions</p></li><li class="listitem"><p>Using Windows 2000 ACLs if the file system is POSIX enabled</p></li></ul></div><p> + </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">“Implementation”</a>. - </p></dd><dt><span class="term">User and Group Controls</span></dt><dd><p><a class="indexterm" name="id2618114"></a><a class="indexterm" name="id2618122"></a><a class="indexterm" name="id2618134"></a><a class="indexterm" name="id2618145"></a><a class="indexterm" name="id2618153"></a><a class="indexterm" name="id2618161"></a><a class="indexterm" name="id2618168"></a><a class="indexterm" name="id2618176"></a><a class="indexterm" name="id2618184"></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="id2618204"></a><a class="indexterm" name="id2618212"></a><a class="indexterm" name="id2618220"></a><a class="indexterm" name="id2618228"></a><a class="indexterm" name="id2618239"></a><a class="indexterm" name="id2618247"></a><a class="indexterm" name="id2618255"></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="id2618277"></a><a class="indexterm" name="id2618285"></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="id2618307"></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="id2618324"></a><a class="indexterm" name="id2618332"></a><a class="indexterm" name="id2618339"></a><a class="indexterm" name="id2618347"></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="id2618367"></a><a class="indexterm" name="id2618375"></a><a class="indexterm" name="id2618383"></a><a class="indexterm" name="id2618391"></a><a class="indexterm" name="id2618399"></a><a class="indexterm" name="id2618407"></a><a class="indexterm" name="id2618415"></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="id2618433"></a><a class="indexterm" name="id2618441"></a><a class="indexterm" name="id2618449"></a><a class="indexterm" name="id2618456"></a><a class="indexterm" name="id2618464"></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="id2618494"></a><a class="indexterm" name="id2618502"></a><a class="indexterm" name="id2618514"></a><a class="indexterm" name="id2618525"></a><a class="indexterm" name="id2618533"></a><a class="indexterm" name="id2618541"></a><a class="indexterm" name="id2618549"></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="id2618579"></a><a class="indexterm" name="id2618587"></a><a class="indexterm" name="id2618595"></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="id2618625"></a><a class="indexterm" name="id2618633"></a><a class="indexterm" name="id2618640"></a><a class="indexterm" name="id2618648"></a><a class="indexterm" name="id2618656"></a><a class="indexterm" name="id2618671"></a><a class="indexterm" name="id2618679"></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="id2618700"></a><a class="indexterm" name="id2618708"></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="id2618748"></a><a class="indexterm" name="id2618756"></a><a class="indexterm" name="id2618764"></a><a class="indexterm" name="id2618772"></a><a class="indexterm" name="id2618780"></a><a class="indexterm" name="id2618787"></a><a class="indexterm" name="id2618796"></a><a class="indexterm" name="id2618803"></a><a class="indexterm" name="id2618811"></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 @@ -274,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="id2618899"></a><a class="indexterm" name="id2618910"></a><a class="indexterm" name="id2618918"></a><a class="indexterm" name="id2618926"></a><a class="indexterm" name="id2618934"></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 @@ -282,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="id2618965"></a><a class="indexterm" name="id2618973"></a><a class="indexterm" name="id2618981"></a><a class="indexterm" name="id2618992"></a><a class="indexterm" name="id2619000"></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" title="Kerberos Exposed"><div class="titlepage"><div><div><h4 class="title"><a name="id2619019"></a>Kerberos Exposed</h4></div></div></div><p><a class="indexterm" name="id2619026"></a><a class="indexterm" name="id2619034"></a><a class="indexterm" name="id2619042"></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="id2619060"></a><a class="indexterm" name="id2619068"></a><a class="indexterm" name="id2619076"></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="id2619094"></a><a class="indexterm" name="id2619102"></a><a class="indexterm" name="id2619110"></a><a class="indexterm" name="id2619118"></a><a class="indexterm" name="id2619129"></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="id2619149"></a> - <a class="indexterm" name="id2619156"></a> - <a class="indexterm" name="id2619163"></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 @@ -319,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="id2619193"></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="id2619212" href="#ftn.id2619212" 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 @@ -331,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="id2619238"></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 @@ -339,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="id2619261"></a> - <a class="indexterm" name="id2619267"></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 @@ -352,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="id2619303"></a><a class="indexterm" name="id2619314"></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. @@ -360,52 +360,52 @@ Windows NT services will not be able to translate DCE PACs into Windows NT user and group identifiers. This is not an issue with Kerberos interoperability, but rather an issue of interoperability between DCE and Windows NT access control information. - </p></blockquote></div></div></div></div><div class="sect1" title="Implementation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ch10expl"></a>Implementation</h2></div></div></div><p> + </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" title="Share Access Controls"><div class="titlepage"><div><div><h3 class="title"><a name="id2619366"></a>Share Access Controls</h3></div></div></div><p><a class="indexterm" name="id2619373"></a><a class="indexterm" name="id2619380"></a><a class="indexterm" name="id2619388"></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" title="Procedure 11.1. Create/Edit/Delete Share ACLs"><a name="id2619402"></a><p class="title"><b>Procedure 11.1. Create/Edit/Delete Share ACLs</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p><a class="indexterm" name="id2619412"></a><a class="indexterm" name="id2619420"></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 class="step" title="Step 2"><p> + </p></li><li><p> Click <span class="guimenu">Start</span> → <span class="guimenuitem">Settings</span> → <span class="guimenuitem">Control Panel</span> → <span class="guimenuitem">Administrative Tools</span> → <span class="guimenuitem">Computer Management</span>. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> In the left panel, <span class="guimenu">[Right mouse menu item] Computer Management (Local)</span> → <span class="guimenuitem">Connect to another computer ...</span> → <span class="guimenuitem">Browse...</span> → <span class="guimenuitem">Advanced</span> → <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> → <span class="guimenuitem">OK</span> → <span class="guimenuitem">OK</span>.<a class="indexterm" name="id2619543"></a> + administer. Click <span class="guimenu">OK</span> → <span class="guimenuitem">OK</span> → <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 class="step" title="Step 4"><p> + </p></li><li><p> In the left panel, click <span class="guimenu">Computer Management (FRODO)</span> → <span class="guimenuitem">[+] Shared Folders</span> → <span class="guimenuitem">Shares</span>. - </p></li><li class="step" title="Step 5"><p><a class="indexterm" name="id2619607"></a><a class="indexterm" name="id2619615"></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 class="step" title="Step 6"><p><a class="indexterm" name="id2619638"></a><a class="indexterm" name="id2619646"></a><a class="indexterm" name="id2619654"></a><a class="indexterm" name="id2619662"></a><a class="indexterm" name="id2619670"></a><a class="indexterm" name="id2619678"></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 belong to the group <code class="constant">Everyone</code>, which therefore overrules any permissions set for the permitted group. - </p></li><li class="step" title="Step 7"><p> + </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" title="Share Definition Controls"><div class="titlepage"><div><div><h3 class="title"><a name="id2619714"></a>Share Definition Controls</h3></div></div></div><p><a class="indexterm" name="id2619721"></a><a class="indexterm" name="id2619733"></a><a class="indexterm" name="id2619741"></a><a class="indexterm" name="id2619748"></a><a class="indexterm" name="id2619756"></a><a class="indexterm" name="id2619764"></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="id2619785"></a><a class="indexterm" name="id2619793"></a><a class="indexterm" name="id2619800"></a><a class="indexterm" name="id2619809"></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 class="orderedlist" type="1"><li class="listitem"><p>Share-level ACLs</p></li><li class="listitem"><p>Share-definition controls</p></li><li class="listitem"><p>Directory and file permissions</p></li><li class="listitem"><p>Directory and file POSIX ACLs</p></li></ol></div><div class="sect3" title="Checkpoint Controls"><div class="titlepage"><div><div><h4 class="title"><a name="id2619854"></a>Checkpoint Controls</h4></div></div></div><p><a class="indexterm" name="id2619861"></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] @@ -416,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" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p><a class="indexterm" name="id2619896"></a><a class="indexterm" name="id2619908"></a><a class="indexterm" name="id2619916"></a><a class="indexterm" name="id2619924"></a><a class="indexterm" name="id2619932"></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="id2619967"></a><a class="indexterm" name="id2619974"></a><a class="indexterm" name="id2619982"></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="id2620013"></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, @@ -441,7 +441,7 @@ read only = Yes invalid users = patrickj </pre><p> - <a class="indexterm" name="id2620054"></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: @@ -453,7 +453,7 @@ invalid users = patrickj admin users = gbshaw </pre><p> - <a class="indexterm" name="id2620085"></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. @@ -475,11 +475,11 @@ admin users = gbshaw write list = peters </pre><p> - <a class="indexterm" name="id2620145"></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" title="Override Controls"><div class="titlepage"><div><div><h4 class="title"><a name="id2620166"></a>Override Controls</h4></div></div></div><p><a class="indexterm" name="id2620173"></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 @@ -497,14 +497,14 @@ force user = billc force group = Mentors </pre><p> - <a class="indexterm" name="id2620217"></a><a class="indexterm" name="id2620225"></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="id2620245"></a><a class="indexterm" name="id2620253"></a><a class="indexterm" name="id2620261"></a><a class="indexterm" name="id2620272"></a><a class="indexterm" name="id2620280"></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 @@ -514,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" title="Share Point Directory and File Permissions"><div class="titlepage"><div><div><h3 class="title"><a name="id2620328"></a>Share Point Directory and File Permissions</h3></div></div></div><p><a class="indexterm" name="id2620335"></a><a class="indexterm" name="id2620343"></a><a class="indexterm" name="id2620351"></a><a class="indexterm" name="id2620358"></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 @@ -522,29 +522,29 @@ 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="id2620381"></a><a class="indexterm" name="id2620389"></a><a class="indexterm" name="id2620397"></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 class="orderedlist" type="1"><li class="listitem"><p> + </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 class="listitem"><p> + </p></li><li><p> File changes and edits are made. - </p></li><li class="listitem"><p> + </p></li><li><p> The file is saved, and MS Word is closed. - </p></li><li class="listitem"><p> + </p></li><li><p> The file is now owned by the user <code class="constant">billc</code> and group <code class="constant">doctors</code>, and is set read/write by <code class="constant">billc</code>, read-only by <code class="constant">doctors</code>, and no access by everyone. - </p></li><li class="listitem"><p> - The original owner cannot now access her own file and is <span class="quote">“<span class="quote">justifiably</span>”</span> upset. + </p></li><li><p> + The original owner cannot now access her own file and is “<span class="quote">justifiably</span>” upset. </p></li></ol></div><p> There have been many postings over the years that report the same basic problem. Frequently Samba users - want to know when this <span class="quote">“<span class="quote">bug</span>”</span> will be fixed. The fact is, this is not a bug in Samba at all. + want to know when this “<span class="quote">bug</span>” 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="id2620498"></a><a class="indexterm" name="id2620506"></a><a class="indexterm" name="id2620514"></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 @@ -557,12 +557,12 @@ perhaps have the same ownership and permissions as the old file. To Samba, these are entirely independent operations. </p><p> - The question is, <span class="quote">“<span class="quote">How can we solve the problem?</span>”</span> + The question is, “<span class="quote">How can we solve the problem?</span>” </p><p> 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" title="Procedure 11.2. Using Directory Permissions to Force File User and Group Ownership"><a name="id2620561"></a><p class="title"><b>Procedure 11.2. Using Directory Permissions to Force File User and Group Ownership</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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] @@ -570,18 +570,18 @@ browseable = Yes read only = No </pre><p> - </p></li><li class="step" title="Step 2"><p><a class="indexterm" name="id2620587"></a><a class="indexterm" name="id2620598"></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 class="step" title="Step 3"><p><a class="indexterm" name="id2620630"></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 class="step" title="Step 4"><p><a class="indexterm" name="id2620659"></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 @@ -591,11 +591,11 @@ <code class="prompt">root# </code> find /usr/data/finance -type d -exec chmod ug+s {}\; </pre><p> - </p></li><li class="step" title="Step 5"><p><a class="indexterm" name="id2620699"></a><a class="indexterm" name="id2620707"></a><a class="indexterm" name="id2620715"></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" title="Managing Windows 200x ACLs"><div class="titlepage"><div><div><h3 class="title"><a name="id2620740"></a>Managing Windows 200x ACLs</h3></div></div></div><p><a class="indexterm" name="id2620747"></a><a class="indexterm" name="id2620755"></a><a class="indexterm" name="id2620763"></a><a class="indexterm" name="id2620771"></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 @@ -603,62 +603,62 @@ </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" title="Using the MMC Computer Management Interface"><div class="titlepage"><div><div><h4 class="title"><a name="id2620795"></a>Using the MMC Computer Management Interface</h4></div></div></div><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><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 class="step" title="Step 2"><p> + </p></li><li><p> Click <span class="guimenu">Start</span> → <span class="guimenuitem">Settings</span> → <span class="guimenuitem">Control Panel</span> → <span class="guimenuitem">Administrative Tools</span> → <span class="guimenuitem">Computer Management</span>. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> In the left panel, <span class="guimenu">[Right mouse menu item] Computer Management (Local)</span> → <span class="guimenuitem">Connect to another computer ...</span> → <span class="guimenuitem">Browse...</span> → <span class="guimenuitem">Advanced</span> → <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> → <span class="guimenuitem">OK</span> → <span class="guimenuitem">OK</span>. 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 class="step" title="Step 4"><p> + </p></li><li><p> In the left panel, click <span class="guimenu">Computer Management (FRODO)</span> → <span class="guimenuitem">[+] Shared Folders</span> → <span class="guimenuitem">Shares</span>. - </p></li><li class="step" title="Step 5"><p><a class="indexterm" name="id2620978"></a><a class="indexterm" name="id2620986"></a><a class="indexterm" name="id2620993"></a><a class="indexterm" name="id2621001"></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 class="step" title="Step 6"><p><a class="indexterm" name="id2621041"></a><a class="indexterm" name="id2621049"></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 belong to the group <code class="constant">Everyone</code>, which therefore overrules any permissions set for the permitted group. - </p></li><li class="step" title="Step 7"><p> + </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" title="Using MS Windows Explorer (File Manager)"><div class="titlepage"><div><div><h4 class="title"><a name="id2621086"></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 <code class="filename">/data/apps</code>. - </p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p> + </p><div class="procedure"><ol type="1"><li><p> Click <span class="guimenu">Start</span> → <span class="guimenuitem">[right-click] My Computer</span> → <span class="guimenuitem">Explore</span> → <span class="guimenuitem">[left panel] [+] My Network Places</span> → <span class="guimenuitem">[+] Entire Network</span> → <span class="guimenuitem">[+] Microsoft Windows Network</span> → <span class="guimenuitem">[+] Meganet</span> → <span class="guimenuitem">[+] Massive</span> → <span class="guimenuitem">[right-click] Apps</span> → <span class="guimenuitem">Properties</span> → <span class="guimenuitem">Security</span> → <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 class="step" title="Step 2"><p><a class="indexterm" name="id2621210"></a><a class="indexterm" name="id2621218"></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 belong to the group <code class="constant">Everyone</code>, which therefore overrules any permissions set for the permitted group. - </p></li><li class="step" title="Step 3"><p> + </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" title="Setting Posix ACLs in UNIX/Linux"><div class="titlepage"><div><div><h4 class="title"><a name="id2621257"></a>Setting Posix ACLs in UNIX/Linux</h4></div></div></div><p><a class="indexterm" name="id2621264"></a><a class="indexterm" name="id2621272"></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 Linux system: - </p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p> + </p><div class="procedure"><ol type="1"><li><p> Log into the Linux system as the user <code class="constant">root</code>. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Change directory to the location of the exported (shared) Windows file share (Apps), which is in the directory <code class="filename">/data</code>. Execute the following: </p><pre class="screen"> @@ -674,7 +674,7 @@ user::rwx group::rwx other::r-x </pre><p> - </p></li><li class="step" title="Step 3"><p><a class="indexterm" name="id2621346"></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 @@ -697,111 +697,111 @@ mask::rwx other::r-x </pre><p> This confirms that the change of POSIX ACL permissions has been effective. - </p></li><li class="step" title="Step 4"><p><a class="indexterm" name="id2621402"></a><a class="indexterm" name="id2621409"></a><a class="indexterm" name="id2621417"></a><a class="indexterm" name="id2621425"></a><a class="indexterm" name="id2621433"></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" title="Key Points Learned"><div class="titlepage"><div><div><h3 class="title"><a name="id2621467"></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 class="itemizedlist" type="disc"><li class="listitem"><p><a class="indexterm" name="id2621484"></a><a class="indexterm" name="id2621492"></a><a class="indexterm" name="id2621500"></a><a class="indexterm" name="id2621508"></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 class="listitem"><p><a class="indexterm" name="id2621527"></a><a class="indexterm" name="id2621535"></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 class="listitem"><p><a class="indexterm" name="id2621551"></a><a class="indexterm" name="id2621559"></a><a class="indexterm" name="id2621566"></a><a class="indexterm" name="id2621574"></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 UNIX/Linux systems may be fully integrated into Active Directory domains. - </p></li><li class="listitem"><p> + </p></li><li><p> 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" title="Questions and Answers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2621601"></a>Questions and Answers</h2></div></div></div><p> - </p><div class="qandaset" title="Frequently Asked Questions"><a name="id2621610"></a><dl><dt> <a href="kerberos.html#id2621617"> + </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#id2621687"> + </a></dt><dt> <a href="kerberos.html#id2615602"> Does Samba-3 support Active Directory? - </a></dt><dt> <a href="kerberos.html#id2621718"> + </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#id2621757"> + </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#id2621786"> + </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#id2621863"> + </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#id2621929"> + </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#id2621992"> + </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#id2622040"> + </a></dt><dt> <a href="kerberos.html#id2615955"> In the book, “The Official Samba-3 HOWTO and Reference Guide”, 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#id2622107"> + </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" width="100%" summary="Q and A Set"><col align="left" width="1%"><col><tbody><tr class="question"><td align="left" valign="top"><a name="id2621617"></a><a name="id2621619"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2621622"></a><a class="indexterm" name="id2621630"></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="id2621650"></a><a class="indexterm" name="id2621657"></a><a class="indexterm" name="id2621665"></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="id2621687"></a><a name="id2621690"></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="id2621700"></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="id2621718"></a><a name="id2621721"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2621724"></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="id2621740"></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="id2621757"></a><a name="id2621759"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2621762"></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="id2621786"></a><a name="id2621788"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2621792"></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="id2621807"></a><a class="indexterm" name="id2621815"></a><a class="indexterm" name="id2621823"></a><a class="indexterm" name="id2621832"></a><a class="indexterm" name="id2621840"></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="id2621863"></a><a name="id2621865"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2621868"></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="id2621896"></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="id2621929"></a><a name="id2621931"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2621934"></a><a class="indexterm" name="id2621942"></a><a class="indexterm" name="id2621950"></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="id2621977"></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="id2621992"></a><a name="id2621994"></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="id2622007"></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"> @@ -809,20 +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="id2622040"></a><a name="id2622042"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2622046"></a> - In the book, <span class="quote">“<span class="quote">The Official Samba-3 HOWTO and Reference Guide</span>”</span>, you recommended use + </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, “<span class="quote">The Official Samba-3 HOWTO and Reference Guide</span>”, 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="id2622074"></a><a class="indexterm" name="id2622081"></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="id2622107"></a><a name="id2622109"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2622112"></a><a class="indexterm" name="id2622120"></a><a class="indexterm" name="id2622128"></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"></div><div class="footnote"><a class="ulink" href="http://199.105.191.226/Man/2699/020430msdoj/" target="_top"><sup>[<a name="ftn.id2619212" href="#id2619212" 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> + </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 f23c3b0aea..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.75.2"><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" title="Chapter 9. Migrating NT4 Domain to Samba-3"><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#id2607394">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2607479">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2607534">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2607720">Technical Issues</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2608043">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2608069">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2608210">NT4 Migration Using LDAP Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2610669">NT4 Migration Using tdbsam Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2611075">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2611114">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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2607394"></a>Introduction</h2></div></div></div><p><a class="indexterm" name="id2607401"></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="id2607419"></a> - <a class="indexterm" name="id2607426"></a> - <a class="indexterm" name="id2607435"></a> - <a class="indexterm" name="id2607444"></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="id2607461"></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" title="Assignment Tasks"><div class="titlepage"><div><div><h3 class="title"><a name="id2607479"></a>Assignment Tasks</h3></div></div></div><p> - <a class="indexterm" name="id2607487"></a> - <a class="indexterm" name="id2607494"></a> - <a class="indexterm" name="id2607501"></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" title="Dissection and Discussion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2607534"></a>Dissection and Discussion</h2></div></div></div><p> - <a class="indexterm" name="id2607542"></a> - <a class="indexterm" name="id2607548"></a> - <a class="indexterm" name="id2607555"></a> - <a class="indexterm" name="id2607567"></a> - <a class="indexterm" name="id2607578"></a> - <a class="indexterm" name="id2607585"></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="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" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> - <a class="indexterm" name="id2607609"></a> - <a class="indexterm" name="id2607616"></a> + </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> + <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="id2607638"></a> - <a class="indexterm" name="id2607647"></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="id2607666"></a> - <a class="indexterm" name="id2607675"></a> - <a class="indexterm" name="id2607682"></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" title="Technical Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2607720"></a>Technical Issues</h3></div></div></div><p> - <a class="indexterm" name="id2607728"></a> - <a class="indexterm" name="id2607735"></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">“Schematic Explaining the net rpc vampire Process”</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="id2607808"></a> - <a class="indexterm" name="id2607815"></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="id2607835"></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="id2607850"></a><a class="indexterm" name="id2607858"></a><a class="indexterm" name="id2607866"></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="id2607884"></a> - <a class="indexterm" name="id2607890"></a> - <a class="indexterm" name="id2607897"></a> - <a class="indexterm" name="id2607904"></a> - <a class="indexterm" name="id2607911"></a> - <a class="indexterm" name="id2607918"></a> - <a class="indexterm" name="id2607925"></a> - <a class="indexterm" name="id2607932"></a> - <a class="indexterm" name="id2607938"></a> - <a class="indexterm" name="id2607945"></a> - <a class="indexterm" name="id2607952"></a> - <a class="indexterm" name="id2607959"></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" title="Political Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2608043"></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" title="Implementation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2608069"></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 @@ -160,28 +160,28 @@ (machine names, computer names, domain names, workgroup names ALL names!). </p><p> The migration process involves the following steps: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> Prepare the target Samba-3 server. This involves configuring Samba-3 for migration to either a tdbsam or an ldapsam backend. - </p></li><li class="listitem"><p> - <a class="indexterm" name="id2608156"></a> - <a class="indexterm" name="id2608163"></a> - <a class="indexterm" name="id2608169"></a> + </p></li><li><p> + <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 the target UNIX host insists on POSIX-compliant all lowercase user and group names. - </p></li><li class="listitem"><p> + </p></li><li><p> Step through the migration process. - </p></li><li class="listitem"><p><a class="indexterm" name="id2608190"></a> + </p></li><li><p><a class="indexterm" name="id2602105"></a> Remove the NT4 PDC from the network. - </p></li><li class="listitem"><p> + </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" title="NT4 Migration Using LDAP Backend"><div class="titlepage"><div><div><h3 class="title"><a name="id2608210"></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">“View of Accounts in NT4 Domain User Manager”</a>. In this example use is made of the smbldap-tools scripts to add the accounts that are migrated into the ldapsam passdb backend. @@ -194,28 +194,28 @@ that should be passed to them before attempting to perform the account migration. Note also that the deletion scripts must be commented out during migration. These should be uncommented following successful migration of the NT4 Domain accounts. - </p><div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> + </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> Under absolutely no circumstances should the Samba daemons be started until instructed to do so. 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" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - <a class="indexterm" name="id2608413"></a> - <a class="indexterm" name="id2608420"></a> - <a class="indexterm" name="id2608426"></a> + </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="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 to locate a utility called <code class="literal">groupmem</code> (by George Kraft) that provides this functionality. 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" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - <a class="indexterm" name="id2608463"></a> + </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + <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="id2608484"></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" title="Procedure 9.1. User Migration Steps"><a name="id2608494"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2608554"></a><em class="parameter"><code>workgroup = DAMNATION</code></em></td></tr><tr><td><a class="indexterm" name="id2608565"></a><em class="parameter"><code>netbios name = MERLIN</code></em></td></tr><tr><td><a class="indexterm" name="id2608577"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://localhost</code></em></td></tr><tr><td><a class="indexterm" name="id2608589"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2608601"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2608612"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2608624"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2608636"></a><em class="parameter"><code>smb ports = 139 445</code></em></td></tr><tr><td><a class="indexterm" name="id2608648"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2608660"></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="id2608672"></a><em class="parameter"><code>#delete user script = /opt/IDEALX/sbin/smbldap-userdel '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2608685"></a><em class="parameter"><code>add group script = /opt/IDEALX/sbin/smbldap-groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2608697"></a><em class="parameter"><code>#delete group script = /opt/IDEALX/sbin/smbldap-groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2608710"></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="id2608722"></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="id2608736"></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="id2608748"></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="id2608761"></a><em class="parameter"><code>logon script = scripts\logon.cmd</code></em></td></tr><tr><td><a class="indexterm" name="id2608773"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2608785"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2608796"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2608808"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2608820"></a><em class="parameter"><code>domain master = No</code></em></td></tr><tr><td><a class="indexterm" name="id2608832"></a><em class="parameter"><code>#wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2608843"></a><em class="parameter"><code>wins server = 192.168.123.124</code></em></td></tr><tr><td><a class="indexterm" name="id2608855"></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="id2608867"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2608879"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2608891"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2608903"></a><em class="parameter"><code>ldap passwd sync = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2608915"></a><em class="parameter"><code>ldap suffix = dc=terpstra-world,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2608927"></a><em class="parameter"><code>ldap ssl = no</code></em></td></tr><tr><td><a class="indexterm" name="id2608939"></a><em class="parameter"><code>ldap timeout = 20</code></em></td></tr><tr><td><a class="indexterm" name="id2608951"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2608963"></a><em class="parameter"><code>idmap backend = ldap:ldap://localhost</code></em></td></tr><tr><td><a class="indexterm" name="id2608975"></a><em class="parameter"><code>idmap uid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2608986"></a><em class="parameter"><code>idmap gid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2608998"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2609010"></a><em class="parameter"><code>ea support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2609022"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2609067"></a><em class="parameter"><code>comment = Application Data</code></em></td></tr><tr><td><a class="indexterm" name="id2609079"></a><em class="parameter"><code>path = /data/home/apps</code></em></td></tr><tr><td><a class="indexterm" name="id2609091"></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="id2609111"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2609123"></a><em class="parameter"><code>path = /home/users/%U/Documents</code></em></td></tr><tr><td><a class="indexterm" name="id2609135"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2609146"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2609158"></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="id2609178"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2609190"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2609202"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2609214"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2609225"></a><em class="parameter"><code>use client driver = No</code></em></td></tr><tr><td><a class="indexterm" name="id2609237"></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="id2609258"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2609269"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2609281"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2609293"></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="id2609313"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2609325"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2609337"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2609349"></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="id2609369"></a><em class="parameter"><code>comment = Profile Data Share</code></em></td></tr><tr><td><a class="indexterm" name="id2609381"></a><em class="parameter"><code>path = /var/lib/samba/profdata</code></em></td></tr><tr><td><a class="indexterm" name="id2609393"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2609405"></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="id2609425"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2609437"></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 @@ -330,24 +330,24 @@ automount: files nis aliases: files #passwd_compat: ldap #Not needed. #group_compat: ldap #Not needed. -</pre></div></div><br class="example-break"><ol class="procedure" type="1"><li class="step" title="Step 1"><p> +</pre></div></div><br class="example-break"><ol type="1"><li><p> Configure the Samba <code class="filename">smb.conf</code> file to create a BDC. An example configuration is given in <a class="link" href="ntmigration.html#sbent4smb" title="Example 9.1. NT4 Migration Samba-3 Server smb.conf Part: A">“NT4 Migration Samba-3 Server smb.conf Part: A”</a>. The delete scripts are commented out so that during the process of migration no account information can be deleted. - </p></li><li class="step" title="Step 2"><p> - <a class="indexterm" name="id2609455"></a> + </p></li><li><p> + <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">“NT4 Migration LDAP Server Configuration File: /etc/openldap/slapd.conf Part A”</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 class="step" title="Step 3"><p> - <a class="indexterm" name="id2609569"></a> - <a class="indexterm" name="id2609576"></a> + </p></li><li><p> + <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">“NT4 Migration NSS LDAP File: /etc/ldap.conf”</a>. - </p></li><li class="step" title="Step 4"><p> - <a class="indexterm" name="id2609637"></a> + </p></li><li><p> + <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)">“NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:1)”</a>. Note that the LDAP entries have been commented out. This is deliberate. If these entries are active (not commented out), and the @@ -357,7 +357,7 @@ aliases: files open and therefore cannot gain exclusive control of it. By commenting these entries out, it is possible to avoid this gridlock situation and thus the overall installation and configuration will progress more smoothly. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> Validate the the target NT4 PDC name is being correctly resolved to its IP address by executing the following: </p><pre class="screen"> @@ -373,7 +373,7 @@ rtt min/avg/max/mdev = 0.141/0.164/0.192/0.021 ms </pre><p> Do not proceed to the next step if this step fails. It is imperative that the name of the PDC can be resolved to its IP address. If this is broken, fix it. - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> Pull the domain SID from the NT4 domain that is being migrated as follows: </p><pre class="screen"> <code class="prompt">root# </code> net rpc getsid -S TRANGRESSION -U Administrator%not24get @@ -391,11 +391,11 @@ Storing SID S-1-5-21-1385457007-882775198-1210191635 \ </p><pre class="screen"> <code class="prompt">root# </code> net setlocalsid S-1-5-21-1385457007-882775198-1210191635 </pre><p> - </p></li><li class="step" title="Step 7"><p> - <a class="indexterm" name="id2609806"></a> - <a class="indexterm" name="id2609813"></a> - <a class="indexterm" name="id2609820"></a> - <a class="indexterm" name="id2609827"></a> + </p></li><li><p> + <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">“Install and Configure Idealx smbldap-tools Scripts”</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="id2609976"></a> - <a class="indexterm" name="id2609983"></a> - <a class="indexterm" name="id2609990"></a> - <a class="indexterm" name="id2609997"></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 @@ -501,16 +501,16 @@ writing new configuration file: was stored in the sambaUnixIdPooldn DIT location cn=NextFreeUnixId. Where smbldap-tools are being upgraded to version 0.9.1 it is appropriate to update this to the new location only if the directory information is also relocated. - </p></li><li class="step" title="Step 8"><p> + </p></li><li><p> Start the LDAP server using the system interface script. On Novell SLES9 this is done as shown here: </p><pre class="screen"> <code class="prompt">root# </code> rcldap start </pre><p> - </p></li><li class="step" title="Step 9"><p> + </p></li><li><p> Edit the <code class="filename">/etc/nsswitch.conf</code> file so it has the entries shown in <a class="link" href="ntmigration.html#sbentnss2" title="Example 9.7. NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:2)">“NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:2)”</a>. Note that the LDAP entries have now been uncommented. - </p></li><li class="step" title="Step 10"><p> + </p></li><li><p> The LDAP management password must be installed into the <code class="filename">secrets.tdb</code> file as follows: </p><pre class="screen"> @@ -518,7 +518,7 @@ writing new configuration file: Setting stored password for "cn=Manager,dc=terpstra-world,dc=org" in secrets.tdb </pre><p> - </p></li><li class="step" title="Step 11"><p> + </p></li><li><p> Populate the LDAP directory as shown here: </p><pre class="screen"> <code class="prompt">root# </code> /opt/IDEALX/sbin/smbldap-populate -a root -k 0 -m 0 @@ -544,8 +544,8 @@ adding new entry: cn=Replicators,ou=Groups,dc=terpstra-world,dc=org </pre><p> The script tries to add the ou=People container twice, hence the error message. This is expected behavior. - </p></li><li class="step" title="Step 12"><p> - <a class="indexterm" name="id2610162"></a> + </p></li><li><p> + <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: @@ -553,7 +553,7 @@ adding new entry: cn=Replicators,ou=Groups,dc=terpstra-world,dc=org <code class="prompt">root# </code> rcldap restart <code class="prompt">root# </code> chkconfig ldap on </pre><p> - </p></li><li class="step" title="Step 13"><p> + </p></li><li><p> Verify that the new user accounts that have been added to the LDAP directory can be resolved as follows: </p><pre class="screen"> @@ -584,8 +584,8 @@ Print Operators:x:550: Backup Operators:x:551: Replicators:x:552: </pre><p> - In both cases the LDAP accounts follow the <span class="quote">“<span class="quote">+::0:</span>”</span> entry. - </p></li><li class="step" title="Step 14"><p> + In both cases the LDAP accounts follow the “<span class="quote">+::0:</span>” entry. + </p></li><li><p> Now it is time to join the Samba BDC to the target NT4 domain that is being migrated to Samba-3 by executing the following: </p><pre class="screen"> @@ -594,7 +594,7 @@ merlin:/opt/IDEALX/sbin # net rpc join -S TRANSGRESSION \ -U Administrator%not24get Joined domain DAMNATION. </pre><p> - </p></li><li class="step" title="Step 15"><p> + </p></li><li><p> Set the new domain administrator (root) password for both UNIX and Windows as shown here: </p><pre class="screen"> <code class="prompt">root# </code> /opt/IDEALX/sbin/smbldap-passwd root @@ -604,7 +604,7 @@ Retype new password : ******** </pre><p> Note: During account migration, the Windows Administrator account will not be migrated to the Samba server. - </p></li><li class="step" title="Step 16"><p> + </p></li><li><p> Now validate that these accounts can be resolved using Samba's tools as shown here for user accounts: </p><pre class="screen"> @@ -632,7 +632,7 @@ Backup Operators (S-1-5-32-551) -> Backup Operators Replicators (S-1-5-32-552) -> Replicators </pre><p> These are the expected results for a correctly configured system. - </p></li><li class="step" title="Step 17"><p> + </p></li><li><p> Commence migration as shown here: </p><pre class="screen"> <code class="prompt">root# </code> net rpc vampire -S TRANSGRESSION \ @@ -640,7 +640,7 @@ Replicators (S-1-5-32-552) -> Replicators </pre><p> Check the vampire log to confirm that only expected errors have been reported. See <a class="link" href="ntmigration.html#sbevam1" title="Migration Log Validation">“Migration Log Validation”</a>. - </p></li><li class="step" title="Step 18"><p> + </p></li><li><p> The migration of user accounts can be quickly validated as follows: </p><pre class="screen"> <code class="prompt">root# </code> pdbedit -Lw @@ -675,7 +675,7 @@ LAPDOG$:25:14AA535885120943AAD3B435B51404EE:... SCAVENGER$:26:B6288EB6D147B56F8963805A19B0ED49:... merlin$:27:820C50523F368C54AB9D85AE603AD09D:... </pre><p> - </p></li><li class="step" title="Step 19"><p> + </p></li><li><p> The mapping of UNIX and Windows groups can be validated as show here: </p><pre class="screen"> <code class="prompt">root# </code> net groupmap list @@ -707,13 +707,13 @@ Users (S-1-5-32-545) -> Users </pre><p> It is of vital importance that the domain SID portions of all group accounts are identical. - </p></li><li class="step" title="Step 20"><p> + </p></li><li><p> The final responsibility in the migration process is to create identical 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 class="step" title="Step 21"><p> - <a class="indexterm" name="id2610476"></a> - <a class="indexterm" name="id2610483"></a> + </p></li><li><p> + <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. @@ -736,18 +736,18 @@ Loaded services file OK. Server role: ROLE_DOMAIN_PDC Press enter to see a dump of your service definitions </pre><p> - </p></li><li class="step" title="Step 22"><p> + </p></li><li><p> Now shut down the old NT4 PDC. Only when the old NT4 PDC and all NT4 BDCs have been shut down can the Samba-3 PDC be started. - </p></li><li class="step" title="Step 23"><p> + </p></li><li><p> All workstations should function as they did with the old NT4 PDC. All interdomain trust accounts should remain in place and fully functional. All machine accounts and user logon accounts should also function correctly. - </p></li><li class="step" title="Step 24"><p> + </p></li><li><p> The configuration of Samba-3 BDC servers can be accomplished now or at any convenient time in the future. Please refer to the carefully detailed process for doing so is outlined in <a class="link" href="happy.html#sbehap-bldg1" title="Samba-3 BDC Configuration">“Samba-3 BDC Configuration”</a>. - </p></li></ol></div><div class="sect3" title="Migration Log Validation"><div class="titlepage"><div><div><h4 class="title"><a name="sbevam1"></a>Migration Log Validation</h4></div></div></div><p> + </p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="sbevam1"></a>Migration Log Validation</h4></div></div></div><p> The following <code class="filename">vampire.log</code> file is typical of a valid migration. </p><pre class="screen"> adding user Administrator to group Domain Admins @@ -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" title="NT4 Migration Using tdbsam Backend"><div class="titlepage"><div><div><h3 class="title"><a name="id2610669"></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" title="Procedure 9.2. Migration Steps Using tdbsam"><a name="id2610716"></a><p class="title"><b>Procedure 9.2. Migration Steps Using tdbsam</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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">“The 500-User Office”</a>. Set the workgroup name to <code class="constant">MEGANET</code>. - </p></li><li class="step" title="Step 2"><p><a class="indexterm" name="id2610744"></a><a class="indexterm" name="id2610752"></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 class="step" title="Step 3"><p> + </p></li><li><p> Start Samba as you have done previously. - </p></li><li class="step" title="Step 4"><p><a class="indexterm" name="id2610794"></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 class="step" title="Step 5"><p><a class="indexterm" name="id2610829"></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 class="step" title="Step 6"><p><a class="indexterm" name="id2610883"></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 class="step" title="Step 7"><p><a class="indexterm" name="id2610960"></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 class="step" title="Step 8"><p><a class="indexterm" name="id2610995"></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,68 +979,68 @@ Administrators Members can fully administer the computer/domain Users Ordinary users </pre><p> Everything looks well and in order. - </p></li><li class="step" title="Step 9"><p><a class="indexterm" name="id2611035"></a><a class="indexterm" name="id2611043"></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" title="Key Points Learned"><div class="titlepage"><div><div><h3 class="title"><a name="id2611075"></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 class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> An LDAP backend is a suitable vehicle for NT4 migrations. - </p></li><li class="listitem"><p> + </p></li><li><p> A tdbsam backend can be used to perform a migration. - </p></li><li class="listitem"><p> + </p></li><li><p> Multiple NT4 domains can be merged into a single Samba-3 domain. - </p></li><li class="listitem"><p> + </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" title="Questions and Answers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2611114"></a>Questions and Answers</h2></div></div></div><p> - </p><div class="qandaset" title="Frequently Asked Questions"><a name="id2611123"></a><dl><dt> <a href="ntmigration.html#id2611129"> + </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#id2611169"> + </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#id2611226"> + </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#id2611406"> + </a></dt><dt> <a href="ntmigration.html#id2605321"> Why did you validate connectivity before attempting migration? - </a></dt><dt> <a href="ntmigration.html#id2611452"> + </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#id2611574"> + </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#id2611650"> + </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#id2611715"> + </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#id2611749"> + </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#id2611854"> + </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" width="100%" summary="Q and A Set"><col align="left" width="1%"><col><tbody><tr class="question"><td align="left" valign="top"><a name="id2611129"></a><a name="id2611131"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2611134"></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="id2611150"></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="id2611169"></a><a name="id2611172"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2611175"></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="id2611190"></a><a class="indexterm" name="id2611198"></a><a class="indexterm" name="id2611206"></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="id2611226"></a><a name="id2611229"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2611232"></a><a class="indexterm" name="id2611239"></a><a class="indexterm" name="id2611247"></a><a class="indexterm" name="id2611255"></a><a class="indexterm" name="id2611263"></a><a class="indexterm" name="id2611274"></a><a class="indexterm" name="id2611285"></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="id2611317"></a><a class="indexterm" name="id2611324"></a><a class="indexterm" name="id2611332"></a><a class="indexterm" name="id2611340"></a><a class="indexterm" name="id2611348"></a><a class="indexterm" name="id2611356"></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="id2611406"></a><a name="id2611409"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2611412"></a><a class="indexterm" name="id2611420"></a><a class="indexterm" name="id2611428"></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="id2611452"></a><a name="id2611454"></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="id2611465"></a><a class="indexterm" name="id2611473"></a><a class="indexterm" name="id2611481"></a><a class="indexterm" name="id2611488"></a><a class="indexterm" name="id2611496"></a><a class="indexterm" name="id2611504"></a><a class="indexterm" name="id2611512"></a><a class="indexterm" name="id2611520"></a><a class="indexterm" name="id2611527"></a><a class="indexterm" name="id2611535"></a><a class="indexterm" name="id2611543"></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="id2611574"></a><a name="id2611576"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2611580"></a><a class="indexterm" name="id2611588"></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="id2611608"></a><a class="indexterm" name="id2611616"></a><a class="indexterm" name="id2611624"></a><a class="indexterm" name="id2611632"></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="id2611650"></a><a name="id2611652"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2611655"></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="id2611672"></a><a class="indexterm" name="id2611680"></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="id2611715"></a><a name="id2611717"></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="id2611728"></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="id2611749"></a><a name="id2611751"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2611754"></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="id2611770"></a><a class="indexterm" name="id2611778"></a><a class="indexterm" name="id2611786"></a><a class="indexterm" name="id2611794"></a><a class="indexterm" name="id2611802"></a><a class="indexterm" name="id2611809"></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="id2611854"></a><a name="id2611856"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2611859"></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="id2611896"></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 0cc3d68b5e..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.75.2"><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" title="Chapter 10. Migrating NetWare Server to Samba-3"><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#id2612089">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2612206">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2612318">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2612395">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2612585">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2612594">NetWare Migration Using LDAP Backend</a></span></dt></dl></dd></dl></div><p> - <a class="indexterm" name="id2611934"></a> - <a class="indexterm" name="id2611941"></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="id2611959"></a> - <a class="indexterm" name="id2611965"></a> - <a class="indexterm" name="id2611972"></a> - <a class="indexterm" name="id2611979"></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="id2611994"></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="id2612009"></a> - <a class="indexterm" name="id2612015"></a> - <a class="indexterm" name="id2612022"></a> - <a class="indexterm" name="id2612029"></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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2612089"></a>Introduction</h2></div></div></div><p> - <a class="indexterm" name="id2612096"></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 border="0" summary="Simple list" class="simplelist"><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> + </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 class="itemizedlist" type="disc"><li class="listitem"><p>Very slow performance</p></li><li class="listitem"><p>Available storage hovering around the 5% range</p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p>Extremely slow print spooling.</p></li><li class="listitem"><p> + </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="id2612192"></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" title="Assignment Tasks"><div class="titlepage"><div><div><h3 class="title"><a name="id2612206"></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,12 +89,12 @@ 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="id2612243"></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 border="0" summary="Simple list" class="simplelist"><tr><td> + </p><table class="simplelist" border="0" summary="Simple list"><tr><td> <p>3.0 GHz P4 Processor</p> </td></tr><tr><td> <p>1 GB RAM</p> @@ -111,33 +111,33 @@ </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" title="Dissection and Discussion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2612318"></a>Dissection and Discussion</h2></div></div></div><p> - <a class="indexterm" name="id2612326"></a> - <a class="indexterm" name="id2612333"></a> - <a class="indexterm" name="id2612340"></a> - <a class="indexterm" name="id2612347"></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 <span class="quote">“<span class="quote">LDAP System Administration,</span>”</span> by Gerald Carter. + I had been reading the book “<span class="quote">LDAP System Administration,</span>” 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="id2612366"></a> - <a class="indexterm" name="id2612373"></a> - <a class="indexterm" name="id2612379"></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 <span class="quote">“<span class="quote">LDAP System - Administration,</span>”</span> I installed OpenLDAP (from RPM; later I compiled + the guidance I obtained from “<span class="quote">LDAP System + Administration,</span>” I installed OpenLDAP (from RPM; later I compiled a more current version from source) and built my initial LDAP tree. - </p><div class="sect2" title="Technical Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2612395"></a>Technical Issues</h3></div></div></div><p> - <a class="indexterm" name="id2612403"></a> - <a class="indexterm" name="id2612410"></a> - <a class="indexterm" name="id2612417"></a> - <a class="indexterm" name="id2612424"></a> - <a class="indexterm" name="id2612430"></a> - <a class="indexterm" name="id2612437"></a> - <a class="indexterm" name="id2612444"></a> - <a class="indexterm" name="id2612451"></a> - <a class="indexterm" name="id2612458"></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 @@ -146,7 +146,7 @@ imported into LDAP. This would allow use of LDAP for Linux authentication, IMAP, POP3, and SMTP. </p><p> - Because a decision was made to use Courier-IMAP the schema <span class="quote">“<span class="quote">authldap.schema</span>”</span> + Because a decision was made to use Courier-IMAP the schema “<span class="quote">authldap.schema</span>” from the Courier-IMAP source, tarball is necessary to resolve Courier-specific LDAP directory needs. Where the Courier-IMAP file provided by SUSE is used, this file is named <code class="filename">courier.schema</code>. @@ -183,21 +183,21 @@ cat /etc/passwd | while read l; do echo "loginShell: $loginShell" echo "userPassword: $userPassword" done -</pre></div></div><br class="example-break"><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +</pre></div></div><br class="example-break"><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The PADL MigrationTools are recommended for migration of the UNIX account information into 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" title="Implementation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2612585"></a>Implementation</h2></div></div></div><p> - </p><div class="sect2" title="NetWare Migration Using LDAP Backend"><div class="titlepage"><div><div><h3 class="title"><a name="id2612594"></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 border="0" summary="Simple list" class="simplelist"><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> + </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" title="LDAP Server Configuration"><div class="titlepage"><div><div><h4 class="title"><a name="id2612670"></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="id2612861"></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">“NSS LDAP Control File /etc/ldap.conf”</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="id2612945"></a> - <a class="indexterm" name="id2612952"></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">“The PAM Control File /etc/security/pam_unix2.conf”</a> file. @@ -458,9 +458,9 @@ auth: use_ldap account: use_ldap password: use_ldap session: none -</pre></div></div><br class="example-break"><a class="indexterm" name="id2613035"></a><a class="indexterm" name="id2613041"></a><a class="indexterm" name="id2613048"></a><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><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 class="listitem"><p> + </p></li><li><p> If failover is configured incorrectly, weird behavior can occur. For example, DNS can fail to resolve. </p></li></ul></div><p> @@ -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="id2613084"></a><a class="indexterm" name="id2613091"></a><a class="indexterm" name="id2613098"></a><table border="0" summary="Simple list" class="simplelist"><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="id2613127"></a> - <a class="indexterm" name="id2613134"></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="id2613146"></a> - <a class="indexterm" name="id2613153"></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">“Samba Configuration File smb.conf Part A”</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 border="0" summary="Simple list" class="simplelist"><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="id2613222"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2613234"></a><em class="parameter"><code>netbios name = MASSIVE</code></em></td></tr><tr><td><a class="indexterm" name="id2613246"></a><em class="parameter"><code>server string = Corp File Server</code></em></td></tr><tr><td><a class="indexterm" name="id2613258"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://localhost</code></em></td></tr><tr><td><a class="indexterm" name="id2613270"></a><em class="parameter"><code>pam password change = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2613282"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2613294"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2613306"></a><em class="parameter"><code>log file = /data/samba/log/%m.log</code></em></td></tr><tr><td><a class="indexterm" name="id2613318"></a><em class="parameter"><code>name resolve order = wins host bcast</code></em></td></tr><tr><td><a class="indexterm" name="id2613330"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2613341"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2613353"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2613365"></a><em class="parameter"><code>cups options = Raw</code></em></td></tr><tr><td><a class="indexterm" name="id2613377"></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="id2613389"></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="id2613402"></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="id2613415"></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="id2613428"></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="id2613441"></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="id2613453"></a><em class="parameter"><code>logon script = logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2613465"></a><em class="parameter"><code>logon path = \\%L\profiles\%U\%a</code></em></td></tr><tr><td><a class="indexterm" name="id2613477"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td><a class="indexterm" name="id2613488"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2613500"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2613512"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2613524"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2613536"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2613548"></a><em class="parameter"><code>ldap idmap suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2613560"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2613572"></a><em class="parameter"><code>ldap passwd sync = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2613584"></a><em class="parameter"><code>ldap suffix = ou=MEGANET2,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2613596"></a><em class="parameter"><code>ldap ssl = no</code></em></td></tr><tr><td><a class="indexterm" name="id2613607"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2613619"></a><em class="parameter"><code>admin users = root, "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2613631"></a><em class="parameter"><code>printer admin = "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2613643"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2613683"></a><em class="parameter"><code>comment = Network logon service</code></em></td></tr><tr><td><a class="indexterm" name="id2613695"></a><em class="parameter"><code>path = /data/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2613706"></a><em class="parameter"><code>write list = "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2613718"></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="id2613739"></a><em class="parameter"><code>comment = Roaming Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2613751"></a><em class="parameter"><code>path = /data/samba/profiles/</code></em></td></tr><tr><td><a class="indexterm" name="id2613762"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2613774"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2613786"></a><em class="parameter"><code>veto files = desktop.ini</code></em></td></tr><tr><td><a class="indexterm" name="id2613798"></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="id2613818"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2613830"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2613841"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2613853"></a><em class="parameter"><code>create mask = 0770</code></em></td></tr><tr><td><a class="indexterm" name="id2613865"></a><em class="parameter"><code>veto files = desktop.ini</code></em></td></tr><tr><td><a class="indexterm" name="id2613876"></a><em class="parameter"><code>hide files = desktop.ini</code></em></td></tr><tr><td><a class="indexterm" name="id2613888"></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="id2613909"></a><em class="parameter"><code>comment = Software for %a computers</code></em></td></tr><tr><td><a class="indexterm" name="id2613920"></a><em class="parameter"><code>path = /data/samba/shares/software/%a</code></em></td></tr><tr><td><a class="indexterm" name="id2613932"></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="id2613953"></a><em class="parameter"><code>comment = Public Files</code></em></td></tr><tr><td><a class="indexterm" name="id2613965"></a><em class="parameter"><code>path = /data/samba/shares/public</code></em></td></tr><tr><td><a class="indexterm" name="id2613977"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2613988"></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="id2614009"></a><em class="parameter"><code>comment = Location of documents printed to PDFCreator printer</code></em></td></tr><tr><td><a class="indexterm" name="id2614021"></a><em class="parameter"><code>path = /data/samba/shares/pdf</code></em></td></tr><tr><td><a class="indexterm" name="id2614033"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[EVERYTHING]</code></em></td></tr><tr><td><a class="indexterm" name="id2614072"></a><em class="parameter"><code>comment = All shares</code></em></td></tr><tr><td><a class="indexterm" name="id2614084"></a><em class="parameter"><code>path = /data/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2614095"></a><em class="parameter"><code>valid users = "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2614107"></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="id2614128"></a><em class="parameter"><code>comment = CD-ROM on MASSIVE</code></em></td></tr><tr><td><a class="indexterm" name="id2614139"></a><em class="parameter"><code>path = /mnt</code></em></td></tr><tr><td><a class="indexterm" name="id2614151"></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="id2614171"></a><em class="parameter"><code>comment = Printer Drivers Share</code></em></td></tr><tr><td><a class="indexterm" name="id2614183"></a><em class="parameter"><code>path = /data/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2614195"></a><em class="parameter"><code>write list = root</code></em></td></tr><tr><td><a class="indexterm" name="id2614207"></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="id2614227"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2614239"></a><em class="parameter"><code>path = /data/samba/spool</code></em></td></tr><tr><td><a class="indexterm" name="id2614251"></a><em class="parameter"><code>create mask = 0644</code></em></td></tr><tr><td><a class="indexterm" name="id2614262"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2614274"></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="id2614294"></a><em class="parameter"><code>comment = "Accounting Color Laser Printer"</code></em></td></tr><tr><td><a class="indexterm" name="id2614306"></a><em class="parameter"><code>path = /data/samba/spool/private</code></em></td></tr><tr><td><a class="indexterm" name="id2614318"></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="id2614331"></a><em class="parameter"><code>create mask = 0644</code></em></td></tr><tr><td><a class="indexterm" name="id2614343"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2614354"></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="id2614375"></a><em class="parameter"><code>comment = Engineering Plotter</code></em></td></tr><tr><td><a class="indexterm" name="id2614387"></a><em class="parameter"><code>path = /data/samba/spool</code></em></td></tr><tr><td><a class="indexterm" name="id2614399"></a><em class="parameter"><code>create mask = 0644</code></em></td></tr><tr><td><a class="indexterm" name="id2614410"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2614422"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2614434"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[APPS]</code></em></td></tr><tr><td><a class="indexterm" name="id2614473"></a><em class="parameter"><code>path = /data/samba/shares/Apps</code></em></td></tr><tr><td><a class="indexterm" name="id2614485"></a><em class="parameter"><code>force group = "Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id2614497"></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="id2614517"></a><em class="parameter"><code>path = /data/samba/shares/Accounting</code></em></td></tr><tr><td><a class="indexterm" name="id2614529"></a><em class="parameter"><code>valid users = @acct, "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2614541"></a><em class="parameter"><code>force group = acct</code></em></td></tr><tr><td><a class="indexterm" name="id2614553"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2614564"></a><em class="parameter"><code>create mask = 0660</code></em></td></tr><tr><td><a class="indexterm" name="id2614576"></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="id2614597"></a><em class="parameter"><code>path = /data/samba/shares/Acct_Admin</code></em></td></tr><tr><td><a class="indexterm" name="id2614609"></a><em class="parameter"><code>valid users = @â€acct_adminâ€</code></em></td></tr><tr><td><a class="indexterm" name="id2614621"></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="id2614642"></a><em class="parameter"><code>path = /data/samba/shares/HR_PR</code></em></td></tr><tr><td><a class="indexterm" name="id2614654"></a><em class="parameter"><code>valid users = @hr, @acct_admin</code></em></td></tr><tr><td><a class="indexterm" name="id2614666"></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="id2614686"></a><em class="parameter"><code>path = /data/samba/shares/Engr</code></em></td></tr><tr><td><a class="indexterm" name="id2614698"></a><em class="parameter"><code>valid users = @engr, @receptionist, @truss, "@Domain Admins", cheri</code></em></td></tr><tr><td><a class="indexterm" name="id2614711"></a><em class="parameter"><code>force group = engr</code></em></td></tr><tr><td><a class="indexterm" name="id2614722"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2614734"></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="id2614754"></a><em class="parameter"><code>path = /data/samba/shares/DATA</code></em></td></tr><tr><td><a class="indexterm" name="id2614766"></a><em class="parameter"><code>valid users = @engr, @receptionist, @truss, "@Domain Admins", cheri</code></em></td></tr><tr><td><a class="indexterm" name="id2614779"></a><em class="parameter"><code>force group = engr</code></em></td></tr><tr><td><a class="indexterm" name="id2614790"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2614802"></a><em class="parameter"><code>create mask = 0770</code></em></td></tr><tr><td><a class="indexterm" name="id2614813"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[X]</code></em></td></tr><tr><td><a class="indexterm" name="id2614852"></a><em class="parameter"><code>path = /data/samba/shares/X</code></em></td></tr><tr><td><a class="indexterm" name="id2614864"></a><em class="parameter"><code>valid users = @engr, @acct</code></em></td></tr><tr><td><a class="indexterm" name="id2614876"></a><em class="parameter"><code>force group = engr</code></em></td></tr><tr><td><a class="indexterm" name="id2614887"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2614899"></a><em class="parameter"><code>create mask = 0770</code></em></td></tr><tr><td><a class="indexterm" name="id2614910"></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="id2614931"></a><em class="parameter"><code>path = /data/samba/shares/network</code></em></td></tr><tr><td><a class="indexterm" name="id2614943"></a><em class="parameter"><code>valid users = "@Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id2614955"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2614966"></a><em class="parameter"><code>create mask = 0770</code></em></td></tr><tr><td><a class="indexterm" name="id2614978"></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="id2614998"></a><em class="parameter"><code>path = /data/samba/shares/Utils</code></em></td></tr><tr><td><a class="indexterm" name="id2615010"></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="id2615031"></a><em class="parameter"><code>path = /data/samba/shares/SYS</code></em></td></tr><tr><td><a class="indexterm" name="id2615043"></a><em class="parameter"><code>valid users = chad</code></em></td></tr><tr><td><a class="indexterm" name="id2615054"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2615066"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><p> - <a class="indexterm" name="id2615081"></a> - <a class="indexterm" name="id2615088"></a> - <a class="indexterm" name="id2615094"></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="id2615108"></a> - <a class="indexterm" name="id2615115"></a> - <a class="indexterm" name="id2615122"></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 @@ -556,8 +556,8 @@ fi </p><pre class="screen"> <code class="prompt">root# </code> smbpasswd -w verysecret </pre><p> - where <span class="quote">“<span class="quote">verysecret</span>”</span> is replaced by the LDAP bind password. - </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + where “<span class="quote">verysecret</span>” is replaced by the LDAP bind password. + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The Idealx smbldap-tools package can be configured using a script called <code class="literal">configure.pl</code> that is provided as part of the tool. See <a class="link" href="happy.html" title="Chapter 5. Making Happy Users">“Making Happy Users”</a> for an example of its use. Many administrators, like Misty, choose to do this manually @@ -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="id2615584"></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="id2615685"></a> - <a class="indexterm" name="id2615692"></a> - <a class="indexterm" name="id2615699"></a> - <a class="indexterm" name="id2615706"></a> - <a class="indexterm" name="id2615712"></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="id2615735"></a> - <a class="indexterm" name="id2615742"></a> - <a class="indexterm" name="id2615749"></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="id2615769"></a> - <a class="indexterm" name="id2615776"></a> - <a class="indexterm" name="id2615783"></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="id2615806"></a> - <a class="indexterm" name="id2615812"></a> - <a class="indexterm" name="id2615819"></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 > somefile.ldif </pre><p> - <a class="indexterm" name="id2615843"></a> - <a class="indexterm" name="id2615850"></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="id2615965"></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="id2615989"></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 <-- 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="id2616020"></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">“Kixtart Control File File: logon.kix”</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="id2616317"></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 @@ -1151,34 +1151,34 @@ ENDIF copy the user's profile to the new server. This was very important, and I really struggled with the most effective way to do it. Here is the method that worked for every one of my users on Windows NT, 2000, and XP: - </p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p> + </p><div class="procedure"><ol type="1"><li><p> Log in as the user on the domain. This creates the local copy of the user's profile and copies it to the server as he or she logs out. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Reboot the computer and log in as the local machine administrator. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Right-click My Computer, click Properties, and navigate to the user profiles tab (varies per version of Windows). - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Select the user's local profile <code class="constant">(COMPUTERNAME\username)</code>, and click the <code class="literal">Copy To</code> button. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> In the next dialog, copy it directly to the profiles share on the Samba server (in my case \\PDCname\profiles\user\<architecture>. You will have had to make a connection to the share as that user (e.g., Windows Explorer type \\PDCname\profiles\username). - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> When the copy is complete (it can take a while) log out, and log back in as the user. All of his or her settings and all contents of My Documents, Favorites, and the registry should have been copied successfully. - </p></li><li class="step" title="Step 7"><p> + </p></li><li><p> If it doesn't look right (the dead giveaway is the desktop background), shut down the computer without logging out (power cycle) and try logging in as the user again. If it still doesn't work, repeat the steps above. I only had to ever repeat it once. </p></li></ol></div><p> Words to the Wise: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> If the user was anything other than a standard user on his or her system before, you will save yourself some headaches by giving him or her identical permissions (on the local machine) as his or her domain account <span class="emphasis"><em>before</em></span> @@ -1186,7 +1186,7 @@ ENDIF in the Control Panel, after joining the computer to the domain and before logging on as that user for the first time. Otherwise the user will have trouble with permissions on his or her registry keys. - </p></li><li class="listitem"><p> + </p></li><li><p> If any application was installed for the user only, rather than for the entire system, it will probably not work without being reinstalled. </p></li></ul></div><p> diff --git a/docs/htmldocs/Samba3-ByExample/pr01.html b/docs/htmldocs/Samba3-ByExample/pr01.html index a99ad924ba..b2a3f97066 100644 --- a/docs/htmldocs/Samba3-ByExample/pr01.html +++ b/docs/htmldocs/Samba3-ByExample/pr01.html @@ -1,6 +1,6 @@ -<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.75.2"><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 lang="en-US" class="preface" title="About the Cover Artwork"><div class="titlepage"><div><div><h2 class="title"><a name="id2546434"></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 <span class="quote">“<span class="quote">Samba-3 by Example</span>”</span>. The history of civilization + edition of “<span class="quote">Samba-3 by Example</span>”. The history of civilization demonstrates the fragile nature of freedom. It can be lost in a moment, and once lost, the cost of recovering liberty can be incredible. The last edition cover featured Alfred the Great who liberated England from the diff --git a/docs/htmldocs/Samba3-ByExample/pr02.html b/docs/htmldocs/Samba3-ByExample/pr02.html index 95499769f2..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.75.2"><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 lang="en-US" class="preface" title="Acknowledgments"><div class="titlepage"><div><div><h2 class="title"><a name="id2506912"></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 83324ba3e8..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.75.2"><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 lang="en-US" class="preface" title="Foreword"><div class="titlepage"><div><div><h2 class="title"><a name="id2507137"></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#id2507144">By John M. Weathersby, Executive Director, OSSI</a></span></dt></dl></div><div class="sect1" title="By John M. Weathersby, Executive Director, OSSI"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2507144"></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 6643060eaf..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.75.2"><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" title="Preface"><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#id2507332">Why Is This Book Necessary?</a></span></dt><dd><dl><dt><span class="sect2"><a href="preface.html#id2505043">Samba 3.0.20 Update Edition</a></span></dt></dl></dd><dt><span class="sect1"><a href="preface.html#id2504930">Prerequisites</a></span></dt><dt><span class="sect1"><a href="preface.html#id2504961">Approach</a></span></dt><dt><span class="sect1"><a href="preface.html#id2505027">Summary of Topics</a></span></dt><dt><span class="sect1"><a href="preface.html#id2556726">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,11 +33,11 @@ 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" title="Why Is This Book Necessary?"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2507332"></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 - <span class="quote">“<span class="quote">Samba Cookbook,</span>”</span> and for training materials to + “<span class="quote">Samba Cookbook,</span>” and for training materials to help kick-start the process of mastering Samba. </p><p> The Samba mailing lists users have asked for sample configuration files @@ -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" title="Samba 3.0.20 Update Edition"><div class="titlepage"><div><div><h3 class="title"><a name="id2505043"></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 @@ -111,8 +111,8 @@ </td><td align="justify"> <p> Symbolically linked files and directories on the UNIX host to absolute paths will - now be followed. This can be turned off using <span class="quote">“<span class="quote">wide links = No</span>”</span> in - the share stanza in the <code class="filename">smb.conf</code> file. Turning off <span class="quote">“<span class="quote">wide links</span>”</span> + now be followed. This can be turned off using “<span class="quote">wide links = No</span>” in + the share stanza in the <code class="filename">smb.conf</code> file. Turning off “<span class="quote">wide links</span>” support will degrade server performance because each path must be checked. </p> </td></tr><tr><td align="left"> @@ -122,11 +122,11 @@ </td><td align="justify"> <p> Versions of Samba prior to samba-3.0.11 required the use of the UNIX <code class="constant">root</code> - account from network Windows clients. The new <span class="quote">“<span class="quote">enable privileges = Yes</span>”</span> capability + account from network Windows clients. The new “<span class="quote">enable privileges = Yes</span>” capability 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" title="Prerequisites"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2504930"></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" title="Approach"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2504961"></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" title="Summary of Topics"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2505027"></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> @@ -187,12 +187,12 @@ so let's see how far we can get. If successful, Abmas grows quickly and soon needs to replace all servers and workstations. </p><p><span class="emphasis"><em>TechInfo</em></span> This chapter demands: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Case 1: The simplest <code class="filename">smb.conf</code> file that may + </p><div class="itemizedlist"><ul type="disc"><li><p>Case 1: The simplest <code class="filename">smb.conf</code> file that may reasonably be used. Works with Samba-2.x also. This configuration uses Share Mode security. Encrypted passwords are not used, so there is no <code class="filename">smbpasswd</code> file. - </p></li><li class="listitem"><p>Case 2: Another simple <code class="filename">smb.conf</code> file that adds + </p></li><li><p>Case 2: Another simple <code class="filename">smb.conf</code> file that adds WINS support and printing support. This case deals with a special requirement that demonstrates how to deal with purpose-built software that has a particular requirement @@ -200,7 +200,7 @@ configuration uses Share Mode security and also works with Samba-2.x. Encrypted passwords are not used, so there is no <code class="filename">smbpasswd</code> file. - </p></li><li class="listitem"><p>Case 3: This <code class="filename">smb.conf</code> configuration uses User Mode + </p></li><li><p>Case 3: This <code class="filename">smb.conf</code> configuration uses User Mode security. The file share configuration demonstrates the ability to provide master access to an administrator while restricting all staff to their own work areas. @@ -338,7 +338,7 @@ network. Avoid name resolution problems, identify potential causes of network collisions, avoid Samba configuration options that will weigh the server down. MS distributed file services to make your network fly and much more. This chapter contains a good deal of - <span class="quote">“<span class="quote">Did I tell you about this...?</span>”</span> type of hints to help keep your name on the top + “<span class="quote">Did I tell you about this...?</span>” type of hints to help keep your name on the top performers list. </p></dd><dt><span class="term">Chapter 14 Samba Support.</span></dt><dd><p> This chapter has been added specifically to help those who are seeking professional @@ -364,23 +364,23 @@ 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" title="Conventions Used"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556726"></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 class="itemizedlist" type="disc"><li class="listitem"><p> - TOSHARG2 is used as an abbreviation for the book, <span class="quote">“<span class="quote">The Official Samba-3 - HOWTO and Reference Guide, Second Edition</span>”</span> Editors: John H. Terpstra and Jelmer R. Vernooij, + </p><div class="itemizedlist"><ul type="disc"><li><p> + TOSHARG2 is used as an abbreviation for the book, “<span class="quote">The Official Samba-3 + HOWTO and Reference Guide, Second Edition</span>” Editors: John H. Terpstra and Jelmer R. Vernooij, Publisher: Prentice Hall, ISBN: 0131882228. - </p></li><li class="listitem"><p> - S3bE2 is used as an abbreviation for the book, <span class="quote">“<span class="quote">Samba-3 by Example, Second Edition</span>”</span> + </p></li><li><p> + S3bE2 is used as an abbreviation for the book, “<span class="quote">Samba-3 by Example, Second Edition</span>” Editors: John H. Terpstra, Publisher: Prentice Hall, ISBN: 013188221X. - </p></li><li class="listitem"><p> + </p></li><li><p> Directories and filenames appear in mono-font. For example, <code class="filename">/etc/pam.conf</code>. - </p></li><li class="listitem"><p> + </p></li><li><p> Executable names are bolded. For example, <code class="literal">smbd</code>. - </p></li><li class="listitem"><p> + </p></li><li><p> Menu items and buttons appear in bold. For example, click <span class="guibutton">Next</span>. - </p></li><li class="listitem"><p> + </p></li><li><p> Selecting a menu item is indicated as: <span class="guimenu">Start</span> → <span class="guimenuitem">Control Panel</span> → <span class="guimenuitem">Administrative Tools</span> → <span class="guimenuitem">Active Directory Users and Computers</span> </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="pr03.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ExNetworks.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Foreword </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Part I. Example Network Configurations</td></tr></table></div></body></html> diff --git a/docs/htmldocs/Samba3-ByExample/primer.html b/docs/htmldocs/Samba3-ByExample/primer.html index 0774b17bd4..e407e327b7 100644 --- a/docs/htmldocs/Samba3-ByExample/primer.html +++ b/docs/htmldocs/Samba3-ByExample/primer.html @@ -1,14 +1,14 @@ -<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.75.2"><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" title="Chapter 16. Networking Primer"><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#id2631489">Requirements and Notes</a></span></dt><dt><span class="sect1"><a href="primer.html#id2631650">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2631710">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#id2631827">Exercises</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2631953">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#id2633100">Simple Windows Client Connection Characteristics</a></span></dt><dt><span class="sect2"><a href="primer.html#id2633603">Windows 200x/XP Client Interaction with Samba-3</a></span></dt><dt><span class="sect2"><a href="primer.html#id2634171">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#id2634286">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 of the types of information that flow over the network. Do not worry, this is not - a biology lesson. We won't lose you in unnecessary detail. Think to yourself, <span class="quote">“<span class="quote">This - is easy,</span>”</span> then tackle each exercise without fear. + a biology lesson. We won't lose you in unnecessary detail. Think to yourself, “<span class="quote">This + is easy,</span>” then tackle each exercise without fear. </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" title="Requirements and Notes"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2631489"></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="id2631509"></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 @@ -29,18 +29,18 @@ </p><p> To obtain <code class="literal">Wireshark</code> for your system, please visit the Wireshark <a class="ulink" href="http://www.wireshark.org/download.html" target="_top">download site</a>. - </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The successful completion of this chapter requires that you capture network traffic using <code class="literal">Wireshark</code>. It is recommended that you use a hub, not an Ethernet switch. It is necessary for the device used to act as a repeater, not as a 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="id2631579"></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="id2631595"></a><a class="indexterm" name="id2631606"></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">“Questions and Answers”</a> also provides useful information that may help you to avoid significantly time-consuming networking problems. - </p></div><div class="sect1" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2631650"></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="id2631664"></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 @@ -72,31 +72,31 @@ preparatory reading. </p><p> Recommended preparatory reading: <span class="emphasis"><em>The Official Samba-3 HOWTO and Reference Guide, Second - Edition</em></span> (TOSHARG2) Chapter 9, <span class="quote">“<span class="quote">Network Browsing,</span>”</span> and Chapter 3, - <span class="quote">“<span class="quote">Server Types and Security Modes.</span>”</span> - </p><div class="sect2" title="Assignment Tasks"><div class="titlepage"><div><div><h3 class="title"><a name="id2631710"></a>Assignment Tasks</h3></div></div></div><p><a class="indexterm" name="id2631717"></a> + Edition</em></span> (TOSHARG2) Chapter 9, “<span class="quote">Network Browsing,</span>” and Chapter 3, + “<span class="quote">Server Types and Security Modes.</span>” + </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="id2631735"></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" title="Procedure 16.1. Diagnostic Tasks"><a name="chap01tasks"></a><p class="title"><b>Procedure 16.1. Diagnostic Tasks</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p><a class="indexterm" name="id2631768"></a><a class="indexterm" name="id2631779"></a><a class="indexterm" name="id2631787"></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 class="step" title="Step 2"><p> + </p></li><li><p> Examine network traces to witness how share mode security functions. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Examine network traces to witness the use of user mode security. - </p></li><li class="step" title="Step 4"><p> + </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" title="Exercises"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2631827"></a>Exercises</h2></div></div></div><p> - <a class="indexterm" name="id2631835"></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> @@ -108,10 +108,10 @@ </p><p> For these exercises, our test environment consisted of a SUSE 9.2 Professional Linux Workstation running VMWare 4.5. The following VMWare images were prepared: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Windows 98 name: MILGATE98</p></li><li class="listitem"><p>Windows Me name: WINEPRESSME</p></li><li class="listitem"><p>Windows XP Professional name: LightrayXP</p></li><li class="listitem"><p>Samba-3.0.20 running on a SUSE Enterprise Linux 9</p></li></ul></div><p> + </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="id2631924"></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,140 +119,140 @@ 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" title="Single-Machine Broadcast Activity"><div class="titlepage"><div><div><h3 class="title"><a name="id2631953"></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" title="Procedure 16.2. Monitoring Windows 9x Steps"><a name="id2631964"></a><p class="title"><b>Procedure 16.2. Monitoring Windows 9x Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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> → <span class="guimenuitem">Start</span>. </p><p> Click the following: - </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Update list of packets in real time</p></li><li class="listitem"><p>Automatic scrolling in live capture</p></li><li class="listitem"><p>Enable MAC name resolution</p></li><li class="listitem"><p>Enable network name resolution</p></li><li class="listitem"><p>Enable transport name resolution</p></li></ol></div><p> + </p><div class="orderedlist"><ol type="1"><li><p>Update list of packets in real time</p></li><li><p>Automatic scrolling in live capture</p></li><li><p>Enable MAC name resolution</p></li><li><p>Enable network name resolution</p></li><li><p>Enable transport name resolution</p></li></ol></div><p> Click <span class="guibutton">OK</span>. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Start the Windows 9x/Me machine to be monitored. Let it run for a full 30 minutes. While monitoring, do not press any keyboard keys, do not click any on-screen icons or menus, and do not answer any dialog boxes. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> At the conclusion of 30 minutes, stop the capture. Save the capture to a file so you can go back to it later. Leave this machine running in preparation for the task in <a class="link" href="primer.html#secondmachine" title="Second Machine Startup Broadcast Interaction">“Second Machine Startup Broadcast Interaction”</a>. - </p></li><li class="step" title="Step 4"><p> + </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" title="Findings"><div class="titlepage"><div><div><h4 class="title"><a name="id2632087"></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">“Windows Me Broadcasts The First 10 Minutes”</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">“Windows Me Later Broadcast Sample”</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="id2632204"></a><a class="indexterm" name="id2632215"></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">“Windows Me Startup Broadcast Capture Statistics”</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<00></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<03></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<20></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<00></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<1d></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<1e></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<1b></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<03></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="id2632562"></a><a class="indexterm" name="id2632570"></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<00></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<03></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<20></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<00></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<1d></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<1e></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<1b></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<03></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="id2632587"></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 <span class="quote">“<span class="quote">Implementing CIFS: The Common Internet File System,</span>”</span> + refer to the book “<span class="quote">Implementing CIFS: The Common Internet File System,</span>” by Christopher Hertel, (Prentice Hall PTR, ISBN: 013047116X). - </p></div></div><div class="sect2" title="Second Machine Startup Broadcast Interaction"><div class="titlepage"><div><div><h3 class="title"><a name="secondmachine"></a>Second Machine Startup Broadcast Interaction</h3></div></div></div><p> + </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" title="Procedure 16.3. Monitoring of Second Machine Activity"><a name="id2632624"></a><p class="title"><b>Procedure 16.3. Monitoring of Second Machine Activity</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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> → <span class="guimenuitem">Start</span>. </p><p> Click: - </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Update list of packets in real time</p></li><li class="listitem"><p>Automatic scrolling in live capture</p></li><li class="listitem"><p>Enable MAC name resolution</p></li><li class="listitem"><p>Enable network name resolution</p></li><li class="listitem"><p>Enable transport name resolution</p></li></ol></div><p> + </p><div class="orderedlist"><ol type="1"><li><p>Update list of packets in real time</p></li><li><p>Automatic scrolling in live capture</p></li><li><p>Enable MAC name resolution</p></li><li><p>Enable network name resolution</p></li><li><p>Enable transport name resolution</p></li></ol></div><p> Click <span class="guibutton">OK</span>. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Start the second Windows 9x/Me machine. Let it run for 15 to 20 minutes. While monitoring, do not press any keyboard keys, do not click any on-screen icons or menus, and do not answer any dialog boxes. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> At the conclusion of the capture time, stop the capture. Be sure to save the captured data so you can examine the network data capture again at a later date should that be necessary. - </p></li><li class="step" title="Step 4"><p> + </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" title="Findings"><div class="titlepage"><div><div><h4 class="title"><a name="id2632740"></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">“Second Machine (Windows 98) Capture Statistics”</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 (i.e., the name is already registered by another machine) on the network segment. Those wishing to explore the inner details of the precise mechanism of how this functions should refer to - <span class="quote">“<span class="quote">Implementing CIFS: The Common Internet File System.</span>”</span> + “<span class="quote">Implementing CIFS: The Common Internet File System.</span>” </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<00></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<03></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<20></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<00></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<1d></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<1e></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<1b></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<03></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="id2633022"></a> - <a class="indexterm" name="id2633029"></a> - <a class="indexterm" name="id2633036"></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">“Typical Windows 9x/Me Host Announcement”</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" title="Simple Windows Client Connection Characteristics"><div class="titlepage"><div><div><h3 class="title"><a name="id2633100"></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" title="Procedure 16.4. Client Connection Exploration Steps"><a name="id2633114"></a><p class="title"><b>Procedure 16.4. Client Connection Exploration Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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 class="step" title="Step 2"><p> + </p></li><li><p> Configure another Windows 9x/Me machine (WINEPRESSME) as a client. Make sure that it exports no shared resources. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Start both Windows 9x/Me machines and allow them to stabilize for 10 minutes. Log on to both machines using a user name (JHT) of your choice. Wait approximately 2 minutes before proceeding. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Start Wireshark (or the network sniffer of your choice). - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> From the WINEPRESSME machine, right-click <span class="guimenu">Network Neighborhood</span>, select <span class="guimenuitem">Explore</span>, select <span class="guimenuitem">My Network Places</span> → <span class="guimenuitem">Entire Network</span> → <span class="guimenuitem">MIDEARTH</span> → <span class="guimenuitem">MILGATE98</span> → <span class="guimenuitem">Stuff</span>. Enter the password you set for the <code class="constant">Full Control</code> mode for the <code class="constant">Stuff</code> share. - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> 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 class="step" title="Step 7"><p> - <a class="indexterm" name="id2633245"></a> + </p></li><li><p> + <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 class="step" title="Step 8"><p><a class="indexterm" name="id2633265"></a><a class="indexterm" name="id2633273"></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. This is a <code class="constant">NULL</code> session setup packet. - </p></li><li class="step" title="Step 9"><p> + </p></li><li><p> Return to the packet capture sequence. There will be a number of packets that have been 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 class="step" title="Step 10"><p> - <a class="indexterm" name="id2633317"></a> - <a class="indexterm" name="id2633324"></a> + </p></li><li><p> + <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" title="Findings and Comments"><div class="titlepage"><div><div><h4 class="title"><a name="id2633338"></a>Findings and Comments</h4></div></div></div><p> - <a class="indexterm" name="id2633346"></a> - The <code class="constant">IPC$</code> share serves a vital purpose<sup>[<a name="id2633358" href="#ftn.id2633358" 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="id2633378"></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="id2633398"></a><a class="indexterm" name="id2633403"></a> - <a class="indexterm" name="id2633412"></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">“Typical Windows 9x/Me NULL SessionSetUp AndX Request”</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="id2633498"></a> - <a class="indexterm" name="id2633505"></a> - <a class="indexterm" name="id2633511"></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,12 +271,12 @@ 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">“Typical Windows 9x/Me User SessionSetUp AndX Request”</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="id2633589"></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" title="Windows 200x/XP Client Interaction with Samba-3"><div class="titlepage"><div><div><h3 class="title"><a name="id2633603"></a>Windows 200x/XP Client Interaction with Samba-3</h3></div></div></div><p> - By now you may be asking, <span class="quote">“<span class="quote">Why did you choose to work with Windows 9x/Me?</span>”</span> + </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, “<span class="quote">Why did you choose to work with Windows 9x/Me?</span>” </p><p> First, we want to demonstrate the simple case. This book is not intended to be a detailed treatise on the Windows networking protocols, but rather to provide prescriptive guidance for deployment of Samba. @@ -290,55 +290,55 @@ 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" title="Procedure 16.5. Steps to Explore Windows XP Pro Connection Set-up"><a name="id2633645"></a><p class="title"><b>Procedure 16.5. Steps to Explore Windows XP Pro Connection Set-up</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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 class="step" title="Step 2"><p> + </p></li><li><p> Start the Windows XP Client and wait 5 minutes before proceeding. - </p></li><li class="step" title="Step 3"><p> + </p></li><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> → <span class="guimenuitem">Start</span>. </p><p> Click: - </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Update list of packets in real time</p></li><li class="listitem"><p>Automatic scrolling in live capture</p></li><li class="listitem"><p>Enable MAC name resolution</p></li><li class="listitem"><p>Enable network name resolution</p></li><li class="listitem"><p>Enable transport name resolution</p></li></ol></div><p> + </p><div class="orderedlist"><ol type="1"><li><p>Update list of packets in real time</p></li><li><p>Automatic scrolling in live capture</p></li><li><p>Enable MAC name resolution</p></li><li><p>Enable network name resolution</p></li><li><p>Enable transport name resolution</p></li></ol></div><p> Click <span class="guibutton">OK</span>. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> On the Windows XP Professional client, press <span class="guimenu">Ctrl-Alt-Delete</span> to bring up the domain logon screen. Log in using valid credentials for a domain user account. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> Now proceed to connect to the domain controller as follows: <span class="guimenu">Start</span> → <span class="guimenuitem">(right-click) My Network Places</span> → <span class="guimenuitem">Explore</span> → <span class="guimenuitem">{Left Panel} [+] Entire Network</span> → <span class="guimenuitem">{Left Panel} [+] Microsoft Windows Network</span> → <span class="guimenuitem">{Left Panel} [+] Midearth</span> → <span class="guimenuitem">{Left Panel} [+] Frodo</span> → <span class="guimenuitem">{Left Panel} [+] data</span>. Close the explorer window. </p><p> In this step, our domain name is <code class="constant">Midearth</code>, the domain controller is called <code class="constant">Frodo</code>, and we have connected to a share called <code class="constant">data</code>. - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> Stop the capture on the <code class="literal">Wireshark</code> monitoring machine. Be sure to save the captured data to a file so that you can refer to it again later. - </p></li><li class="step" title="Step 7"><p> + </p></li><li><p> If desired, the Windows XP Professional client and the domain controller are no longer needed for exercises in this chapter. - </p></li><li class="step" title="Step 8"><p> - <a class="indexterm" name="id2633872"></a> - <a class="indexterm" name="id2633878"></a> + </p></li><li><p> + <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 class="step" title="Step 9"><p> - <a class="indexterm" name="id2633899"></a> - <a class="indexterm" name="id2633906"></a> - <a class="indexterm" name="id2633912"></a> + </p></li><li><p> + <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 -> SPNEGO -> netTokenTarg -> responseToken -> NTLMSSP</code> keys. This should reveal that this is a <code class="constant">NULL</code> session setup packet. The <code class="constant">User name: NULL</code> so indicates. An example decode is shown in <a class="link" href="primer.html#XPCap01" title="Figure 16.6. Typical Windows XP NULL Session Setup AndX Request">“Typical Windows XP NULL Session Setup AndX Request”</a>. - </p></li><li class="step" title="Step 10"><p> + </p></li><li><p> Return to the packet capture sequence. There will be a number of packets that have been 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 class="step" title="Step 11"><p> - <a class="indexterm" name="id2633975"></a> + </p></li><li><p> + <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 -> SPNEGO -> netTokenTarg -> responseToken -> NTLMSSP</code> @@ -348,38 +348,38 @@ decode includes the <code class="constant">Lan Manager Response:</code> and the <code class="constant">NTLM Response:</code>. 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 class="step" title="Step 12"><p> - <a class="indexterm" name="id2634037"></a> - <a class="indexterm" name="id2634044"></a> + </p></li><li><p> + <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" title="Discussion"><div class="titlepage"><div><div><h4 class="title"><a name="id2634140"></a>Discussion</h4></div></div></div><p><a class="indexterm" name="id2634146"></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" title="Conclusions to Exercises"><div class="titlepage"><div><div><h3 class="title"><a name="id2634171"></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 class="itemizedlist" type="disc"><li class="listitem"><p> + </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. - </p></li><li class="listitem"><p> + </p></li><li><p> Network browsing protocols query information stored on browse masters that manage information provided by NetBIOS Name Registrations and by way of ongoing host announcements and workgroup announcements. - </p></li><li class="listitem"><p> + </p></li><li><p> All Samba servers must be configured with a mechanism for mapping the <code class="constant">NULL-Session</code> to a valid but nonprivileged UNIX system account. - </p></li><li class="listitem"><p> + </p></li><li><p> The use of Microsoft encrypted passwords is built right into the fabric of Windows networking operations. Such passwords cannot be provided from the UNIX <code class="filename">/etc/passwd</code> database and thus must be stored elsewhere on the UNIX system in a manner that Samba can use. Samba-2.x permitted such encrypted passwords to be stored in the <code class="constant">smbpasswd</code> 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, <span class="quote">“<span class="quote">Account Information Databases.</span>”</span> - </p></li></ul></div></div></div><div class="sect1" title="Dissection and Discussion"><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="id2634259"></a> + databases in concurrent deployment. Refer to <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 10, “<span class="quote">Account Information Databases.</span>” + </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="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,53 +387,53 @@ 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" title="Technical Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2634286"></a>Technical Issues</h3></div></div></div><p> - <a class="indexterm" name="id2634293"></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 the <em class="parameter"><code>guest account</code></em> that must map to a valid UNIX UID. - </p></div></div><div class="sect1" title="Questions and Answers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chap01qa"></a>Questions and Answers</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="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" title="Frequently Asked Questions"><a name="id2634333"></a><dl><dt> <a href="primer.html#id2634340"> + </p><div class="qandaset"><dl><dt> <a href="primer.html#id2628254"> What is the significance of the MIDEARTH<1b> type query? - </a></dt><dt> <a href="primer.html#id2634386"> + </a></dt><dt> <a href="primer.html#id2628301"> What is the significance of the MIDEARTH<1d> type name registration? - </a></dt><dt> <a href="primer.html#id2634460"> + </a></dt><dt> <a href="primer.html#id2628375"> What is the role and significance of the <01><02>__MSBROWSE__<02><01> name registration? - </a></dt><dt> <a href="primer.html#id2634493"> + </a></dt><dt> <a href="primer.html#id2628408"> What is the significance of the MIDEARTH<1e> type name registration? - </a></dt><dt> <a href="primer.html#id2634523"> + </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#id2634601"> + </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#id2634711"> + </a></dt><dt> <a href="primer.html#id2628625"> Can I just use plain-text passwords with Samba? - </a></dt><dt> <a href="primer.html#id2634798"> + </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#id2634839"> + </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#id2634870"> + </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" width="100%" summary="Q and A Set"><col align="left" width="1%"><col><tbody><tr class="question"><td align="left" valign="top"><a name="id2634340"></a><a name="id2634342"></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<1b> type query? </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p> - <a class="indexterm" name="id2634354"></a> - <a class="indexterm" name="id2634364"></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, <span class="quote">“<span class="quote">Technical Overview of Browsing,</span>”</span> + Refer to <span class="emphasis"><em>TOSHARG2,</em></span> Chapter 9, Section 9.7, “<span class="quote">Technical Overview of Browsing,</span>” 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="id2634386"></a><a name="id2634388"></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<1d> 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="id2634400"></a> - <a class="indexterm" name="id2634410"></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. @@ -441,35 +441,35 @@ The LMB is responsible for monitoring all host announcements on the local network and for collating the information contained within them. Using this information, it can provide answers to other Windows network clients that request information such as: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> The list of machines known to the LMB (i.e., the browse list) - </p></li><li class="listitem"><p> + </p></li><li><p> The IP addresses of all domain controllers known for the domain - </p></li><li class="listitem"><p> + </p></li><li><p> The IP addresses of LMBs - </p></li><li class="listitem"><p> + </p></li><li><p> The IP address of the DMB (if one exists) - </p></li><li class="listitem"><p> + </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="id2634460"></a><a name="id2634462"></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 <01><02>__MSBROWSE__<02><01> name registration? </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p> - <a class="indexterm" name="id2634477"></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="id2634493"></a><a name="id2634495"></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<1e> 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="id2634507"></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="id2634523"></a><a name="id2634526"></a></td><td align="left" valign="top"><p> - <a class="indexterm" name="id2634530"></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,27 +482,27 @@ 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="id2634601"></a><a name="id2634604"></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="id2634616"></a> - <a class="indexterm" name="id2634622"></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, <span class="quote">“<span class="quote">WINS The Windows Inter-networking Name Server</span>”</span>); the + Section 9.5, “<span class="quote">WINS The Windows Inter-networking Name Server</span>”); 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, <span class="quote">“<span class="quote">Discussion</span>”</span>). + a correctly configured DNS server (see <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 9, Section 9.3, “<span class="quote">Discussion</span>”). </p><p> - <a class="indexterm" name="id2634654"></a> - <a class="indexterm" name="id2634661"></a> - <a class="indexterm" name="id2634670"></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 beneficial to configure Samba to use <a class="link" href="smb.conf.5.html#NAMERESOLVEORDER" target="_top">name resolve order = wins host cast</a>. - </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </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="id2634711"></a><a name="id2634713"></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="id2634798"></a><a name="id2634800"></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="id2634839"></a><a name="id2634841"></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="id2634870"></a><a name="id2634873"></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.id2633358" href="#id2633358" 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. - <acronym class="acronym">GNU</acronym> General Public License version 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.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 8e935e9e15..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.75.2"><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" title="Chapter 3. Secure Office Networking"><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#id2564639">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2564691">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2564924">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2564939">Technical Issues</a></span></dt><dt><span class="sect2"><a href="secure.html#id2565367">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2565406">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#id2566260">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#id2570721">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2570783">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">“No-Frills Samba Servers”</a>, and then in <a class="link" href="small.html" title="Chapter 2. Small Office Networking">“Small Office Networking”</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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2564639"></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" title="Assignment Tasks"><div class="titlepage"><div><div><h3 class="title"><a name="id2564691"></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" title="Dissection and Discussion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2564924"></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" title="Technical Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2564939"></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="id2564958"></a> - <a class="indexterm" name="id2564964"></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="id2564991"></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="id2565016"></a> - <a class="indexterm" name="id2565023"></a> - <a class="indexterm" name="id2565029"></a> - <a class="indexterm" name="id2565037"></a> + <a class="indexterm" name="id2558932"></a> + <a class="indexterm" name="id2558938"></a> + <a class="indexterm" name="id2558945"></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="id2565066"></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="id2565097"></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="id2565117"></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="id2565130"></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="id2565146"></a> - <a class="indexterm" name="id2565152"></a> - <a class="indexterm" name="id2565161"></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">“Small Office Networking”</a>, <a class="link" href="small.html#dhcp01" title="Example 2.2. Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf">“Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf”</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" title="Hardware Requirements"><div class="titlepage"><div><div><h4 class="title"><a name="id2565213"></a>Hardware Requirements</h4></div></div></div><p> - <a class="indexterm" name="id2565220"></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">“Estimation of Memory Requirements”</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="id2565272"></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="id2565290"></a> - <a class="indexterm" name="id2565297"></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="id2565354"></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" title="Political Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2565367"></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="id2565388"></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" title="Implementation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2565406"></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">“Abmas Network Topology 130 Users”</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. @@ -283,49 +283,49 @@ Given 500 Users and 2 years: here, there are many other good reference books on these subjects. </p><p> The <code class="filename">smb.conf</code> file has the following noteworthy features: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> The NetBIOS name of the Samba server is set to <code class="constant">DIAMOND</code>. - </p></li><li class="listitem"><p> + </p></li><li><p> The Domain name is set to <code class="constant">PROMISES</code>. - </p></li><li class="listitem"><p> - <a class="indexterm" name="id2565463"></a> - <a class="indexterm" name="id2565470"></a> - <a class="indexterm" name="id2565476"></a> + </p></li><li><p> + <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 information on <code class="constant">eth0</code>, nor does it accept any connections from it. 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 class="listitem"><p> - <a class="indexterm" name="id2565509"></a> - <a class="indexterm" name="id2565515"></a> - <a class="indexterm" name="id2565521"></a> + </p></li><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2565543"></a> - <a class="indexterm" name="id2565550"></a> - <a class="indexterm" name="id2565556"></a> + </p></li><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2565585"></a> + </p></li><li><p> + <a class="indexterm" name="id2559501"></a> The Samba server is configured for use by Windows clients as a time server. - </p></li><li class="listitem"><p> - <a class="indexterm" name="id2565597"></a> - <a class="indexterm" name="id2565604"></a> - <a class="indexterm" name="id2565610"></a> + </p></li><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2565640"></a> - <a class="indexterm" name="id2565647"></a> - <a class="indexterm" name="id2565653"></a> + </p></li><li><p> + <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 @@ -333,20 +333,20 @@ Given 500 Users and 2 years: are provided as part of the <code class="filename">SRVTOOLS.EXE</code> toolkit that can be downloaded from the Microsoft FTP <a class="ulink" href="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE" target="_top">site</a>. - </p></li><li class="listitem"><p> - <a class="indexterm" name="id2565682"></a> + </p></li><li><p> + <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="id2565700" href="#ftn.id2565700" 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 class="listitem"><p> - <a class="indexterm" name="id2565717"></a> - <a class="indexterm" name="id2565723"></a> + </p></li><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2565736"></a> - <a class="indexterm" name="id2565743"></a> - <a class="indexterm" name="id2565749"></a> + </p></li><li><p> + <a class="indexterm" name="id2559652"></a> + <a class="indexterm" name="id2559658"></a> + <a class="indexterm" name="id2559665"></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 @@ -355,42 +355,42 @@ Given 500 Users and 2 years: It is the administrator's responsibility to ensure there is a directory in the root of the 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 class="listitem"><p> - <a class="indexterm" name="id2565789"></a> - <a class="indexterm" name="id2565795"></a> + </p></li><li><p> + <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. - </p></li><li class="listitem"><p> + </p></li><li><p> Every user has a private home directory on the UNIX/Linux host. This is mapped to a network drive that is the same for all users. </p></li></ul></div><p> The configuration of the server is the most complex so far. The following steps are used: - </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p> + </p><div class="orderedlist"><ol type="1"><li><p> Basic System Configuration - </p></li><li class="listitem"><p> + </p></li><li><p> Samba Configuration - </p></li><li class="listitem"><p> + </p></li><li><p> DHCP and DNS Server Configuration - </p></li><li class="listitem"><p> + </p></li><li><p> Printer Configuration - </p></li><li class="listitem"><p> + </p></li><li><p> Process Start-up Configuration - </p></li><li class="listitem"><p> + </p></li><li><p> Validation - </p></li><li class="listitem"><p> + </p></li><li><p> Application Share Configuration - </p></li><li class="listitem"><p> + </p></li><li><p> Windows Client Configuration </p></li></ol></div><p> The following sections cover each step in logical and defined detail. - </p><div class="sect2" title="Basic System Configuration"><div class="titlepage"><div><div><h3 class="title"><a name="ch4bsc"></a>Basic System Configuration</h3></div></div></div><p> - <a class="indexterm" name="id2565881"></a> + </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="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">“Abmas Network Topology 130 Users”</a>. - </p><div class="procedure" title="Procedure 3.1. Server Configuration Steps"><a name="id2565897"></a><p class="title"><b>Procedure 3.1. Server Configuration Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2565908"></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"> @@ -402,9 +402,9 @@ server <code class="prompt">root# </code> hostname -f server.abmas.us </pre><p> - </p></li><li class="step" title="Step 2"><p> - <a class="indexterm" name="id2565948"></a> - <a class="indexterm" name="id2565954"></a> + </p></li><li><p> + <a class="indexterm" name="id2559863"></a> + <a class="indexterm" name="id2559870"></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="id2566005"></a> - <a class="indexterm" name="id2566012"></a> - <a class="indexterm" name="id2566018"></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 class="step" title="Step 3"><p> - <a class="indexterm" name="id2566042"></a> - <a class="indexterm" name="id2566049"></a> - <a class="indexterm" name="id2566055"></a> + </p></li><li><p> + <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 > /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="id2566081" href="#ftn.id2566081" class="footnote">6</a>]</sup> - </p></li><li class="step" title="Step 4"><p> - <a class="indexterm" name="id2566094"></a> - <a class="indexterm" name="id2566100"></a> + 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> 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 @@ -497,7 +497,7 @@ $IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE echo "1" > /proc/sys/net/ipv4/ip_forward echo -e "\nNAT firewall done.\n" </pre></div></div><p><br class="example-break"> - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> Execute the following to make the script executable: </p><pre class="screen"> <code class="prompt">root# </code> chmod 755 /usr/local/sbin/abmas-natfw.sh @@ -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="id2566239"></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" title="Samba Configuration"><div class="titlepage"><div><div><h3 class="title"><a name="id2566260"></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" title="Procedure 3.2. Samba Configuration Steps"><a name="id2566272"></a><p class="title"><b>Procedure 3.2. Samba Configuration Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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: @@ -542,18 +542,18 @@ echo -e "\nNAT firewall done.\n" This operation must be performed while logged in as the <code class="literal">root</code> user. Successful operation is clearly indicated. If this installation should fail for any reason, refer to the operating system manufacturer's documentation for guidance. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Install the <code class="filename">smb.conf</code> file shown in <a class="link" href="secure.html#promisnet" title="Example 3.4. 130 User Network with tdbsam [globals] Section">“130 User Network with tdbsam [globals] Section”</a>, <a class="link" href="secure.html#promisnetsvca" title="Example 3.5. 130 User Network with tdbsam Services Section Part A">“130 User Network with tdbsam Services Section Part A”</a>, and <a class="link" href="secure.html#promisnetsvcb" title="Example 3.6. 130 User Network with tdbsam Services Section Part B">“130 User Network with tdbsam Services Section Part B”</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 border="0" summary="Simple list" class="simplelist"><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="id2566378"></a><em class="parameter"><code>workgroup = PROMISES</code></em></td></tr><tr><td><a class="indexterm" name="id2566388"></a><em class="parameter"><code>netbios name = DIAMOND</code></em></td></tr><tr><td><a class="indexterm" name="id2566399"></a><em class="parameter"><code>interfaces = eth1, eth2, lo</code></em></td></tr><tr><td><a class="indexterm" name="id2566409"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566420"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id2566430"></a><em class="parameter"><code>pam password change = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566440"></a><em class="parameter"><code>passwd program = /usr/bin/passwd %u</code></em></td></tr><tr><td><a class="indexterm" name="id2566451"></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="id2566463"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2566474"></a><em class="parameter"><code>unix password sync = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566484"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2566495"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2566505"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2566516"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2566526"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2566537"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2566548"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566558"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2566569"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2566580"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2566591"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2566602"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2566614"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2566625"></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="id2566636"></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="id2566648"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2566660"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2566671"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2566682"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2566693"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2566703"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2566714"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566724"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566734"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566745"></a><em class="parameter"><code>utmp = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566755"></a><em class="parameter"><code>map acl inherit = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566766"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2566776"></a><em class="parameter"><code>cups options = Raw</code></em></td></tr><tr><td><a class="indexterm" name="id2566786"></a><em class="parameter"><code>veto files = /*.eml/*.nws/*.{*}/</code></em></td></tr><tr><td><a class="indexterm" name="id2566798"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2566837"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2566847"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2566858"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2566868"></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="id2566887"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2566897"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2566908"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566918"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566928"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566939"></a><em class="parameter"><code>default devmode = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566949"></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="id2566968"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2566978"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2566989"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2567000"></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="id2567019"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2567029"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2567040"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2567050"></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="id2567069"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2567080"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2567090"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[service]</code></em></td></tr><tr><td><a class="indexterm" name="id2567128"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2567139"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2567149"></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="id2567168"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2567179"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2567190"></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="id2567208"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2567219"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2567229"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2567240"></a><em class="parameter"><code>admin users = bjordan</code></em></td></tr></table></div></div><p><br class="example-break"> - </p></li><li class="step" title="Step 3"><p> - <a class="indexterm" name="id2567257"></a><a class="indexterm" name="id2567262"></a> +</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="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 @@ -565,8 +565,8 @@ Retype new SMB password: XXXXXXXX This account is essential in the regular maintenance of your Samba server. It must never be deleted. If for any reason the account is deleted, you may not be able to recreate this account without considerable trouble. - </p></li><li class="step" title="Step 4"><p> - <a class="indexterm" name="id2567306"></a> + </p></li><li><p> + <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: @@ -592,17 +592,17 @@ root = Administrator # End of File #### </pre><p> - </p></li><li class="step" title="Step 5"><p> - <a class="indexterm" name="id2567348"></a> - <a class="indexterm" name="id2567354"></a> - <a class="indexterm" name="id2567365"></a> - <a class="indexterm" name="id2567376"></a> + </p></li><li><p> + <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">“Small Office Networking”</a>, <a class="link" href="small.html#initGrps" title="Example 2.1. Script to Map Windows NT Groups to UNIX Groups">“Script to Map Windows NT Groups to UNIX Groups”</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="id2567413"></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 @@ -654,14 +654,14 @@ Replicators (S-1-5-32-552) -> -1 System Operators (S-1-5-32-549) -> -1 Users (S-1-5-32-545) -> -1 </pre><p> - </p></li><li class="step" title="Step 6"><p> - <a class="indexterm" name="id2567486"></a> - <a class="indexterm" name="id2567492"></a> - <a class="indexterm" name="id2567498"></a> - <a class="indexterm" name="id2567505"></a> - <a class="indexterm" name="id2567511"></a> - <a class="indexterm" name="id2567517"></a> - <a class="indexterm" name="id2567526"></a> + </p></li><li><p> + <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="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 @@ -685,19 +685,19 @@ Retype new SMB password: XXXXXXXX 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 class="step" title="Step 7"><p> - <a class="indexterm" name="id2567630"></a> - <a class="indexterm" name="id2567638"></a> - <a class="indexterm" name="id2567647"></a> + </p></li><li><p> + <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 class="step" title="Step 8"><p> + </p></li><li><p> Create the directory mount point for the disk subsystem that can be mounted to provide data storage for company files. In this case the mount point is indicated in the <code class="filename">smb.conf</code> 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 class="step" title="Step 9"><p> - <a class="indexterm" name="id2567686"></a> + </p></li><li><p> + <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} @@ -714,7 +714,7 @@ Added user <em class="parameter"><code>username</code></em>. The directory root of the <code class="literal">finsvcs</code> share is <code class="filename">/data/finsvcs</code>. The <code class="filename">/apps</code> directory is the root of the <code class="constant">apps</code> share that provides the application server infrastructure. - </p></li><li class="step" title="Step 10"><p> + </p></li><li><p> The <code class="filename">smb.conf</code> file specifies an infrastructure to support roaming profiles and network logon services. You can now create the file system infrastructure to provide the locations on disk that these services require. Adequate planning is essential, @@ -737,10 +737,10 @@ Added user <em class="parameter"><code>username</code></em>. <code class="prompt">root# </code> chown 'username':users /var/lib/samba/profiles/'username' <code class="prompt">root# </code> chmod ug+wrx,o+rx,-w /var/lib/samba/profiles/'username' </pre><p> - </p></li><li class="step" title="Step 11"><p> - <a class="indexterm" name="id2567880"></a> - <a class="indexterm" name="id2567886"></a> - <a class="indexterm" name="id2567892"></a> + </p></li><li><p> + <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. @@ -756,12 +756,12 @@ net use p: \\diamond\apps <code class="prompt">root# </code> unix2dos < /var/lib/samba/netlogon/scripts/logon.bat.unix \ > /var/lib/samba/netlogon/scripts/logon.bat </pre><p> - </p></li></ol></div></div><div class="sect2" title="Configuration of DHCP and DNS Servers"><div class="titlepage"><div><div><h3 class="title"><a name="ch4dhcpdns"></a>Configuration of DHCP and DNS Servers</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="ch4dhcpdns"></a>Configuration of DHCP and DNS Servers</h3></div></div></div><p> 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" title="Procedure 3.3. DHCP and DNS Server Configuration Steps"><a name="id2567964"></a><p class="title"><b>Procedure 3.3. DHCP and DNS Server Configuration Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2567975"></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">“DHCP Server Configuration File /etc/dhcpd.conf”</a>. @@ -811,19 +811,19 @@ subnet 127.0.0.0 netmask 255.0.0.0 { subnet 123.45.67.64 netmask 255.255.255.252 { } </pre></div></div><p><br class="example-break"> - </p></li><li class="step" title="Step 2"><p> - <a class="indexterm" name="id2568050"></a> + </p></li><li><p> + <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">“DNS Master Configuration File /etc/named.conf Master Section”</a>, <a class="link" href="secure.html#ch4namedvarfwd" title="Example 3.10. DNS Master Configuration File /etc/named.conf Forward Lookup Definition Section">“DNS Master Configuration File /etc/named.conf Forward Lookup Definition Section”</a>, and <a class="link" href="secure.html#ch4namedvarrev" title="Example 3.11. DNS Master Configuration File /etc/named.conf Reverse Lookup Definition Section">“DNS Master Configuration File /etc/named.conf Reverse Lookup Definition Section”</a> files that are concatenated (merged) in this specific order. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Create the files shown in their respective directories as shown in <a class="link" href="secure.html#namedrscfiles" title="Table 3.2. DNS (named) Resource Files">DNS (named) Resource Files</a>. </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">“DNS Localhost Forward Zone File: /var/lib/named/localhost.zone”</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">“DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone”</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">“DNS Root Name Server Hint File: /var/lib/named/root.hint”</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">“DNS Abmas.biz Forward Zone File”</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">“DNS Abmas.us Forward Zone File”</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">“DNS 192.168.1 Reverse Zone File”</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">“DNS 192.168.2 Reverse Zone File”</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="id2568260"></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 ### @@ -1007,8 +1007,8 @@ mail CNAME server dns CNAME server </pre></div></div><p><br class="example-break"> - </p></li><li class="step" title="Step 4"><p> - <a class="indexterm" name="id2568474"></a><a class="indexterm" name="id2568479"></a> + </p></li><li><p> + <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="id2568504"></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 class="step" title="Step 5"><p> - <a class="indexterm" name="id2568525"></a> + </p></li><li><p> + <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: @@ -1035,24 +1035,24 @@ hosts: files dns wins there are a few more steps along the road. First, configure the print spooling and print processing system. Then you can configure the server so that all services start automatically on reboot. You must also manually start all services prior to validation testing. - </p></div><div class="sect2" title="Printer Configuration"><div class="titlepage"><div><div><h3 class="title"><a name="ch4ptrcfg"></a>Printer Configuration</h3></div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ch4ptrcfg"></a>Printer Configuration</h3></div></div></div><p> Network administrators who are new to CUPS based-printing typically experience some difficulty mastering its powerful features. The steps outlined in this section are designed to navigate around the distractions of learning CUPS. Instead of implementing smart features and capabilities, our approach is to use it as a 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" title="Procedure 3.4. Printer Configuration Steps"><a name="id2568584"></a><p class="title"><b>Procedure 3.4. Printer Configuration Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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 class="step" title="Step 2"><p> + </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="id2568610"></a> - <a class="indexterm" name="id2568616"></a> - </p></li><li class="step" title="Step 3"><p> - <a class="indexterm" name="id2568630"></a><a class="indexterm" name="id2568638"></a> + <a class="indexterm" name="id2562524"></a> + <a class="indexterm" name="id2562531"></a> + </p></li><li><p> + <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="id2568681"></a> + <a class="indexterm" name="id2562596"></a> This creates the necessary print queues with no assigned print filter. - </p></li><li class="step" title="Step 4"><p><a class="indexterm" name="id2568696"></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 class="step" title="Step 5"><p><a class="indexterm" name="id2568750"></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 @@ -1083,29 +1083,29 @@ hosts: files dns wins <code class="prompt">root# </code> /usr/sbin/accept qmsf <code class="prompt">root# </code> /usr/sbin/accept hplj6f </pre><p> - </p></li><li class="step" title="Step 6"><p> - <a class="indexterm" name="id2568801"></a> - <a class="indexterm" name="id2568808"></a> - <a class="indexterm" name="id2568815"></a> + </p></li><li><p> + <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 class="step" title="Step 7"><p> - <a class="indexterm" name="id2568843"></a> + </p></li><li><p> + <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 </pre><p> - </p></li><li class="step" title="Step 8"><p> + </p></li><li><p> Printing drivers are installed on each network client workstation. </p></li></ol></div><p> Note: If the parameter <em class="parameter"><code>cups options = Raw</code></em> is specified in the <code class="filename">smb.conf</code> file, the last two steps can be omitted with CUPS version 1.1.18, or later. </p><p> The UNIX system print queues have been configured and are ready for validation testing. - </p></div><div class="sect2" title="Process Startup Configuration"><div class="titlepage"><div><div><h3 class="title"><a name="procstart"></a>Process Startup Configuration</h3></div></div></div><p> - <a class="indexterm" name="id2568908"></a> + </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="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="id2568944"></a> - <a class="indexterm" name="id2568950"></a> - <a class="indexterm" name="id2568957"></a> - <a class="indexterm" name="id2568964"></a> - <a class="indexterm" name="id2568971"></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> 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 @@ -1126,20 +1126,20 @@ application/octet-stream re-read its control files. </p><p> Last, each service must be started to permit system validation to proceed. - </p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p> + </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="id2569022"></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 <code class="prompt">root# </code> chkconfig cups on <code class="prompt">root# </code> chkconfig smb on </pre><p> - </p></li><li class="step" title="Step 2"><p> - <a class="indexterm" name="id2569066"></a> - <a class="indexterm" name="id2569073"></a> - <a class="indexterm" name="id2569080"></a> + </p></li><li><p> + <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: @@ -1149,8 +1149,8 @@ application/octet-stream <code class="prompt">root# </code> /etc/rc.d/init.d/cups restart <code class="prompt">root# </code> /etc/rc.d/init.d/smb restart </pre><p> - </p></li></ol></div></div><div class="sect2" title="Validation"><div class="titlepage"><div><div><h3 class="title"><a name="ch4valid"></a>Validation</h3></div></div></div><p> - <a class="indexterm" name="id2569134"></a> + </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="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" title="Procedure 3.5. Server Validation Steps"><a name="id2569157"></a><p class="title"><b>Procedure 3.5. Server Validation Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2569168"></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 @@ -1186,8 +1186,8 @@ rtt min/avg/max/mdev = 0.131/0.173/0.192/0.026 ms </pre><p> This proves that name resolution via the <code class="filename">/etc/hosts</code> file is working. - </p></li><li class="step" title="Step 2"><p> - <a class="indexterm" name="id2569237"></a> + </p></li><li><p> + <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 @@ -1195,8 +1195,8 @@ rtt min/avg/max/mdev = 0.131/0.173/0.192/0.026 ms </p><pre class="screen"> hosts: dns </pre><p> - </p></li><li class="step" title="Step 3"><p> - <a class="indexterm" name="id2569270"></a> + </p></li><li><p> + <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="id2569300"></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="id2569339"></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 class="step" title="Step 4"><p> - <a class="indexterm" name="id2569365"></a> + </p></li><li><p> + <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">“Process Startup Configuration”</a>). You must edit @@ -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="id2569456"></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. @@ -1259,7 +1259,7 @@ PING diamond (192.168.1.1) 56(84) bytes of data. hosts: files dns wins </pre><p> The system is looking good. Let's move on. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> It would give you peace of mind to know that the DHCP server is running and available for service. You can validate DHCP services by running: @@ -1270,8 +1270,8 @@ hosts: files dns wins </pre><p> 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 class="step" title="Step 6"><p> - <a class="indexterm" name="id2569516"></a> + </p></li><li><p> + <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 @@ -1342,11 +1342,11 @@ Loaded services file OK. ### Remainder cut to save space ### </pre><p> Clear away all errors before proceeding. - </p></li><li class="step" title="Step 7"><p> - <a class="indexterm" name="id2569617"></a> - <a class="indexterm" name="id2569624"></a> - <a class="indexterm" name="id2569630"></a> - <a class="indexterm" name="id2569637"></a> + </p></li><li><p> + <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="id2569669" href="#ftn.id2569669" class="footnote">7</a>]</sup> of it. - </p></li><li class="step" title="Step 8"><p> - <a class="indexterm" name="id2569699"></a> - <a class="indexterm" name="id2569706"></a> + two instances<sup>[<a name="id2563584" href="#ftn.id2563584" class="footnote">7</a>]</sup> of it. + </p></li><li><p> + <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% @@ -1393,10 +1393,10 @@ $rootprompt; ps ax | grep winbind of browsing the server from a Windows client to obtain a list of shares on the server. 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 class="step" title="Step 9"><p> - <a class="indexterm" name="id2569764"></a> - <a class="indexterm" name="id2569771"></a> - <a class="indexterm" name="id2569778"></a> + </p></li><li><p> + <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="id2569824"></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 class="step" title="Step 10"><p> - <a class="indexterm" name="id2569853"></a> + </p></li><li><p> + <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 @@ -1434,8 +1434,8 @@ smb: \> dir 55974 blocks of size 65536. 33968 blocks available smb: \> q </pre><p> - </p></li><li class="step" title="Step 11"><p> - <a class="indexterm" name="id2569910"></a> + </p></li><li><p> + <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 @@ -1509,9 +1509,9 @@ 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" title="Application Share Configuration"><div class="titlepage"><div><div><h3 class="title"><a name="ch4appscfg"></a>Application Share Configuration</h3></div></div></div><p> - <a class="indexterm" name="id2570013"></a> - <a class="indexterm" name="id2570020"></a> + </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="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. @@ -1519,20 +1519,20 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds Some Windows software will only run locally on the desktop computer. Such software is typically not suited for administrative installation. Administratively installed software permits one or more of the following installation choices: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> Install software fully onto a workstation, storing data files on the same workstation. - </p></li><li class="listitem"><p> + </p></li><li><p> Install software fully onto a workstation with central network data file storage. - </p></li><li class="listitem"><p> + </p></li><li><p> Install software to run off a central application server with data files stored on the local workstation. This is often called a minimum installation, or a network client installation. - </p></li><li class="listitem"><p> + </p></li><li><p> Install software to run off a central application server with data files stored 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="id2570072"></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="id2570109"></a> - <a class="indexterm" name="id2570116"></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="id2570138"></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" title="Comments Regarding Software Terms of Use"><div class="titlepage"><div><div><h4 class="title"><a name="id2570170"></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,142 +1596,142 @@ 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="id2570218"></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" title="Windows Client Configuration"><div class="titlepage"><div><div><h3 class="title"><a name="ch4wincfg"></a>Windows Client Configuration</h3></div></div></div><p> + </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> Christine needs to roll out 130 new desktop systems. There is no doubt that she also needs to reinstall many of the notebook computers that will be recycled for use with the new network configuration. The smartest way to handle the challenge of the roll-out program is to build a staged system for each type of target machine, and then use an image replication tool such as Norton 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" title="Procedure 3.6. Windows Client Configuration Procedure"><a name="sbewinclntprep"></a><p class="title"><b>Procedure 3.6. Windows Client Configuration Procedure</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2570268"></a> - <a class="indexterm" name="id2570275"></a> + </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="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. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Join the Windows Domain <code class="constant">PROMISES</code>. Use the Domain Administrator username <code class="constant">root</code> and the SMB password you assigned to this account. A detailed step-by-step procedure for joining a Windows 200x/XP Professional client to a Windows Domain is given in <a class="link" href="appendix.html" title="Chapter 15. A Collection of Useful Tidbits">“A Collection of Useful Tidbits”</a>, <a class="link" href="appendix.html#domjoin" title="Joining a Domain: Windows 200x/XP Professional">“Joining a Domain: Windows 200x/XP Professional”</a>. Reboot the machine as prompted and then log on using the Domain Administrator account (<code class="constant">root</code>). - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Verify <code class="constant">DIAMOND</code> is visible in <span class="guimenu">My Network Places</span>, that it is possible to connect to it and see the shares <span class="guimenuitem">accounts</span>, <span class="guimenuitem">apps</span>, and <span class="guimenuitem">finsvcs</span>, and that it is possible to open each share to reveal its contents. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Create a drive mapping to the <code class="constant">apps</code> share on the server <code class="constant">DIAMOND</code>. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> Perform an administrative installation of each application to be used. Select the options that you wish to use. Of course, you can choose to run applications over the network, correct? - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> Now install all applications to be installed locally. Typical tools include Adobe Acrobat, NTP-based time synchronization software, drivers for specific local devices such as fingerprint scanners, and the like. Probably the most significant application for local installation is antivirus software. - </p></li><li class="step" title="Step 7"><p> + </p></li><li><p> Now install all four printers onto the staging system. The printers you install include the accounting department HP LaserJet 6 and Minolta QMS Magicolor printers. You will also configure identical printers that are located in the financial services department. Install printers on each machine following the steps shown in the Windows client printer preparation procedure below. - </p></li><li class="step" title="Step 8"><p> - <a class="indexterm" name="id2570413"></a> + </p></li><li><p> + <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 defragmentation tool so that the file system is in optimal condition before replication. - </p></li><li class="step" title="Step 9"><p> + </p></li><li><p> 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 class="step" title="Step 10"><p> - <a class="indexterm" name="id2570442"></a> - <a class="indexterm" name="id2570452"></a> + </p></li><li><p> + <a class="indexterm" name="id2564357"></a> + <a class="indexterm" name="id2564366"></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. - </p></li><li class="step" title="Step 11"><p> + </p></li><li><p> Log on to the machine as the local Administrator (the only option), and join the machine to the Domain, following the procedure set out in <a class="link" href="appendix.html" title="Chapter 15. A Collection of Useful Tidbits">“A Collection of Useful Tidbits”</a>, <a class="link" href="appendix.html#domjoin" title="Joining a Domain: Windows 200x/XP Professional">“Joining a Domain: Windows 200x/XP Professional”</a>. The system is now ready for the user to log on, provided you have created a network logon account for that user, of course. - </p></li><li class="step" title="Step 12"><p> + </p></li><li><p> Instruct all users to log on to the workstation using their assigned username and password. - </p></li></ol></div><div class="procedure" title="Procedure 3.7. Windows Client Printer Preparation Procedure"><a name="sbewinclntptrprep"></a><p class="title"><b>Procedure 3.7. Windows Client Printer Preparation Procedure</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> + </p></li></ol></div><div class="procedure"><a name="sbewinclntptrprep"></a><p class="title"><b>Procedure 3.7. Windows Client Printer Preparation Procedure</b></p><ol type="1"><li><p> Click <span class="guimenu">Start</span> → <span class="guimenuitem">Settings</span> → <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 class="step" title="Step 2"><p> + </p></li><li><p> Click <span class="guibutton">Next</span>. In the <span class="guimenuitem">Manufacturer:</span> panel, select <code class="constant">HP</code>. In the <span class="guimenuitem">Printers:</span> panel, select the printer called <code class="constant">HP LaserJet 6</code>. Click <span class="guibutton">Next</span>. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> In the <span class="guimenuitem">Available ports:</span> panel, select <code class="constant">FILE:</code>. Accept the default printer name by clicking - <span class="guibutton">Next</span>. When asked, <span class="quote">“<span class="quote">Would you like to print a - test page?,</span>”</span> click <span class="guimenuitem">No</span>. Click + <span class="guibutton">Next</span>. When asked, “<span class="quote">Would you like to print a + test page?,</span>” click <span class="guimenuitem">No</span>. Click <span class="guibutton">Finish</span>. - </p></li><li class="step" title="Step 4"><p> + </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> → <span class="guimenuitem">Properties</span> → <span class="guisubmenu">Details (Tab)</span> → <span class="guimenuitem">Add Port</span>. - </p></li><li class="step" title="Step 5"><p> + </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">\\DIAMOND\hplj6a</code>. Click <span class="guibutton">OK</span>+<span class="guibutton">OK</span> to complete the installation. - </p></li><li class="step" title="Step 6"><p> + </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" title="Key Points Learned"><div class="titlepage"><div><div><h3 class="title"><a name="id2570721"></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. - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> A simple firewall has been configured to protect the server in the event that the ISP firewall service should fail. - </p></li><li class="listitem"><p> + </p></li><li><p> The Samba configuration uses measures to ensure that only local network users can connect to SMB/CIFS services. - </p></li><li class="listitem"><p> + </p></li><li><p> Samba uses the new <code class="constant">tdbsam</code> passdb backend facility. Considerable complexity was added to Samba functionality. - </p></li><li class="listitem"><p> + </p></li><li><p> A DHCP server was configured to implement dynamic DNS (DDNS) updates to the DNS server. - </p></li><li class="listitem"><p> + </p></li><li><p> The DNS server was configured to permit DDNS only for local network clients. This server also provides primary DNS services for the company Internet presence. - </p></li><li class="listitem"><p> + </p></li><li><p> 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" title="Questions and Answers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2570783"></a>Questions and Answers</h2></div></div></div><p> - </p><div class="qandaset" title="Frequently Asked Questions"><a name="id2570793"></a><dl><dt>1. <a href="secure.html#id2570799"> + </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#id2570868"> + </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#id2570890"> + </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#id2570913"> + </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#id2570941"> + </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#id2570988"> + </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#id2571024"> + </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#id2571048"> + </a></dt><dt>8. <a href="secure.html#id2564963"> Why use dynamic DNS (DDNS)? - </a></dt><dt>9. <a href="secure.html#id2571068"> + </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#id2571153"> + </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" width="100%" summary="Q and A Set"><col align="left" width="1%"><col><tbody><tr class="question" title="1."><td align="left" valign="top"><a name="id2570799"></a><a name="id2570801"></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="id2570857" href="#ftn.id2570857" class="footnote">8</a>]</sup> of the tdbsam backend itself. - </p></td></tr><tr class="question" title="2."><td align="left" valign="top"><a name="id2570868"></a><a name="id2570870"></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" title="3."><td align="left" valign="top"><a name="id2570890"></a><a name="id2570892"></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" title="4."><td align="left" valign="top"><a name="id2570913"></a><a name="id2570915"></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" title="5."><td align="left" valign="top"><a name="id2570941"></a><a name="id2570943"></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" title="6."><td align="left" valign="top"><a name="id2570988"></a><a name="id2570990"></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" title="7."><td align="left" valign="top"><a name="id2571024"></a><a name="id2571026"></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,21 +1807,21 @@ 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" title="8."><td align="left" valign="top"><a name="id2571048"></a><a name="id2571050"></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" title="9."><td align="left" valign="top"><a name="id2571068"></a><a name="id2571070"></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 - a name like <span class="quote">“<span class="quote">myhost.mydomain.tld</span>”</span> where <em class="parameter"><code>tld</code></em> + a name like “<span class="quote">myhost.mydomain.tld</span>” where <em class="parameter"><code>tld</code></em> 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="id2571106" href="#ftn.id2571106" 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="id2571140" href="#ftn.id2571140" 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" title="10."><td align="left" valign="top"><a name="id2571153"></a><a name="id2571155"></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.id2565700" href="#id2565700" 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.id2566081" href="#id2566081" 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.id2569669" href="#id2569669" 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.id2570857" href="#id2570857" 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.id2571106" href="#id2571106" 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.id2571140" href="#id2571140" 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 6d93b6fefd..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.75.2"><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" title="Chapter 1. No-Frills Samba Servers"><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#id2556922">Introduction</a></span></dt><dt><span class="sect1"><a href="simple.html#id2556963">Assignment Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="simple.html#id2557004">Drafting Office</a></span></dt><dt><span class="sect2"><a href="simple.html#id2557714">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#id2561049">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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556922"></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="id2556934" href="#ftn.id2556934" 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" title="Assignment Tasks"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556963"></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 @@ -25,10 +25,10 @@ </p><p> This chapter has three assignments built around fictitious companies: </p><p> - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>A drafting office</p></li><li class="listitem"><p>A charity administration office</p></li><li class="listitem"><p>An accounting office</p></li></ul></div><p> + </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" title="Drafting Office"><div class="titlepage"><div><div><h3 class="title"><a name="id2557004"></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="id2557029"></a> - <a class="indexterm" name="id2557036"></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="id2557063"></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" title="Dissection and Discussion"><div class="titlepage"><div><div><h4 class="title"><a name="id2557084"></a>Dissection and Discussion</h4></div></div></div><p> - <a class="indexterm" name="id2557092"></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="id2557112" href="#ftn.id2557112" 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,24 +73,24 @@ 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" title="Implementation"><div class="titlepage"><div><div><h4 class="title"><a name="id2557141"></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" title="Procedure 1.1. Samba Server Configuration"><a name="id2557164"></a><p class="title"><b>Procedure 1.1. Samba Server Configuration</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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 class="step" title="Step 2"><p> - <a class="indexterm" name="id2557188"></a> - <a class="indexterm" name="id2557196"></a> + </p></li><li><p> + <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"> <code class="prompt">root# </code> rpm -Uvh samba-3.0.20-1.i386.rpm </pre><p> - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Create a mount point for the file system that will be used to store all data files. You can create a directory called <code class="filename">/plans</code>: </p><pre class="screen"> @@ -100,60 +100,60 @@ 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="id2557255"></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> directory as the mount point. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> 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">“Drafting Office smb.conf File”</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 border="0" summary="Simple list" class="simplelist"><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="id2557323"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2557334"></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="id2557352"></a><em class="parameter"><code>path = /plans</code></em></td></tr><tr><td><a class="indexterm" name="id2557363"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557373"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr></table></div></div><p><br class="example-break"> - </p></li><li class="step" title="Step 5"><p> - <a class="indexterm" name="id2557391"></a> +</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="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 class="step" title="Step 6"><p> - <a class="indexterm" name="id2557415"></a> - <a class="indexterm" name="id2557423"></a> - <a class="indexterm" name="id2557429"></a> + </p></li><li><p> + <a class="indexterm" name="id2551329"></a> + <a class="indexterm" name="id2551337"></a> + <a class="indexterm" name="id2551344"></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" title="Procedure 1.2. Windows Client Configuration"><a name="id2557456"></a><p class="title"><b>Procedure 1.2. Windows Client Configuration</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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 class="step" title="Step 2"><p> - <a class="indexterm" name="id2557476"></a> + </p></li><li><p> + <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 class="step" title="Step 3"><p> - <a class="indexterm" name="id2557491"></a> + </p></li><li><p> + <a class="indexterm" name="id2551405"></a> Set the workgroup name on all clients to <code class="constant">MIDEARTH</code>. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Verify on each client that the machine called <code class="constant">SERVER</code> is visible in the <span class="guimenu">Network Neighborhood</span>, that it is 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" title="Validation"><div class="titlepage"><div><div><h4 class="title"><a name="validate1"></a>Validation</h4></div></div></div><p> - <a class="indexterm" name="id2557538"></a> + </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="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 class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2557557"></a> - <a class="indexterm" name="id2557563"></a> - <a class="indexterm" name="id2557569"></a> + </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="id2551484"></a> To check the ability to access the <code class="literal">smbd</code> daemon services, execute the following: </p><pre class="screen"> @@ -172,13 +172,13 @@ --------- -------- MIDEARTH SERVER </pre><p> - <a class="indexterm" name="id2557601"></a> - <a class="indexterm" name="id2557607"></a> + <a class="indexterm" name="id2551515"></a> + <a class="indexterm" name="id2551521"></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 Samba has been running for 15 minutes. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Now verify that Samba correctly handles being passed a username and password, and that it answers its own name. Execute the following: </p><pre class="screen"> @@ -187,13 +187,13 @@ The output should be identical to the previous response. Samba has been configured to ignore all usernames given; instead it uses the <em class="parameter"><code>guest account</code></em> for all connections. - </p></li><li class="step" title="Step 3"><p> - <a class="indexterm" name="id2557657"></a> - <a class="indexterm" name="id2557663"></a> + </p></li><li><p> + <a class="indexterm" name="id2551571"></a> + <a class="indexterm" name="id2551577"></a> From the Windows 9x/Me client, launch Windows Explorer: <span class="guiicon">[Desktop: right-click] Network Neighborhood</span>+<span class="guimenu">Explore</span> → <span class="guimenuitem">[Left Panel] [+] Entire Network</span> → <span class="guimenuitem">[Left Panel] [+] Server</span> → <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" title="Charity Administration Office"><div class="titlepage"><div><div><h3 class="title"><a name="id2557714"></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="id2557776"></a> - <a class="indexterm" name="id2557783"></a> + <a class="indexterm" name="id2551691"></a> + <a class="indexterm" name="id2551697"></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="id2557816"></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" title="Dissection and Discussion"><div class="titlepage"><div><div><h4 class="title"><a name="id2557838"></a>Dissection and Discussion</h4></div></div></div><p> - <a class="indexterm" name="id2557845"></a> - <a class="indexterm" name="id2557851"></a> - <a class="indexterm" name="id2557858"></a> - <a class="indexterm" name="id2557864"></a> + </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> 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="id2557903"></a> - <a class="indexterm" name="id2557909"></a> - <a class="indexterm" name="id2557916"></a> + <a class="indexterm" name="id2551817"></a> + <a class="indexterm" name="id2551824"></a> + <a class="indexterm" name="id2551830"></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">“A Collection of Useful Tidbits”</a>, <a class="link" href="appendix.html#ch12-SUIDSGID" title="Effect of Setting File and Directory SUID/SGID Permissions Explained">“Effect of Setting File and Directory SUID/SGID Permissions Explained”</a>. </p><p> - <a class="indexterm" name="id2557948"></a> - <a class="indexterm" name="id2557955"></a> - <a class="indexterm" name="id2557963"></a> - <a class="indexterm" name="id2557969"></a> + <a class="indexterm" name="id2551863"></a> + <a class="indexterm" name="id2551869"></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="id2557986"></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" title="Implementation"><div class="titlepage"><div><div><h4 class="title"><a name="id2558033"></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">“Charity Administration Office Network”</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" title="Procedure 1.3. Samba Server Configuration"><a name="id2558094"></a><p class="title"><b>Procedure 1.3. Samba Server Configuration</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2558104"></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 class="step" title="Step 2"><p> - <a class="indexterm" name="id2558128"></a> - <a class="indexterm" name="id2558134"></a> + </p></li><li><p> + <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 @@ -322,13 +322,13 @@ Re-enter new password: XXXXXXXX Password changed </pre><p> where XXXXXXXX is a secret password. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Use the 3-Ware IDE RAID Controller firmware utilities to configure the four 200GB drives as a single RAID level 5 drive, with one drive set aside as the hot spare. (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 class="step" title="Step 4"><p> - <a class="indexterm" name="id2558179"></a> + </p></li><li><p> + <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"> @@ -337,12 +337,12 @@ Password changed </pre><p> 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></li><li class="step" title="Step 5"><p> + </p></li><li><p> Use SUSE Linux system tools (refer to the SUSE Administrators Guide for correct procedures) to format the partition with a suitable file system. The reiserfs file system is suitable. Configure this drive to automount using the <code class="filename">/data</code> directory as the mount point. It must be mounted before proceeding. - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> Under the directory called <code class="filename">/data</code>, create two directories named <code class="filename">ftmfiles</code> and <code class="filename">officefiles</code>, and set ownership and permissions: @@ -360,7 +360,7 @@ Password changed /data/officefiles/invitations /data/officefiles/misc </pre><p> - <a class="indexterm" name="id2558287"></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,9 +368,9 @@ 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="id2558316" href="#ftn.id2558316" 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 class="step" title="Step 7"><p> + </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">“Charity Administration Office smb.conf New-style File”</a> in the <code class="filename">/etc/samba</code> directory. This newer <code class="filename">smb.conf</code> file uses user-mode security and is more suited to the mode of operation of Samba-3 than the older share-mode security @@ -379,82 +379,82 @@ Password changed Note: If you want to use the older-style configuration that uses share-mode security, you 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">“Charity Administration Office smb.conf Old-style File”</a> in the <code class="filename">/etc/samba</code> directory. - </p></li><li class="step" title="Step 8"><p> - <a class="indexterm" name="id2558382"></a> + </p></li><li><p> + <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: </p><pre class="screen"> 192.168.1.1 server </pre><p> - </p></li><li class="step" title="Step 9"><p> + </p></li><li><p> Configure the printers with the IP address as shown in <a class="link" href="simple.html#charitynet" title="Figure 1.1. Charity Administration Office Network">“Charity Administration Office Network”</a>. 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 class="step" title="Step 10"><p> - <a class="indexterm" name="id2558427"></a> + </p></li><li><p> + <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 <code class="prompt">root# </code> lpadmin -p hplj5 -v socket://192.168.1.30:9100 -E </pre><p> This creates the necessary print queues with no assigned print filter. - </p></li><li class="step" title="Step 11"><p> - <a class="indexterm" name="id2558460"></a> - <a class="indexterm" name="id2558466"></a> - <a class="indexterm" name="id2558472"></a> + </p></li><li><p> + <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 class="step" title="Step 12"><p> - <a class="indexterm" name="id2558496"></a> + </p></li><li><p> + <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 class="step" title="Step 13"><p> - <a class="indexterm" name="id2558519"></a> + </p></li><li><p> + <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="id2558531"></a> - <a class="indexterm" name="id2558538"></a> - <a class="indexterm" name="id2558544"></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 border="0" summary="Simple list" class="simplelist"><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="id2558608"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2558619"></a><em class="parameter"><code>printing = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2558629"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2558640"></a><em class="parameter"><code>map to guest = Bad User</code></em></td></tr><tr><td><a class="indexterm" name="id2558650"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2558660"></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="id2558679"></a><em class="parameter"><code>comment = Funds Tracking & Management Files</code></em></td></tr><tr><td><a class="indexterm" name="id2558691"></a><em class="parameter"><code>path = /data/ftmfiles</code></em></td></tr><tr><td><a class="indexterm" name="id2558701"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2558712"></a><em class="parameter"><code>force user = abmas</code></em></td></tr><tr><td><a class="indexterm" name="id2558722"></a><em class="parameter"><code>force group = office</code></em></td></tr><tr><td><a class="indexterm" name="id2558732"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558743"></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="id2558762"></a><em class="parameter"><code>comment = General Office Files</code></em></td></tr><tr><td><a class="indexterm" name="id2558772"></a><em class="parameter"><code>path = /data/officefiles</code></em></td></tr><tr><td><a class="indexterm" name="id2558782"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2558793"></a><em class="parameter"><code>force user = abmas</code></em></td></tr><tr><td><a class="indexterm" name="id2558803"></a><em class="parameter"><code>force group = office</code></em></td></tr><tr><td><a class="indexterm" name="id2558814"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558824"></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="id2558843"></a><em class="parameter"><code>comment = Print Temporary Spool Configuration</code></em></td></tr><tr><td><a class="indexterm" name="id2558854"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2558864"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558875"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558885"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558896"></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 border="0" summary="Simple list" class="simplelist"><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="id2558937"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2558948"></a><em class="parameter"><code>security = SHARE</code></em></td></tr><tr><td><a class="indexterm" name="id2558958"></a><em class="parameter"><code>printing = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2558969"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2558979"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558989"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2559000"></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="id2559019"></a><em class="parameter"><code>comment = Funds Tracking & Management Files</code></em></td></tr><tr><td><a class="indexterm" name="id2559030"></a><em class="parameter"><code>path = /data/ftmfiles</code></em></td></tr><tr><td><a class="indexterm" name="id2559040"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2559051"></a><em class="parameter"><code>force user = abmas</code></em></td></tr><tr><td><a class="indexterm" name="id2559061"></a><em class="parameter"><code>force group = office</code></em></td></tr><tr><td><a class="indexterm" name="id2559072"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2559082"></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="id2559101"></a><em class="parameter"><code>comment = General Office Files</code></em></td></tr><tr><td><a class="indexterm" name="id2559111"></a><em class="parameter"><code>path = /data/officefiles</code></em></td></tr><tr><td><a class="indexterm" name="id2559122"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2559132"></a><em class="parameter"><code>force user = abmas</code></em></td></tr><tr><td><a class="indexterm" name="id2559142"></a><em class="parameter"><code>force group = office</code></em></td></tr><tr><td><a class="indexterm" name="id2559153"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2559163"></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="id2559182"></a><em class="parameter"><code>comment = Print Temporary Spool Configuration</code></em></td></tr><tr><td><a class="indexterm" name="id2559193"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2559204"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2559214"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2559225"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2559235"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><div class="procedure" title="Procedure 1.4. Windows Client Configuration"><a name="id2559246"></a><p class="title"><b>Procedure 1.4. Windows Client Configuration</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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 & 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 & 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">“Charity Administration Office Network”</a>. - </p></li><li class="step" title="Step 2"><p> + </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 class="step" title="Step 3"><p> - <a class="indexterm" name="id2559281"></a> + </p></li><li><p> + <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 class="step" title="Step 4"><p> + </p></li><li><p> Set the workgroup name on all clients to <code class="constant">MIDEARTH</code>. - </p></li><li class="step" title="Step 5"><p> - <a class="indexterm" name="id2559309"></a> - Install the <span class="quote">“<span class="quote">Client for Microsoft Networks.</span>”</span> Ensure that the only option - enabled in its properties is the option <span class="quote">“<span class="quote">Logon and restore network connections.</span>”</span> - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> + <a class="indexterm" name="id2553223"></a> + Install the “<span class="quote">Client for Microsoft Networks.</span>” Ensure that the only option + enabled in its properties is the option “<span class="quote">Logon and restore network connections.</span>” + </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 class="step" title="Step 7"><p> - <a class="indexterm" name="id2559344"></a> + </p></li><li><p> + <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 class="step" title="Step 8"><p> - <a class="indexterm" name="id2559373"></a> - <a class="indexterm" name="id2559380"></a> + </p></li><li><p> + <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">“Windows Me Registry Edit File: Disable Password Caching”</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> @@ -471,70 +471,70 @@ REGEDIT4 </p><pre class="screen"> C:\WINDOWS: regedit ME-dpwc.reg </pre><p> - </p></li><li class="step" title="Step 9"><p> + </p></li><li><p> Instruct all users to log onto the workstation using a name and password of their own choosing. The Samba server has been configured to ignore the username and password given. - </p></li><li class="step" title="Step 10"><p> + </p></li><li><p> On each Windows Me workstation, configure a network drive mapping to drive <code class="filename">G:</code> 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 class="procedure" type="1"><li class="step" title="Step 10.1"><p> + </p><div class="procedure"><ol type="1"><li><p> <span class="guimenu">My Network</span> → <span class="guimenuitem">Map Network Drive...</span> - </p></li><li class="step" title="Step 10.2"><p> - In the box labeled <span class="quote">“<span class="quote">Drive:</span>”</span>, type G. - </p></li><li class="step" title="Step 10.3"><p> - In the box labeled <span class="quote">“<span class="quote">Path:</span>”</span>, enter + </p></li><li><p> + In the box labeled “<span class="quote">Drive:</span>”, type G. + </p></li><li><p> + In the box labeled “<span class="quote">Path:</span>”, enter <code class="filename">\\server\officefiles</code>. - </p></li><li class="step" title="Step 10.4"><p> + </p></li><li><p> Click <span class="guimenuitem">Reconnect at logon</span>. Click <span class="guibutton">OK</span>. - </p></li></ol></div></li><li class="step" title="Step 11"><p> + </p></li></ol></div></li><li><p> On each workstation, install the FTM software following the manufacturer's instructions. - </p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 11.1"><p> + </p><div class="procedure"><ol type="1"><li><p> During installation, you are prompted for the name of the Windows 98 server. Enter the name <code class="constant">SERVER</code>. - </p></li><li class="step" title="Step 11.2"><p> + </p></li><li><p> You are prompted for the name of the data share. The prompt defaults to <code class="constant">FTMFILES</code>. Press enter to accept the default value. - </p></li><li class="step" title="Step 11.3"><p> + </p></li><li><p> You are now prompted for the print queue name. The default prompt is the name of the server you entered (<code class="constant">SERVER</code> as follows: <code class="constant">\\SERVER\PRINTQ</code>). Simply accept the default and press enter to continue. The software now completes the installation. - </p></li></ol></div></li><li class="step" title="Step 12"><p> + </p></li></ol></div></li><li><p> Install an office automation software package of the customer's choice. Either Microsoft Office 2003 Standard or OpenOffice 1.1.0 suffices for any functions the office may need to perform. Repeat this on each workstation. - </p></li><li class="step" title="Step 13"><p> + </p></li><li><p> Install a printer on each workstation using the following steps: - </p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 13.1"><p> + </p><div class="procedure"><ol type="1"><li><p> Click <span class="guimenu">Start</span> → <span class="guimenuitem">Settings</span> → <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 class="step" title="Step 13.2"><p> + </p></li><li><p> Click <span class="guibutton">Next</span>. In the Manufacturer: panel, select <code class="constant">HP</code>. In the Printers: panel, select the printer called <code class="constant">HP LaserJet 5/5M Postscript</code>. Click <span class="guibutton">Next</span>. - </p></li><li class="step" title="Step 13.3"><p> + </p></li><li><p> In the Available ports: panel, select <code class="constant">FILE:</code>. Accept the default printer name by clicking <span class="guibutton">Next</span>. When asked, - <span class="quote">“<span class="quote">Would you like to print a test page?</span>”</span>, click + “<span class="quote">Would you like to print a test page?</span>”, click <span class="guimenuitem">No</span>. Click <span class="guibutton">Finish</span>. - </p></li><li class="step" title="Step 13.4"><p> + </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 5/5M Postscript</span> → <span class="guimenuitem">Properties</span> → <span class="guisubmenu">Details (Tab)</span> → <span class="guimenuitem">Add Port</span>. - </p></li><li class="step" title="Step 13.5"><p> + </p></li><li><p> In the Network panel, enter the name of the print queue on the Samba server as follows: <code class="constant">\\SERVER\hplj5</code>. Click <span class="guibutton">OK</span>+<span class="guibutton">OK</span> to complete the installation. - </p></li><li class="step" title="Step 13.6"><p> + </p></li><li><p> 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" title="Validation"><div class="titlepage"><div><div><h4 class="title"><a name="id2559785"></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">“Validation”</a>. - </p></div></div><div class="sect2" title="Accounting Office"><div class="titlepage"><div><div><h3 class="title"><a name="AccountingOffice"></a>Accounting Office</h3></div></div></div><p> + </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 computer users. The network clients were upgraded two years ago. All computers run Windows 2000 Professional. This year the server will be upgraded from an old Windows NT4 server (actually @@ -551,18 +551,18 @@ 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="id2559849"></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 workstation. You must not change anything on the workstations. Mr. Meany gave instructions to - replace the server, <span class="quote">“<span class="quote">but leave everything else alone to avoid staff unrest.</span>”</span> + replace the server, “<span class="quote">but leave everything else alone to avoid staff unrest.</span>” </p><p> 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 <span class="quote">“<span class="quote">the best server Microsoft ever sold - </span>”</span> and that Windows NT and 2000 are <span class="quote">“<span class="quote">too fang-dangled complex!</span>”</span> - </p><div class="sect3" title="Dissection and Discussion"><div class="titlepage"><div><div><h4 class="title"><a name="id2559880"></a>Dissection and Discussion</h4></div></div></div><p> - <a class="indexterm" name="id2559887"></a> + He believes that Windows for Workgroups 3.11 was “<span class="quote">the best server Microsoft ever sold + </span>” and that Windows NT and 2000 are “<span class="quote">too fang-dangled complex!</span>” + </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 @@ -573,7 +573,7 @@ C:\WINDOWS: regedit ME-dpwc.reg </p><p> You have finished configuring the new hardware and have just completed installation of Red Hat Fedora Core2. Roll up your sleeves and let's get to work. - </p></div><div class="sect3" title="Implementation"><div class="titlepage"><div><div><h4 class="title"><a name="AcctgNet"></a>Implementation</h4></div></div></div><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="AcctgNet"></a>Implementation</h4></div></div></div><p> The workstations have fixed IP addresses. The old server runs Windows NT4 Workstation, so it cannot be running as a WINS server. It is best that the new configuration preserves the same configuration. The office does not use Internet access, so security really is not an issue. @@ -582,30 +582,30 @@ 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">“Accounting Office Network Information”</a>. The overall network topology is shown in <a class="link" href="simple.html#acctingnet2" title="Figure 1.2. Accounting Office Network Topology">“Accounting Office Network Topology”</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" title="Procedure 1.5. Migration from Windows NT4 Workstation System to Samba-3"><a name="id2560258"></a><p class="title"><b>Procedure 1.5. Migration from Windows NT4 Workstation System to Samba-3</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p><a class="indexterm" name="id2560269"></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. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Name the new server <code class="constant">CASHPOOL</code> using the standard configuration method. Restart the machine following system prompts. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Install the latest Samba-3 binary Red Hat Linux RPM that is available from the Samba FTP site. - </p></li><li class="step" title="Step 4"><p> - <a class="indexterm" name="id2560314"></a> - <a class="indexterm" name="id2560320"></a> + </p></li><li><p> + <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 class="step" title="Step 5"><p> - Install the <code class="filename">smb.conf</code> file shown<sup>[<a name="id2560350" href="#ftn.id2560350" class="footnote">4</a>]</sup> + </p></li><li><p> + 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">“Accounting Office Network smb.conf Old Style Configuration File”</a>. - </p></li><li class="step" title="Step 6"><p> - <a class="indexterm" name="id2560382"></a> - <a class="indexterm" name="id2560389"></a> - <a class="indexterm" name="id2560395"></a> + </p></li><li><p> + <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">“Accounting Office Network Information”</a>), execute the following: </p><pre class="screen"> @@ -619,8 +619,8 @@ New SMB password: XXXXXXXXX <-- the password from the table Retype new SMB password: XXXXXXXXX Added user "LoginID" </pre><p> - </p></li><li class="step" title="Step 7"><p> - <a class="indexterm" name="id2560444"></a> + </p></li><li><p> + <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 @@ -634,59 +634,59 @@ Added user "LoginID" <code class="prompt">root# </code> chmod -R ug+rwxs,o-r+x /data </pre><p> The data storage structure is now prepared for use. - </p></li><li class="step" title="Step 8"><p> - <a class="indexterm" name="id2560492"></a> + </p></li><li><p> + <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 class="step" title="Step 9"><p> - <a class="indexterm" name="id2560518"></a> - <a class="indexterm" name="id2560524"></a> + </p></li><li><p> + <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 class="step" title="Step 10"><p> - <a class="indexterm" name="id2560549"></a> - <a class="indexterm" name="id2560555"></a> + </p></li><li><p> + <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 class="step" title="Step 11"><p> - <a class="indexterm" name="id2560578"></a> + </p></li><li><p> + <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="id2560590"></a> - <a class="indexterm" name="id2560596"></a> - <a class="indexterm" name="id2560602"></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 <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><li class="step" title="Step 12"><p> + </p></li><li><p> On Alan's workstation, use Windows Explorer to migrate the files from the old server to the new server. The new server should appear in the <span class="guimenu">Network Neighborhood</span> with the name of the old server (<code class="constant">CASHPOOL</code>). - </p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 12.1"><p> + </p><div class="procedure"><ol type="1"><li><p> Log on to Alan's workstation as the user <code class="constant">alan</code>. - </p></li><li class="step" title="Step 12.2"><p> + </p></li><li><p> Launch a second instance of Windows Explorer and navigate to the share called <span class="guiicon">files</span> on the server called <span class="guimenu">STABLE</span>. - </p></li><li class="step" title="Step 12.3"><p> + </p></li><li><p> Click in the right panel, and press <span class="guimenu">Ctrl-A</span> to select all files and directories. Press <span class="guimenu">Ctrl-C</span> to instruct Windows that you wish to copy all selected items. - </p></li><li class="step" title="Step 12.4"><p> + </p></li><li><p> Launch the Windows Explorer, and navigate to the share called <span class="guiicon">files</span> on the server called <span class="guimenu">CASHPOOL</span>. Click in the right panel, and then press <span class="guimenu">Ctrl-V</span> to commence the copying process. - </p></li></ol></div></li><li class="step" title="Step 13"><p> + </p></li></ol></div></li><li><p> Verify that the files are being copied correctly from the Windows NT4 machine to the Samba-3 server. This is best done on the Samba-3 server. Check the contents of the directory tree under <code class="filename">/data</code> by executing the following command: @@ -703,44 +703,44 @@ application/octet-stream <code class="prompt">root# </code> chgrp -R accts /data <code class="prompt">root# </code> chmod -R ug+rwxs,o-r+x /data </pre><p> - </p></li><li class="step" title="Step 14"><p> + </p></li><li><p> 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 border="0" summary="Simple list" class="simplelist"><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="id2560830"></a><em class="parameter"><code>workgroup = BILLMORE</code></em></td></tr><tr><td><a class="indexterm" name="id2560840"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2560851"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560861"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2560872"></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="id2560891"></a><em class="parameter"><code>comment = Work area files</code></em></td></tr><tr><td><a class="indexterm" name="id2560902"></a><em class="parameter"><code>path = /data/%U</code></em></td></tr><tr><td><a class="indexterm" name="id2560912"></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="id2560931"></a><em class="parameter"><code>comment = Master work area files</code></em></td></tr><tr><td><a class="indexterm" name="id2560942"></a><em class="parameter"><code>path = /data</code></em></td></tr><tr><td><a class="indexterm" name="id2560952"></a><em class="parameter"><code>valid users = alan</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> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2560981"></a><em class="parameter"><code>comment = Print Temporary Spool Configuration</code></em></td></tr><tr><td><a class="indexterm" name="id2560993"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2561003"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2561014"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2561024"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2561034"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"></div></div></div><div class="sect1" title="Questions and Answers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561049"></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" title="Frequently Asked Questions"><a name="id2561061"></a><dl><dt> <a href="simple.html#id2561067"> + </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#id2561093"> + </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#id2561144"> + </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#id2561171"> + </a></dt><dt> <a href="simple.html#id2555087"> What is better about CUPS printing than LPRng printing? - </a></dt><dt> <a href="simple.html#id2561215"> + </a></dt><dt> <a href="simple.html#id2555131"> When should Windows client IP addresses be hard-coded? - </a></dt><dt> <a href="simple.html#id2561241"> + </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#id2561279"> + </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#id2561304"> + </a></dt><dt> <a href="simple.html#id2555220"> When would you set the global parameter disable spoolss? - </a></dt><dt> <a href="simple.html#id2561390"> + </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#id2561414"> + </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" width="100%" summary="Q and A Set"><col align="left" width="1%"><col><tbody><tr class="question"><td align="left" valign="top"><a name="id2561067"></a><a name="id2561069"></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="id2561093"></a><a name="id2561095"></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="id2561144"></a><a name="id2561146"></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="id2561171"></a><a name="id2561173"></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="id2561215"></a><a name="id2561217"></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="id2561241"></a><a name="id2561243"></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="id2561279"></a><a name="id2561282"></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="id2561304"></a><a name="id2561306"></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 @@ -830,17 +830,17 @@ application/octet-stream considers the printer to be local, it attempts to issue the <em class="parameter"><code>OpenPrinterEx()</code></em> call requesting access rights associated with the logged on user. If the user possesses local administrator rights but not root privilege on the Samba host (often the case), the <em class="parameter"><code>OpenPrinterEx()</code></em> call fails. The result is - that the client now displays an <span class="quote">“<span class="quote">Access Denied; Unable to connect</span>”</span> message in the printer queue window + that the client now displays an “<span class="quote">Access Denied; Unable to connect</span>” 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="id2561390"></a><a name="id2561392"></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="id2561414"></a><a name="id2561416"></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,14 +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.id2556934" href="#id2556934" 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.id2557112" href="#id2557112" 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"></div><div class="footnote"><p><sup>[<a name="ftn.id2560350" href="#id2560350" 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 362209cefe..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.75.2"><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" title="Chapter 2. Small Office Networking"><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#id2561519">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2561542">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2561602">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2561650">Technical Issues</a></span></dt><dt><span class="sect2"><a href="small.html#id2561848">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2561869">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2563413">Validation</a></span></dt><dt><span class="sect2"><a href="small.html#id2564061">Notebook Computers: A Special Case</a></span></dt><dt><span class="sect2"><a href="small.html#id2564087">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2564161">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">“No-Frills Samba Servers”</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="id2561475"></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 @@ -33,10 +33,10 @@ features, and yet he had happy users. Months later he was still adding new innovations. He always asked the users if a particular feature was what they wanted. He asked his boss for a raise - and got it. He often told me, <span class="quote">“<span class="quote">Always keep a few new tricks up your - sleeves for when you need them.</span>”</span> Was he smart? You decide. Let's + and got it. He often told me, “<span class="quote">Always keep a few new tricks up your + sleeves for when you need them.</span>” Was he smart? You decide. Let's get on with our next exercise. - </p><div class="sect1" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561519"></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" title="Assignment Tasks"><div class="titlepage"><div><div><h3 class="title"><a name="id2561542"></a>Assignment Tasks</h3></div></div></div><p> - <a class="indexterm" name="id2561549"></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,28 +80,28 @@ 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" title="Dissection and Discussion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561602"></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 class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> Scalability, from 52 to over 100 users in 12 months - </p></li><li class="listitem"><p> + </p></li><li><p> Mobile computing capability - <a class="indexterm" name="id2561623"></a> - </p></li><li class="listitem"><p> + <a class="indexterm" name="id2555539"></a> + </p></li><li><p> Improved reliability and usability - </p></li><li class="listitem"><p> + </p></li><li><p> Easier administration </p></li></ul></div><p> 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">“Accounting Office”</a>). - </p><div class="sect2" title="Technical Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2561650"></a>Technical Issues</h3></div></div></div><p> - <a class="indexterm" name="id2561657"></a> - <a class="indexterm" name="id2561664"></a> - <a class="indexterm" name="id2561670"></a> - <a class="indexterm" name="id2561676"></a> - <a class="indexterm" name="id2561682"></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"> @@ -110,7 +110,7 @@ All printers will be configured as DHCP clients. The DHCP server will assign the printer a fixed IP address by way of its Ethernet interface (MAC) address. See <a class="link" href="small.html#dhcp01" title="Example 2.2. Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf">“Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf”</a>. - </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The <code class="filename">smb.conf</code> file you are creating in this exercise can be used with equal effectiveness with Samba-2.2.x series releases. This is deliberate so that in the next chapter it is possible to start with the installation that you have created here, migrate it @@ -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="id2561741"></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="id2561772"></a> - <a class="indexterm" name="id2561780"></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="id2561834"></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" title="Political Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2561848"></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" title="Implementation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561869"></a>Implementation</h2></div></div></div><p> - <a class="indexterm" name="id2561877"></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">“Implementation”</a> to meet the new requirements. The decision to treat this case, as with @@ -175,23 +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">“Migrating NT4 Domain to Samba-3”</a>. Additionally, a fresh installation makes the example easier to follow. </p><p> - <a class="indexterm" name="id2561903"></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="id2561918"></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="id2561932"></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><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" title="Procedure 2.1. Server Installation Steps"><a name="id2561987"></a><p class="title"><b>Procedure 2.1. Server Installation Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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 class="step" title="Step 2"><p> - <a class="indexterm" name="id2562008"></a> + </p></li><li><p> + <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: @@ -202,15 +202,15 @@ 192.168.1.11 hplj4 192.168.2.10 qms </pre><p> - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Install the Samba-3 binary RPM from the Samba-Team FTP site. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Install the ISC DHCP server using the UNIX/Linux system tools available to you. - </p></li><li class="step" title="Step 5"><p> - <a class="indexterm" name="id2562059"></a> - <a class="indexterm" name="id2562065"></a> - <a class="indexterm" name="id2562071"></a> - <a class="indexterm" name="id2562078"></a> + </p></li><li><p> + <a class="indexterm" name="id2555975"></a> + <a class="indexterm" name="id2555981"></a> + <a class="indexterm" name="id2555988"></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 @@ -220,12 +220,12 @@ echo 1 > /proc/sys/net/ipv4/ip_forward </pre><p> This causes the Linux kernel to forward IP packets so that it acts as a router. - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> Install the <code class="filename">smb.conf</code> file as shown in <a class="link" href="small.html#acct2conf" title="Example 2.3. Accounting Office Network smb.conf File [globals] Section">“Accounting Office Network smb.conf File [globals] Section”</a> and <a class="link" href="small.html#acct3conf" title="Example 2.4. Accounting Office Network smb.conf File Services and Shares Section">“Accounting Office Network smb.conf File Services and Shares Section”</a>. Combine these two examples to form a single <code class="filename">/etc/samba/smb.conf</code> file. - </p></li><li class="step" title="Step 7"><p> - <a class="indexterm" name="id2562137"></a> + </p></li><li><p> + <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 @@ -233,13 +233,13 @@ New SMB password: XXXXXXX Retype new SMB password: XXXXXXX <code class="prompt">root# </code> </pre><p> - <a class="indexterm" name="id2562166"></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 class="step" title="Step 8"><p> - <a class="indexterm" name="id2562184"></a> + </p></li><li><p> + <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: @@ -265,14 +265,14 @@ root = Administrator # End of File #### </pre><p> - </p></li><li class="step" title="Step 9"><p> - <a class="indexterm" name="id2562224"></a> + </p></li><li><p> + <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">“Script to Map Windows NT Groups to UNIX Groups”</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="id2562252"></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 @@ -321,31 +321,31 @@ Replicators (S-1-5-32-552) -> -1 System Operators (S-1-5-32-549) -> -1 Users (S-1-5-32-545) -> -1 </pre><p> - </p></li><li class="step" title="Step 10"><p> - <a class="indexterm" name="id2562330"></a> - <a class="indexterm" name="id2562337"></a> - <a class="indexterm" name="id2562345"></a> + </p></li><li><p> + <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="id2562370"></a> - <a class="indexterm" name="id2562376"></a> - <a class="indexterm" name="id2562382"></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. - </p></li><li class="step" title="Step 11"><p> + </p></li><li><p> 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 class="step" title="Step 12"><p> + </p></li><li><p> Create the directory mount point for the disk subsystem that is mounted to provide data storage for company files. In this case the mount point is indicated in the <code class="filename">smb.conf</code> file is <code class="filename">/data</code>. Format the file system as required, mount the formatted file system partition using <code class="literal">mount</code>, and make the appropriate changes in <code class="filename">/etc/fstab</code>. - </p></li><li class="step" title="Step 13"><p> + </p></li><li><p> Create the top-level file storage directories are follows: </p><pre class="screen"> <code class="prompt">root# </code> mkdir -p /data/{accounts,finsvcs} @@ -357,42 +357,42 @@ Users (S-1-5-32-545) -> -1 Each department is responsible for creating its own directory structure within its share. The directory root of the <code class="literal">accounts</code> share is <code class="filename">/data/accounts</code>. The directory root of the <code class="literal">finsvcs</code> share is <code class="filename">/data/finsvcs</code>. - </p></li><li class="step" title="Step 14"><p> + </p></li><li><p> 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">“Abmas Accounting 52-User Network Topology”</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="id2562526"></a> - <a class="indexterm" name="id2562532"></a> - </p></li><li class="step" title="Step 15"><p> - <a class="indexterm" name="id2562545"></a> - <a class="indexterm" name="id2562553"></a> + <a class="indexterm" name="id2556442"></a> + <a class="indexterm" name="id2556449"></a> + </p></li><li><p> + <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="id2562584"></a> + <a class="indexterm" name="id2556500"></a> This creates the necessary print queues with no assigned print filter. - </p></li><li class="step" title="Step 16"><p> - <a class="indexterm" name="id2562598"></a> - <a class="indexterm" name="id2562604"></a> - <a class="indexterm" name="id2562611"></a> + </p></li><li><p> + <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 class="step" title="Step 17"><p> - <a class="indexterm" name="id2562635"></a> + </p></li><li><p> + <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 class="step" title="Step 18"><p> - <a class="indexterm" name="id2562658"></a> + </p></li><li><p> + <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">“Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf”</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="id2562690"></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; @@ -436,15 +436,15 @@ subnet 192.168.2.0 netmask 255.255.255.0 { subnet 127.0.0.0 netmask 255.0.0.0 { } </pre></div></div><p><br class="example-break"> - </p></li><li class="step" title="Step 19"><p> + </p></li><li><p> 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="id2562734"></a> - <a class="indexterm" name="id2562740"></a> - <a class="indexterm" name="id2562747"></a> - <a class="indexterm" name="id2562753"></a> - <a class="indexterm" name="id2562759"></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> </p><pre class="screen"> <code class="prompt">root# </code> chkconfig dhcp on <code class="prompt">root# </code> chkconfig smb on @@ -453,13 +453,13 @@ subnet 127.0.0.0 netmask 255.0.0.0 { <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><li class="step" title="Step 20"><p> - <a class="indexterm" name="id2562810"></a> - <a class="indexterm" name="id2562816"></a> - <a class="indexterm" name="id2562824"></a> - <a class="indexterm" name="id2562830"></a> - <a class="indexterm" name="id2562837"></a> - <a class="indexterm" name="id2562843"></a> + </p></li><li><p> + <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 @@ -467,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 border="0" summary="Simple list" class="simplelist"><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="id2562901"></a><em class="parameter"><code>workgroup = BILLMORE</code></em></td></tr><tr><td><a class="indexterm" name="id2562911"></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="id2562923"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2562933"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2562944"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2562955"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2562965"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2562976"></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="id2562988"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2562999"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2563010"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2563022"></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="id2563033"></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="id2563045"></a><em class="parameter"><code>logon script = scripts\login.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2563056"></a><em class="parameter"><code>logon path = </code></em></td></tr><tr><td><a class="indexterm" name="id2563066"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2563077"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2563087"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2563098"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2563108"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2563148"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2563159"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2563169"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2563180"></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="id2563198"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2563209"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2563219"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2563230"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2563240"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2563250"></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="id2563269"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2563280"></a><em class="parameter"><code>path = /data/%U</code></em></td></tr><tr><td><a class="indexterm" name="id2563291"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2563301"></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="id2563320"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2563330"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2563341"></a><em class="parameter"><code>valid users = %G</code></em></td></tr><tr><td><a class="indexterm" name="id2563351"></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="id2563370"></a><em class="parameter"><code>comment = Financial Service Files</code></em></td></tr><tr><td><a class="indexterm" name="id2563381"></a><em class="parameter"><code>path = /data/finsvcs</code></em></td></tr><tr><td><a class="indexterm" name="id2563391"></a><em class="parameter"><code>valid users = %G</code></em></td></tr><tr><td><a class="indexterm" name="id2563402"></a><em class="parameter"><code>read only = No</code></em></td></tr></table></div></div><br class="example-break"><div class="sect2" title="Validation"><div class="titlepage"><div><div><h3 class="title"><a name="id2563413"></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" title="Procedure 2.2. Validation Steps"><a name="id2563425"></a><p class="title"><b>Procedure 2.2. Validation Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2563435"></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: @@ -517,11 +517,11 @@ Unknown parameter encountered: "dogbert" Ignoring unknown parameter "dogbert" </pre><p> Clear away all errors before proceeding, and start or restart samba as necessary. - </p></li><li class="step" title="Step 2"><p> - <a class="indexterm" name="id2563515"></a> - <a class="indexterm" name="id2563521"></a> - <a class="indexterm" name="id2563527"></a> - <a class="indexterm" name="id2563533"></a> + </p></li><li><p> + <a class="indexterm" name="id2557431"></a> + <a class="indexterm" name="id2557437"></a> + <a class="indexterm" name="id2557443"></a> + <a class="indexterm" name="id2557450"></a> Check that the Samba server is running: </p><pre class="screen"> <code class="prompt">root# </code> ps ax | grep mbd @@ -537,8 +537,8 @@ $rootprompt; ps ax | grep winbind two instances of it. For more information regarding <code class="literal">winbindd</code>, see <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 class="step" title="Step 3"><p> - <a class="indexterm" name="id2563584"></a> + </p></li><li><p> + <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% @@ -566,10 +566,10 @@ $rootprompt; ps ax | grep winbind of browsing the server from a Windows client to obtain a list of shares on the server. 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 class="step" title="Step 4"><p> - <a class="indexterm" name="id2563635"></a> - <a class="indexterm" name="id2563641"></a> - <a class="indexterm" name="id2563647"></a> + </p></li><li><p> + <a class="indexterm" name="id2557551"></a> + <a class="indexterm" name="id2557557"></a> + <a class="indexterm" name="id2557564"></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 @@ -587,8 +587,8 @@ hplj4 (192.168.1.11) at 08:00:46:7A:35:E4 [ether] on eth0 The MAC address <code class="constant">08:00:46:7A:35:E4</code> matches that specified for the 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 class="step" title="Step 5"><p> - <a class="indexterm" name="id2563708"></a> + </p></li><li><p> + <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 @@ -605,53 +605,53 @@ smb: \> dir 65387 blocks of size 65536. 28590 blocks available smb: \> q </pre><p> - </p></li></ol></div></div><div class="procedure" title="Procedure 2.3. Windows XP Professional Client Configuration"><a name="id2563756"></a><p class="title"><b>Procedure 2.3. Windows XP Professional Client Configuration</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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">“Abmas Accounting 52-User Network Topology”</a>. All clients use DHCP for TCP/IP protocol stack configuration. - <a class="indexterm" name="id2563774"></a> - <a class="indexterm" name="id2563780"></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 class="step" title="Step 2"><p> + </p></li><li><p> Join the Windows Domain called <code class="constant">BILLMORE</code>. Use the Domain Administrator username <code class="constant">root</code> and the SMB password you assigned to this account. A detailed step-by-step procedure for joining a Windows 200x/XP Professional client to a Windows Domain is given in <a class="link" href="appendix.html" title="Chapter 15. A Collection of Useful Tidbits">“A Collection of Useful Tidbits”</a>, <a class="link" href="appendix.html#domjoin" title="Joining a Domain: Windows 200x/XP Professional">“Joining a Domain: Windows 200x/XP Professional”</a>. Reboot the machine as prompted and then log on using a Domain User account. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Verify on each client that the machine called <code class="constant">SLEETH</code> is visible in <span class="guimenu">My Network Places</span>, that it is possible to connect to it and see the shares <span class="guimenuitem">accounts</span> and <span class="guimenuitem">finsvcs</span>, and that it is possible to open that share to reveal its contents. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Instruct all users to log onto the workstation using their assigned username and password. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> Install a printer on each using the following steps: - </p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 5.1"><p> + </p><div class="procedure"><ol type="1"><li><p> Click <span class="guimenu">Start</span> → <span class="guimenuitem">Settings</span> → <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 class="step" title="Step 5.2"><p> + </p></li><li><p> Click <span class="guibutton">Next</span>. In the <span class="guimenuitem">Manufacturer:</span> panel, select <code class="constant">HP</code>. In the <span class="guimenuitem">Printers:</span> panel, select the printer called <code class="constant">HP LaserJet 4</code>. Click <span class="guibutton">Next</span>. - </p></li><li class="step" title="Step 5.3"><p> + </p></li><li><p> In the <span class="guimenuitem">Available ports:</span> panel, select <code class="constant">FILE:</code>. Accept the default printer name by clicking - <span class="guibutton">Next</span>. When asked, <span class="quote">“<span class="quote">Would you like to print a - test page?</span>”</span>, click <span class="guimenuitem">No</span>. Click + <span class="guibutton">Next</span>. When asked, “<span class="quote">Would you like to print a + test page?</span>”, click <span class="guimenuitem">No</span>. Click <span class="guibutton">Finish</span>. - </p></li><li class="step" title="Step 5.4"><p> + </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 4</span> → <span class="guimenuitem">Properties</span> → <span class="guisubmenu">Details (Tab)</span> → <span class="guimenuitem">Add Port</span>. - </p></li><li class="step" title="Step 5.5"><p> + </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">\\SERVER\hplj4</code>. Click <span class="guibutton">OK</span>+<span class="guibutton">OK</span> to complete the installation. - </p></li><li class="step" title="Step 5.6"><p> + </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" title="Notebook Computers: A Special Case"><div class="titlepage"><div><div><h3 class="title"><a name="id2564061"></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. @@ -661,56 +661,56 @@ smb: \> 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" title="Key Points Learned"><div class="titlepage"><div><div><h3 class="title"><a name="id2564087"></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 class="itemizedlist" type="disc"><li class="listitem"><p> - <a class="indexterm" name="id2564107"></a> + </p><div class="itemizedlist"><ul type="disc"><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2564120"></a> + </p></li><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2564134"></a> + </p></li><li><p> + <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. - </p></li><li class="listitem"><p> + </p></li><li><p> You experienced the benefits of centrally managed user accounts on the server. - </p></li><li class="listitem"><p> + </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" title="Questions and Answers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2564161"></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" title="Frequently Asked Questions"><a name="id2564172"></a><dl><dt>1. <a href="small.html#id2564174"> + </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#id2564201"> + </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#id2564232"> + </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#id2564268"> + </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#id2564307"> + </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#id2564346"> + </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#id2564382"> + </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#id2564450"> + </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#id2564494"> + </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#id2564544"> + </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" width="100%" summary="Q and A Set"><col align="left" width="1%"><col><tbody><tr class="question" title="1."><td align="left" valign="top"><a name="id2564174"></a><a name="id2564176"></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 @@ -719,7 +719,7 @@ smb: \> 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" title="2."><td align="left" valign="top"><a name="id2564201"></a><a name="id2564203"></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> @@ -728,14 +728,14 @@ smb: \> 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" title="3."><td align="left" valign="top"><a name="id2564232"></a><a name="id2564234"></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" title="4."><td align="left" valign="top"><a name="id2564268"></a><a name="id2564270"></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 @@ -745,7 +745,7 @@ smb: \> 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" title="5."><td align="left" valign="top"><a name="id2564307"></a><a name="id2564309"></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> @@ -754,25 +754,25 @@ smb: \> 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" title="6."><td align="left" valign="top"><a name="id2564346"></a><a name="id2564348"></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" title="7."><td align="left" valign="top"><a name="id2564382"></a><a name="id2564385"></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. - </p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p> + </p><div class="procedure"><ol type="1"><li><p> Back up your existing configuration files in case you need to restore them. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Rename the <code class="filename">group_mapping.tdb</code> file. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Use the <code class="literal">smbpasswd</code> to add the root account. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Restore the <code class="filename">group_mapping.tdb</code> file. - </p></li></ol></div></td></tr><tr class="question" title="8."><td align="left" valign="top"><a name="id2564450"></a><a name="id2564452"></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> @@ -780,7 +780,7 @@ smb: \> 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" title="9."><td align="left" valign="top"><a name="id2564494"></a><a name="id2564497"></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>, @@ -792,7 +792,7 @@ smb: \> 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" title="10."><td align="left" valign="top"><a name="id2564544"></a><a name="id2564546"></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 4ea328ddbf..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.75.2"><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" title="Chapter 7. Adding Domain Member Servers and Clients"><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#id2595324">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2595378">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2595413">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2595441">Technical Issues</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596090">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2596190">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#id2602396">UNIX/Linux Client Domain Member</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2602971">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2603025">Questions and Answers</a></span></dt></dl></div><p><a class="indexterm" name="id2595226"></a><a class="indexterm" name="id2595233"></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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2595324"></a>Introduction</h2></div></div></div><p><a class="indexterm" name="id2595330"></a><a class="indexterm" name="id2595338"></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="id2595359"></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" title="Assignment Tasks"><div class="titlepage"><div><div><h3 class="title"><a name="id2595378"></a>Assignment Tasks</h3></div></div></div><p><a class="indexterm" name="id2595384"></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" title="Dissection and Discussion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2595413"></a>Dissection and Discussion</h2></div></div></div><p> - <a class="indexterm" name="id2595421"></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,57 +39,57 @@ 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" title="Technical Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2595441"></a>Technical Issues</h3></div></div></div><p> - One of the great challenges we face when people ask us, <span class="quote">“<span class="quote">What is the best way to solve - this problem?</span>”</span> is to get beyond the facts so we not only can clearly comprehend + </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, “<span class="quote">What is the best way to solve + this problem?</span>” 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="id2595460"></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 class="itemizedlist" type="disc"><li class="listitem"><p> - <a class="indexterm" name="id2595476"></a> - <a class="indexterm" name="id2595483"></a> - <a class="indexterm" name="id2595490"></a> - <a class="indexterm" name="id2595499"></a> - <a class="indexterm" name="id2595506"></a> + </p><div class="itemizedlist"><ul type="disc"><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2595521"></a> - <a class="indexterm" name="id2595528"></a> - <a class="indexterm" name="id2595540"></a> - <a class="indexterm" name="id2595547"></a> + </p></li><li><p> + <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 from the domain in which that user's account resides. It must then map that ID to a UID/GID pair that it can use locally. This is handled by <code class="literal">winbindd</code>. - </p></li><li class="listitem"><p> + </p></li><li><p> Samba, when running on a domain member server, can resolve user identities from a number of sources: - </p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p> - <a class="indexterm" name="id2595579"></a> - <a class="indexterm" name="id2595586"></a> - <a class="indexterm" name="id2595593"></a> - <a class="indexterm" name="id2595599"></a> - <a class="indexterm" name="id2595606"></a> + </p><div class="itemizedlist"><ul type="circle"><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2595639"></a> - <a class="indexterm" name="id2595646"></a> - <a class="indexterm" name="id2595653"></a> + </p></li><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2595667"></a> - <a class="indexterm" name="id2595674"></a> - <a class="indexterm" name="id2595680"></a> - <a class="indexterm" name="id2595687"></a> + </p></li><li><p> + <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="id2595727"></a> - <a class="indexterm" name="id2595734"></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. @@ -110,38 +110,38 @@ Which of the resolver methods is chosen is determined by the way that Samba is configured 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 class="listitem"><p> - <a class="indexterm" name="id2595799"></a> - <a class="indexterm" name="id2595806"></a> - <a class="indexterm" name="id2595816"></a> + </p></li><li><p> + <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="id2595851"></a> - <a class="indexterm" name="id2595858"></a> - <a class="indexterm" name="id2595865"></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="id2595880"></a> - <a class="indexterm" name="id2595886"></a> - <a class="indexterm" name="id2595893"></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="id2595916"></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="id2595953"></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="id2596004"></a> - <a class="indexterm" name="id2596011"></a> - <a class="indexterm" name="id2596020"></a> - <a class="indexterm" name="id2596027"></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="id2596075"></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" title="Political Issues"><div class="titlepage"><div><div><h3 class="title"><a name="id2596090"></a>Political Issues</h3></div></div></div><p> - <a class="indexterm" name="id2596098"></a> - <a class="indexterm" name="id2596105"></a> - <a class="indexterm" name="id2596111"></a> - <a class="indexterm" name="id2596120"></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="id2596159"></a> - <a class="indexterm" name="id2596165"></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" title="Implementation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2596190"></a>Implementation</h2></div></div></div><p> - <a class="indexterm" name="id2596198"></a> - <a class="indexterm" name="id2596208"></a> - <a class="indexterm" name="id2596217"></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="id2596233"></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="id2596255"></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="id2596271"></a> - <a class="indexterm" name="id2596278"></a> - <a class="indexterm" name="id2596285"></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. @@ -225,13 +225,13 @@ </p><p> 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" title="Samba Domain with Samba Domain Member Server Using NSS LDAP"><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="id2596326"></a> - <a class="indexterm" name="id2596332"></a> - <a class="indexterm" name="id2596339"></a> - <a class="indexterm" name="id2596346"></a> - <a class="indexterm" name="id2596355"></a> - <a class="indexterm" name="id2596362"></a> + </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="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="id2596426"></a> - <a class="indexterm" name="id2596433"></a> - <a class="indexterm" name="id2596440"></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. @@ -258,38 +258,38 @@ user and group account information. The POSIX information is usually obtained using the <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 class="itemizedlist" type="disc"><li class="listitem"><p> - <a class="indexterm" name="id2596477"></a> - <a class="indexterm" name="id2596484"></a> + </p><div class="itemizedlist"><ul type="disc"><li><p> + <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 class="listitem"><p> - <a class="indexterm" name="id2596507"></a> - <a class="indexterm" name="id2596514"></a> - <a class="indexterm" name="id2596520"></a> - <a class="indexterm" name="id2596527"></a> - <a class="indexterm" name="id2596534"></a> - <a class="indexterm" name="id2596540"></a> - <a class="indexterm" name="id2596547"></a> - <a class="indexterm" name="id2596554"></a> - <a class="indexterm" name="id2596561"></a> + </p></li><li><p> + <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>, <code class="literal">nis</code>, <code class="literal">nisplus</code>, <code class="literal">hesiod.</code> When correctly installed, Samba adds to this list the <code class="literal">winbindd</code> facility. The ldap facility is frequently the nss_ldap tool provided by PADL Software. - </p></li></ul></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> To advoid confusion the use of the term <code class="literal">local passdb backend</code> means that 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="id2596640"></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">“Samba Domain: Samba Member Server”</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="id2596702"></a> - <a class="indexterm" name="id2596709"></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 @@ -300,11 +300,11 @@ The instructions given here apply to the Samba environment shown in <a class="link" href="happy.html" title="Chapter 5. Making Happy Users">“Making Happy Users”</a> and <a class="link" href="2000users.html" title="Chapter 6. A Distributed 2000-User Network">“A Distributed 2000-User Network”</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">“Making Happy Users”</a> configuration), change the target LDAP server from <code class="constant">lapdc</code> to <code class="constant">massive.</code> - </p><div class="procedure" title="Procedure 7.1. Configuration of NSS_LDAP-Based Identity Resolution"><a name="id2596757"></a><p class="title"><b>Procedure 7.1. Configuration of NSS_LDAP-Based Identity Resolution</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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">“Samba Domain Member in Samba Domain Using LDAP smb.conf File”</a>. Locate this file in the directory <code class="filename">/etc/samba</code>. - </p></li><li class="step" title="Step 2"><p> - <a class="indexterm" name="id2596795"></a> + </p></li><li><p> + <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 @@ -322,12 +322,12 @@ <code class="prompt">root# </code> strings /lib/libnss_ldap* | grep ldap.conf /etc/ldap.conf </pre><p> - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> 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">“NSS using LDAP for Identity Resolution File: /etc/nsswitch.conf”</a>. - </p></li><li class="step" title="Step 4"><p> - <a class="indexterm" name="id2596883"></a> - <a class="indexterm" name="id2596890"></a> + </p></li><li><p> + <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="id2596954"></a> - <a class="indexterm" name="id2596961"></a> - <a class="indexterm" name="id2596968"></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 @@ -373,8 +373,8 @@ sammy:x:4321: doubling up of group memberships and may cause problems with winbind under certain conditions. It is intended that these limitations with winbind will be resolved soon after Samba-3.0.20 has been released. - </p></li><li class="step" title="Step 5"><p> - <a class="indexterm" name="id2596992"></a> + </p></li><li><p> + <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="id2597014"></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">“LDIF IDMAP Add-On Load File File: /etc/openldap/idmap.LDIF”</a>). You can add the required entries using the following command: @@ -391,16 +391,16 @@ ou: idmap <code class="prompt">root# </code> ldapadd -x -D "cn=Manager,dc=abmas,dc=biz" \ -w not24get < /etc/openldap/idmap.LDIF </pre><p> - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> Samba automatically populates the LDAP directory container when it needs to. To permit Samba write access to the LDAP directory it is necessary to set the LDAP administrative password in the <code class="filename">secrets.tdb</code> file as shown here: </p><pre class="screen"> <code class="prompt">root# </code> smbpasswd -w not24get </pre><p> - </p></li><li class="step" title="Step 7"><p> - <a class="indexterm" name="id2597078"></a> - <a class="indexterm" name="id2597090"></a> + </p></li><li><p> + <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 @@ -411,17 +411,17 @@ Joined domain MEGANET2. Failure to join the domain could be caused by any number of variables. The most common causes of failure to join are: </p><p> - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Broken resolution of NetBIOS names to the respective IP address.</p></li><li class="listitem"><p>Incorrect username and password credentials.</p></li><li class="listitem"><p>The NT4 <em class="parameter"><code>restrict anonymous</code></em> is set to exclude anonymous + </p><div class="itemizedlist"><ul type="disc"><li><p>Broken resolution of NetBIOS names to the respective IP address.</p></li><li><p>Incorrect username and password credentials.</p></li><li><p>The NT4 <em class="parameter"><code>restrict anonymous</code></em> is set to exclude anonymous connections.</p></li></ul></div><p> </p><p> The connection setup can be diagnosed by executing: </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="id2597162"></a> - <a class="indexterm" name="id2597168"></a> - <a class="indexterm" name="id2597175"></a> - <a class="indexterm" name="id2597182"></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 @@ -448,8 +448,8 @@ Join to 'MEGANET2' is OK NT_STATUS_ACCESS_DENIED Join to 'MEGANET2' failed. </pre><p> - </p></li><li class="step" title="Step 8"><p> - <a class="indexterm" name="id2597243"></a> + </p></li><li><p> + <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: @@ -457,10 +457,10 @@ Join to 'MEGANET2' failed. <code class="prompt">root# </code> wbinfo --set-auth-user=Administrator%not24get </pre><p> The configuration is now ready to obtain the Samba domain user and group information. - </p></li><li class="step" title="Step 9"><p> + </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 border="0" summary="Simple list" class="simplelist"><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="id2597321"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2597333"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2597345"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id2597356"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2597368"></a><em class="parameter"><code>log level = 10</code></em></td></tr><tr><td><a class="indexterm" name="id2597380"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2597391"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2597403"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2597415"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2597427"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2597439"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2597451"></a><em class="parameter"><code>wins server = 192.168.2.1</code></em></td></tr><tr><td><a class="indexterm" name="id2597462"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2597474"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2597486"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2597498"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2597510"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2597522"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2597534"></a><em class="parameter"><code>idmap backend = ldap:ldap://lapdc.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2597546"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2597558"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2597570"></a><em class="parameter"><code>winbind trusted domains only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2597582"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td><a class="indexterm" name="id2597594"></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="id2597615"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2597626"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2597638"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2597650"></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="id2597670"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2597682"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2597694"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2597705"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2597717"></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="id2597737"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2597749"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2597761"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2597773"></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 @@ -497,28 +497,28 @@ publickey: files bootparams: files automount: files aliases: files -</pre></div></div><br class="example-break"></div><div class="sect2" title="NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind"><div class="titlepage"><div><div><h3 class="title"><a name="wdcsdm"></a>NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</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="wdcsdm"></a>NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</h3></div></div></div><p> You need to use this method for creating a Samba domain member server if any of the following conditions prevail: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> LDAP support (client) is not installed on the system. - </p></li><li class="listitem"><p> + </p></li><li><p> There are mitigating circumstances forcing a decision not to use LDAP. - </p></li><li class="listitem"><p> + </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="id2597904"></a> - <a class="indexterm" name="id2597910"></a> - <a class="indexterm" name="id2597917"></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" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - <a class="indexterm" name="id2597933"></a> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + <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="id2597950"></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="id2597987"></a> - <a class="indexterm" name="id2597994"></a> - <a class="indexterm" name="id2598000"></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="id2598019"></a> - <a class="indexterm" name="id2598026"></a> - <a class="indexterm" name="id2598033"></a> - <a class="indexterm" name="id2598040"></a> - <a class="indexterm" name="id2598049"></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" title="Procedure 7.2. Configuration of Winbind-Based Identity Resolution"><a name="id2598078"></a><p class="title"><b>Procedure 7.2. Configuration of Winbind-Based Identity Resolution</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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">“Samba Domain Member Server Using Winbind smb.conf File for NT4 Domain”</a>. - </p></li><li class="step" title="Step 2"><p> - <a class="indexterm" name="id2598110"></a> + </p></li><li><p> + <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">“NSS using LDAP for Identity Resolution File: /etc/nsswitch.conf”</a>. - </p></li><li class="step" title="Step 3"><p> - <a class="indexterm" name="id2598136"></a> + </p></li><li><p> + <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 @@ -559,9 +559,9 @@ Joined domain MEGANET2. </pre><p> This indicates that the domain join succeed. - </p></li><li class="step" title="Step 4"><p> - <a class="indexterm" name="id2598163"></a> - <a class="indexterm" name="id2598169"></a> + </p></li><li><p> + <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"> @@ -587,10 +587,10 @@ MEGANET2+Finances MEGANET2+PIOps </pre><p> This shows that domain groups have been correctly obtained also. - </p></li><li class="step" title="Step 5"><p> - <a class="indexterm" name="id2598226"></a> - <a class="indexterm" name="id2598232"></a> - <a class="indexterm" name="id2598239"></a> + </p></li><li><p> + <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"> @@ -629,9 +629,9 @@ MEGANET2+Accounts:x:10003: MEGANET2+Finances:x:10004: MEGANET2+PIOps:x:10005: </pre><p> - </p></li><li class="step" title="Step 6"><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 border="0" summary="Simple list" class="simplelist"><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="id2598350"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2598362"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2598373"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id2598385"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2598397"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2598409"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2598420"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2598432"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2598444"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2598455"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2598467"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2598479"></a><em class="parameter"><code>wins server = 192.168.2.1</code></em></td></tr><tr><td><a class="indexterm" name="id2598491"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2598503"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2598514"></a><em class="parameter"><code>template primary group = "Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id2598527"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2598539"></a><em class="parameter"><code>winbind separator = +</code></em></td></tr><tr><td><a class="indexterm" name="id2598550"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td><a class="indexterm" name="id2598562"></a><em class="parameter"><code>hosts allow = 192.168.2., 192.168.3., 127.</code></em></td></tr><tr><td><a class="indexterm" name="id2598574"></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="id2598595"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2598607"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2598618"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2598630"></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="id2598650"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2598662"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2598674"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2598685"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2598697"></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="id2598718"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2598729"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2598741"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2598753"></a><em class="parameter"><code>write list = root</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" title="NT4/Samba Domain with Samba Domain Member Server without NSS Support"><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,24 +642,24 @@ 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" title="Procedure 7.3. Configuration Using Local Accounts Only"><a name="id2598796"></a><p class="title"><b>Procedure 7.3. Configuration Using Local Accounts Only</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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">“Samba Domain Member Server Using Local Accounts smb.conf File for NT4 Domain”</a>. - </p></li><li class="step" title="Step 2"><p><a class="indexterm" name="id2598829"></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 Joined domain MEGANET2. </pre><p> This indicates that the domain join succeed. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> 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 class="step" title="Step 4"><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-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 border="0" summary="Simple list" class="simplelist"><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="id2598918"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2598930"></a><em class="parameter"><code>workgroup = MEGANET3</code></em></td></tr><tr><td><a class="indexterm" name="id2598941"></a><em class="parameter"><code>netbios name = BSDBOX</code></em></td></tr><tr><td><a class="indexterm" name="id2598953"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id2598965"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2598977"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2598988"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2599000"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2599012"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -M '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2599024"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2599036"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2599048"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2599060"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2599072"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2599084"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2599096"></a><em class="parameter"><code>wins server = 192.168.2.1</code></em></td></tr><tr><td><a class="indexterm" name="id2599107"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td><a class="indexterm" name="id2599119"></a><em class="parameter"><code>hosts allow = 192.168.2., 192.168.3., 127.</code></em></td></tr><tr><td><a class="indexterm" name="id2599131"></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="id2599152"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2599163"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2599175"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2599187"></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="id2599207"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2599219"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2599231"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2599242"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2599254"></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="id2599274"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2599286"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2599298"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2599310"></a><em class="parameter"><code>write list = root</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" title="Active Directory Domain with Samba Domain Member Server"><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="id2599335"></a> - <a class="indexterm" name="id2599344"></a> - <a class="indexterm" name="id2599351"></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="id2599373"></a> - <a class="indexterm" name="id2599380"></a> - <a class="indexterm" name="id2599387"></a> - <a class="indexterm" name="id2599394"></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">“Active Directory Domain: Samba Member Server”</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" title="Procedure 7.4. Joining a Samba Server as an ADS Domain Member"><a name="id2599507"></a><p class="title"><b>Procedure 7.4. Joining a Samba Server as an ADS Domain Member</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2599519"></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: @@ -761,16 +761,16 @@ massive:/usr/sbin # smbd -b | grep LDAP </pre><p> 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 class="step" title="Step 2"><p> - <a class="indexterm" name="id2599618"></a> - <a class="indexterm" name="id2599627"></a> - <a class="indexterm" name="id2599634"></a> - <a class="indexterm" name="id2599641"></a> - <a class="indexterm" name="id2599650"></a> - <a class="indexterm" name="id2599659"></a> - <a class="indexterm" name="id2599666"></a> - <a class="indexterm" name="id2599673"></a> - <a class="indexterm" name="id2599680"></a> + </p></li><li><p> + <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, @@ -791,25 +791,25 @@ massive:/usr/sbin # smbd -b | grep LDAP </p><p> From this point on, you are certain that the Samba-3 build you are using has the necessary capabilities. You can now configure Samba-3 and the NSS. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Using you favorite editor, configure the <code class="filename">smb.conf</code> file that is located in the <code class="filename">/etc/samba</code> directory so that it has the contents shown in <a class="link" href="unixclients.html#ch9-adssdm" title="Example 7.7. Samba Domain Member smb.conf File for Active Directory Membership">“Samba Domain Member smb.conf File for Active Directory Membership”</a>. - </p></li><li class="step" title="Step 4"><p> + </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">“NSS using LDAP for Identity Resolution File: /etc/nsswitch.conf”</a>. - </p></li><li class="step" title="Step 5"><p> - <a class="indexterm" name="id2599782"></a> + </p></li><li><p> + <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 class="step" title="Step 6"><p> + </p></li><li><p> Delete the tdb files that cache Samba information. You keep a backup of the old files, of course. You also remove all files to ensure that nothing can pollute your nice, new configuration. Execute the following (example is for SUSE Linux): </p><pre class="screen"> <code class="prompt">root# </code> rm /var/lib/samba/*tdb </pre><p> - </p></li><li class="step" title="Step 7"><p> - <a class="indexterm" name="id2599826"></a> + </p></li><li><p> + <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: @@ -818,9 +818,9 @@ massive:/usr/sbin # smbd -b | grep LDAP </pre><p> Now that you are satisfied that your Samba server is ready to join the Windows ADS domain, let's move on. - </p></li><li class="step" title="Step 8"><p> - <a class="indexterm" name="id2599867"></a> - <a class="indexterm" name="id2599878"></a> + </p></li><li><p> + <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,38 +831,38 @@ 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="id2599906"></a> - <a class="indexterm" name="id2599913"></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 class="itemizedlist" type="disc"><li class="listitem"><p> - <a class="indexterm" name="id2599935"></a> + </p><div class="itemizedlist"><ul type="disc"><li><p> + <a class="indexterm" name="id2593850"></a> Defective or misconfigured DNS name resolution. - </p></li><li class="listitem"><p> - <a class="indexterm" name="id2599949"></a> + </p></li><li><p> + <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. - </p></li><li class="listitem"><p> + </p></li><li><p> Incorrectly configured <code class="filename">smb.conf</code> file settings. - </p></li><li class="listitem"><p> + </p></li><li><p> Lack of support of necessary Kerberos protocols because the version of MIT Kerberos (or Heimdal) in use is not up to date enough to support the necessary functionality. </p></li></ul></div><p> - <a class="indexterm" name="id2599980"></a> - <a class="indexterm" name="id2599991"></a> - <a class="indexterm" name="id2599998"></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 class="step" title="Step 9"><p> - <a class="indexterm" name="id2600023"></a> - <a class="indexterm" name="id2600030"></a> + </p></li><li><p> + <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: @@ -889,11 +889,11 @@ data = "E\89\F6?" } </pre><p> This is given to demonstrate to the skeptics that this process truly does work. - </p></li><li class="step" title="Step 10"><p> + </p></li><li><p> It is now time to start Samba in the usual way (as has been done many time before in this book). - </p></li><li class="step" title="Step 11"><p> - <a class="indexterm" name="id2600087"></a> + </p></li><li><p> + <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 class="step" title="Step 12"><p><a class="indexterm" name="id2600133"></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"> @@ -951,10 +951,10 @@ LONDON+Group Policy Creator Owners:x:10007:LONDON+Administrator LONDON+DnsUpdateProxy:x:10008: </pre><p> This is very pleasing. Everything works as expected. - </p></li><li class="step" title="Step 13"><p> - <a class="indexterm" name="id2600191"></a> - <a class="indexterm" name="id2600202"></a> - <a class="indexterm" name="id2600211"></a> + </p></li><li><p> + <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"> @@ -971,8 +971,8 @@ Server time offset: 2 It should be noted that Kerberos protocols are time-clock critical. You should 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 class="step" title="Step 14"><p> - <a class="indexterm" name="id2600247"></a> + </p></li><li><p> + <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,40 +1142,40 @@ 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 border="0" summary="Simple list" class="simplelist"><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="id2600468"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2600480"></a><em class="parameter"><code>workgroup = LONDON</code></em></td></tr><tr><td><a class="indexterm" name="id2600492"></a><em class="parameter"><code>realm = LONDON.ABMAS.BIZ</code></em></td></tr><tr><td><a class="indexterm" name="id2600503"></a><em class="parameter"><code>server string = Samba 3.0.20</code></em></td></tr><tr><td><a class="indexterm" name="id2600515"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2600527"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2600539"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2600551"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2600562"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2600574"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2600586"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2600598"></a><em class="parameter"><code>ldap ssl = no</code></em></td></tr><tr><td><a class="indexterm" name="id2600609"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2600621"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2600633"></a><em class="parameter"><code>template primary group = "Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id2600645"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2600657"></a><em class="parameter"><code>winbind separator = +</code></em></td></tr><tr><td><a class="indexterm" name="id2600669"></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="id2600689"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2600701"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2600712"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2600724"></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="id2600745"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2600756"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2600768"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2600780"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2600791"></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="id2600812"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2600824"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2600835"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2600847"></a><em class="parameter"><code>write list = root</code></em></td></tr></table></div></div><br class="example-break"><div class="sect3" title="IDMAP_RID with Winbind"><div class="titlepage"><div><div><h4 class="title"><a name="id2600860"></a>IDMAP_RID with Winbind</h4></div></div></div><p> - <a class="indexterm" name="id2600868"></a> - <a class="indexterm" name="id2600875"></a> - <a class="indexterm" name="id2600881"></a> - <a class="indexterm" name="id2600888"></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="id2600912"></a> - <a class="indexterm" name="id2600918"></a> - <a class="indexterm" name="id2600925"></a> - <a class="indexterm" name="id2600932"></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 - <span class="quote">“<span class="quote">allow trusted domains = No</span>”</span> must be specified, as it is not compatible + “<span class="quote">allow trusted domains = No</span>” must be specified, as it is not compatible 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="id2600965"></a> - <a class="indexterm" name="id2600972"></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">“Example smb.conf File Using idmap_rid”</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 border="0" summary="Simple list" class="simplelist"><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="id2601046"></a><em class="parameter"><code>workgroup = KPAK</code></em></td></tr><tr><td><a class="indexterm" name="id2601058"></a><em class="parameter"><code>netbios name = BIGJOE</code></em></td></tr><tr><td><a class="indexterm" name="id2601070"></a><em class="parameter"><code>realm = CORP.KPAK.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2601081"></a><em class="parameter"><code>server string = Office Server</code></em></td></tr><tr><td><a class="indexterm" name="id2601093"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2601105"></a><em class="parameter"><code>allow trusted domains = No</code></em></td></tr><tr><td><a class="indexterm" name="id2601117"></a><em class="parameter"><code>idmap backend = idmap_rid:KPAK=500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2601129"></a><em class="parameter"><code>idmap uid = 500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2601141"></a><em class="parameter"><code>idmap gid = 500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2601153"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2601164"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2601177"></a><em class="parameter"><code>winbind enum users = No</code></em></td></tr><tr><td><a class="indexterm" name="id2601188"></a><em class="parameter"><code>winbind enum groups = No</code></em></td></tr><tr><td><a class="indexterm" name="id2601200"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2601212"></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="id2601228"></a> - <a class="indexterm" name="id2601235"></a> - <a class="indexterm" name="id2601242"></a> - <a class="indexterm" name="id2601248"></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="id2601287"></a> - <a class="indexterm" name="id2601294"></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"> @@ -1200,11 +1200,11 @@ hosts: files wins </pre><p> </p><p> The following procedure can be used to utilize the idmap_rid facility: - </p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p> + </p><div class="procedure"><ol type="1"><li><p> Create or install and <code class="filename">smb.conf</code> file with the above configuration. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Edit the <code class="filename">/etc/nsswitch.conf</code> file as shown above. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Execute: </p><pre class="screen"> <code class="prompt">root# </code> net ads join -UAdministrator%password @@ -1212,7 +1212,7 @@ Using short domain name -- KPAK Joined 'BIGJOE' to realm 'CORP.KPAK.COM' </pre><p> </p><p> - <a class="indexterm" name="id2601375"></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 @@ -1224,34 +1224,34 @@ Join to domain is not valid 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 above test, and then examine the log files produced to identify the nature of the failure. - </p></li><li class="step" title="Step 4"><p> + </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><li class="step" title="Step 5"><p> + </p></li><li><p> Validate the operation of this configuration by executing: - <a class="indexterm" name="id2601442"></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" title="IDMAP Storage in LDAP using Winbind"><div class="titlepage"><div><div><h4 class="title"><a name="id2601464"></a>IDMAP Storage in LDAP using Winbind</h4></div></div></div><p> - <a class="indexterm" name="id2601472"></a> - <a class="indexterm" name="id2601479"></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">“Typical ADS Style Domain smb.conf File”</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 border="0" summary="Simple list" class="simplelist"><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="id2601539"></a><em class="parameter"><code>workgroup = SNOWSHOW</code></em></td></tr><tr><td><a class="indexterm" name="id2601551"></a><em class="parameter"><code>netbios name = GOODELF</code></em></td></tr><tr><td><a class="indexterm" name="id2601563"></a><em class="parameter"><code>realm = SNOWSHOW.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2601574"></a><em class="parameter"><code>server string = Samba Server</code></em></td></tr><tr><td><a class="indexterm" name="id2601586"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2601598"></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="id2601610"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=SNOWSHOW,dc=COM</code></em></td></tr><tr><td><a class="indexterm" name="id2601622"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2601634"></a><em class="parameter"><code>ldap suffix = dc=SNOWSHOW,dc=COM</code></em></td></tr><tr><td><a class="indexterm" name="id2601646"></a><em class="parameter"><code>idmap backend = ldap:ldap://ldap.snowshow.com</code></em></td></tr><tr><td><a class="indexterm" name="id2601658"></a><em class="parameter"><code>idmap uid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2601670"></a><em class="parameter"><code>idmap gid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2601682"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2601694"></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="id2601709"></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 - <span class="quote">“<span class="quote">The Official Samba-3 HOWTO and Reference Guide, Second Edition</span>”</span> (TOSHARG2). + “<span class="quote">The Official Samba-3 HOWTO and Reference Guide, Second Edition</span>” (TOSHARG2). </p><p> - <a class="indexterm" name="id2601740"></a> - <a class="indexterm" name="id2601747"></a> - <a class="indexterm" name="id2601754"></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"> @@ -1290,7 +1290,7 @@ administrator:x:1000:1013:Administrator:/home/BE/administrator:/bin/bash [domain_realm] .snowshow.com = SNOWSHOW.COM </pre><p> - </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Samba cannot use the Heimdal libraries if there is no <code class="filename">/etc/krb5.conf</code> file. So long as there is an empty file, the Heimdal kerberos libraries will be usable. There is no need to specify any settings because Samba, using the Heimdal libraries, can figure this out automatically. @@ -1306,8 +1306,8 @@ hosts: files wins ... </pre><p> </p><p> - <a class="indexterm" name="id2601838"></a> - <a class="indexterm" name="id2601845"></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: @@ -1326,16 +1326,16 @@ ssl no </pre><p> </p><p> The following procedure may be followed to affect a working configuration: - </p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p> + </p><div class="procedure"><ol type="1"><li><p> Configure the <code class="filename">smb.conf</code> file as shown above. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Create the <code class="filename">/etc/krb5.conf</code> file following the indications above. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Configure the <code class="filename">/etc/nsswitch.conf</code> file as shown above. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Download, build, and install the PADL nss_ldap tool set. Configure the <code class="filename">/etc/ldap.conf</code> file as shown above. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> Configure an LDAP server and initialize the directory with the top-level entries needed by IDMAP as shown in the following LDIF file: </p><pre class="screen"> @@ -1355,35 +1355,35 @@ dn: ou=Idmap,dc=snowshow,dc=com objectClass: organizationalUnit ou: idmap </pre><p> - </p></li><li class="step" title="Step 6"><p> + </p></li><li><p> Execute the command to join the Samba domain member server to the ADS domain as shown here: </p><pre class="screen"> <code class="prompt">root# </code> net ads testjoin Using short domain name -- SNOWSHOW Joined 'GOODELF' to realm 'SNOWSHOW.COM' </pre><p> - </p></li><li class="step" title="Step 7"><p> + </p></li><li><p> Store the LDAP server access password in the Samba <code class="filename">secrets.tdb</code> file as follows: </p><pre class="screen"> <code class="prompt">root# </code> smbpasswd -w not24get </pre><p> - </p></li><li class="step" title="Step 8"><p> + </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="id2602046"></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" title="IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension"><div class="titlepage"><div><div><h4 class="title"><a name="id2602059"></a>IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</h4></div></div></div><p> - <a class="indexterm" name="id2602068"></a> - <a class="indexterm" name="id2602075"></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">“ADS Membership Using RFC2307bis Identity Resolution smb.conf File”</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 border="0" summary="Simple list" class="simplelist"><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="id2602138"></a><em class="parameter"><code>workgroup = BUBBAH</code></em></td></tr><tr><td><a class="indexterm" name="id2602149"></a><em class="parameter"><code>netbios name = MADMAX</code></em></td></tr><tr><td><a class="indexterm" name="id2602161"></a><em class="parameter"><code>realm = BUBBAH.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2602173"></a><em class="parameter"><code>server string = Samba Server</code></em></td></tr><tr><td><a class="indexterm" name="id2602185"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2602196"></a><em class="parameter"><code>idmap uid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2602208"></a><em class="parameter"><code>idmap gid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2602220"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2602232"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2602244"></a><em class="parameter"><code>winbind trusted domains only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2602256"></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="id2602271"></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="id2602292"></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,52 +1404,52 @@ hosts: files wins ... </pre><p> </p><p> - <a class="indexterm" name="id2602316"></a> - <a class="indexterm" name="id2602323"></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" title="IDMAP, Active Directory, and MS Services for UNIX 3.5"><div class="titlepage"><div><div><h5 class="title"><a name="id2602345"></a>IDMAP, Active Directory, and MS Services for UNIX 3.5</h5></div></div></div><p> - <a class="indexterm" name="id2602354"></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" title="IDMAP, Active Directory, and AD4UNIX"><div class="titlepage"><div><div><h5 class="title"><a name="id2602374"></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" title="UNIX/Linux Client Domain Member"><div class="titlepage"><div><div><h3 class="title"><a name="id2602396"></a>UNIX/Linux Client Domain Member</h3></div></div></div><p><a class="indexterm" name="id2602403"></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="id2602422"></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: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> Proxy sign-on - </p></li><li class="listitem"><p> + </p></li><li><p> Federated directory provisioning - </p></li><li class="listitem"><p> + </p></li><li><p> Metadirectory server solutions - </p></li><li class="listitem"><p> + </p></li><li><p> Replacement authentication systems - </p></li></ul></div><p><a class="indexterm" name="id2602464"></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 class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> Samba winbind (free). Samba-3.0.20 introduced a complete replacement for Winbind that now provides a greater level of scalability in large ADS environments. - </p></li><li class="listitem"><p> + </p></li><li><p> <a class="ulink" href="http://www.padl.com" target="_top">PADL</a> PAM and LDAP tools (free). - </p></li><li class="listitem"><p> + </p></li><li><p> <a class="ulink" href="http://www.vintela.com" target="_top">Vintela</a> Authentication Services (commercial). - </p></li><li class="listitem"><p> + </p></li><li><p> <a class="ulink" href="http://www.centrify.com" target="_top">Centrify</a> DirectControl (commercial). Centrify's commercial product allows UNIX and Linux systems to use Active Directory security, directory and policy services. Enhancements include a centralized ID mapping that @@ -1464,75 +1464,75 @@ 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="id2602543"></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="id2602561"></a> - <a class="indexterm" name="id2602567"></a> - <a class="indexterm" name="id2602574"></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" title="NT4 Domain Member"><div class="titlepage"><div><div><h4 class="title"><a name="id2602597"></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 class="procedure" type="1"><li class="step" title="Step 1"><p> + </p><div class="procedure"><ol type="1"><li><p> Follow the steps outlined in <a class="link" href="unixclients.html#wdcsdm" title="NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind">“NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind”</a> and ensure that all validation tests function as shown. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Identify what services users must log on to. On Red Hat Linux, if it is intended that the user shall be given access to all services, it may be most expeditious to simply configure the file <code class="filename">/etc/pam.d/system-auth</code>. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Carefully make a backup copy of all PAM configuration files before you begin making changes. If you break the PAM configuration, please note that you may need to use an emergency boot process to recover your Linux system. It is possible to break the ability to log into the system if PAM files are incorrectly configured. The entire directory <code class="filename">/etc/pam.d</code> should be backed up to a safe location. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> If you require only console login support, edit the <code class="filename">/etc/pam.d/login</code> so it matches <a class="link" href="unixclients.html#ch9-pamwnbdlogin" title="Example 7.11. SUSE: PAM login Module Using Winbind">“SUSE: PAM login Module Using Winbind”</a>. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> To provide the ability to log onto the graphical desktop interface, you must edit the files <code class="filename">gdm</code> and <code class="filename">xdm</code> in the <code class="filename">/etc/pam.d</code> directory. - </p></li><li class="step" title="Step 6"><p> + </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" title="ADS Domain Member"><div class="titlepage"><div><div><h4 class="title"><a name="id2602719"></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 class="procedure" type="1"><li class="step" title="Step 1"><p> + </p><div class="procedure"><ol type="1"><li><p> Follow the steps outlined in <a class="link" href="unixclients.html#adssdm" title="Active Directory Domain with Samba Domain Member Server">“Active Directory Domain with Samba Domain Member Server”</a> and ensure that all validation tests function as shown. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Identify what services users must log on to. On Red Hat Linux, if it is intended that the user shall be given access to all services, it may be most expeditious to simply configure the file <code class="filename">/etc/pam.d/system-auth</code> as shown in <a class="link" href="unixclients.html#ch9-rhsysauth" title="Example 7.13. Red Hat 9: PAM System Authentication File: /etc/pam.d/system-auth Module Using Winbind">“Red Hat 9: PAM System Authentication File: /etc/pam.d/system-auth Module Using Winbind”</a>. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Carefully make a backup copy of all PAM configuration files before you begin making changes. If you break the PAM configuration, please note that you may need to use an emergency boot process to recover your Linux system. It is possible to break the ability to log into the system if PAM files are incorrectly configured. The entire directory <code class="filename">/etc/pam.d</code> should be backed up to a safe location. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> If you require only console login support, edit the <code class="filename">/etc/pam.d/login</code> so it matches <a class="link" href="unixclients.html#ch9-pamwnbdlogin" title="Example 7.11. SUSE: PAM login Module Using Winbind">“SUSE: PAM login Module Using Winbind”</a>. - </p></li><li class="step" title="Step 5"><p> + </p></li><li><p> To provide the ability to log onto the graphical desktop interface, you must edit the files <code class="filename">gdm</code> and <code class="filename">xdm</code> in the <code class="filename">/etc/pam.d</code> directory. - </p></li><li class="step" title="Step 6"><p> + </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="example"><a name="ch9-pamwnbdlogin"></a><p class="title"><b>Example 7.11. SUSE: PAM <code class="filename">login</code> Module Using Winbind</b></p><div class="example-contents"><pre class="screen"> @@ -1587,74 +1587,74 @@ 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" title="Key Points Learned"><div class="titlepage"><div><div><h3 class="title"><a name="id2602971"></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 or Windows domain account credentials to log on to a UNIX/Linux client. </p><p> The following are key points made in this chapter: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> Domain controllers are always authoritative for the domain. - </p></li><li class="listitem"><p> + </p></li><li><p> Domain members may have local accounts and must be able to resolve the identity of domain user accounts. Domain user account identity must map to a local UID/GID. That local UID/GID can be stored in LDAP. This way, it is possible to share the IDMAP data across all domain member machines. - </p></li><li class="listitem"><p> + </p></li><li><p> Resolution of user and group identities on domain member machines may be implemented using direct LDAP services or using winbind. - </p></li><li class="listitem"><p> + </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" title="Questions and Answers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2603025"></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" title="Frequently Asked Questions"><a name="id2603037"></a><dl><dt> <a href="unixclients.html#id2603043"> + </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#id2603158"> + </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#id2603242"> + </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#id2603353"> + </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#id2603481"> + </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#id2603656"> + </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#id2603840"> + </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#id2603998"> + </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#id2604016"> + </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" width="100%" summary="Q and A Set"><col align="left" width="1%"><col><tbody><tr class="question"><td align="left" valign="top"><a name="id2603043"></a><a name="id2603046"></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="id2603057"></a> - <a class="indexterm" name="id2603064"></a> - <a class="indexterm" name="id2603071"></a> - <a class="indexterm" name="id2603078"></a> - <a class="indexterm" name="id2603084"></a> - <a class="indexterm" name="id2603091"></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="id2603118"></a> - <a class="indexterm" name="id2603126"></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="id2603158"></a><a name="id2603160"></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="id2603167"></a> - </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2603181"></a><a class="indexterm" name="id2603192"></a><a class="indexterm" name="id2603200"></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="id2603220"></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="id2603242"></a><a name="id2603244"></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="id2603256"></a><a class="indexterm" name="id2603264"></a><a class="indexterm" name="id2603272"></a><a class="indexterm" name="id2603280"></a><a class="indexterm" name="id2603288"></a><a class="indexterm" name="id2603296"></a><a class="indexterm" name="id2603304"></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="id2603321"></a><a class="indexterm" name="id2603329"></a><a class="indexterm" name="id2603337"></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="id2603353"></a><a name="id2603355"></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="id2603367"></a><a class="indexterm" name="id2603375"></a><a class="indexterm" name="id2603386"></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="id2603411"></a><a class="indexterm" name="id2603419"></a><a class="indexterm" name="id2603427"></a><a class="indexterm" name="id2603435"></a><a class="indexterm" name="id2603442"></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,25 +1711,25 @@ 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="id2603465"></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="id2603481"></a><a name="id2603483"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2603486"></a><a class="indexterm" name="id2603494"></a><a class="indexterm" name="id2603506"></a><a class="indexterm" name="id2603514"></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="id2603547"></a><a class="indexterm" name="id2603555"></a><a class="indexterm" name="id2603562"></a><a class="indexterm" name="id2603570"></a><a class="indexterm" name="id2603578"></a><a class="indexterm" name="id2603586"></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, - <span class="quote">“<span class="quote">This parameter is designed to allow Samba servers that are members of a Samba-controlled + “<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 in the hosts primary domain. Therefore, the user <code class="constant">SAMBA\user1</code> would be 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>”</span> This clearly suggests that you are trying + of allocating a new UID for him or her.</span>” This clearly suggests that you are trying to use this parameter inappropriately. - </p><p><a class="indexterm" name="id2603628"></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="id2603656"></a><a name="id2603658"></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="id2603669"></a><a class="indexterm" name="id2603677"></a><a class="indexterm" name="id2603685"></a><a class="indexterm" name="id2603693"></a><a class="indexterm" name="id2603700"></a><a class="indexterm" name="id2603708"></a><a class="indexterm" name="id2603716"></a><a class="indexterm" name="id2603724"></a><a class="indexterm" name="id2603732"></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="id2603748"></a><a class="indexterm" name="id2603756"></a><a class="indexterm" name="id2603764"></a><a class="indexterm" name="id2603772"></a><a class="indexterm" name="id2603780"></a><a class="indexterm" name="id2603788"></a><a class="indexterm" name="id2603799"></a><a class="indexterm" name="id2603807"></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="id2603840"></a><a name="id2603842"></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="id2603853"></a><a class="indexterm" name="id2603865"></a><a class="indexterm" name="id2603876"></a><a class="indexterm" name="id2603884"></a><a class="indexterm" name="id2603892"></a><a class="indexterm" name="id2603899"></a><a class="indexterm" name="id2603907"></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="id2603962"></a><a class="indexterm" name="id2603970"></a><a class="indexterm" name="id2603978"></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="id2603998"></a><a name="id2604000"></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="id2604016"></a><a name="id2604018"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2604022"></a><a class="indexterm" name="id2604036"></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="id2604060"></a><a class="indexterm" name="id2604068"></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 e7e781e9ad..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.75.2"><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" title="Chapter 8. Updating Samba-3"><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#id2604185">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2604281">Cautions and Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2605610">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#id2605979">Applicable to All Samba 2.x to Samba-3 Upgrades</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2606312">Samba-2.x with LDAP Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2606494">Updating a Samba-3 Installation</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2606604">Samba-3 to Samba-3 Updates on the Same Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2606808">Migrating Samba-3 to a New Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2607222">Migration of Samba Accounts to Active Directory</a></span></dt></dl></dd></dl></div><p> -<a class="indexterm" name="id2604100"></a> -<a class="indexterm" name="id2604107"></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="id2604124"></a> -<a class="indexterm" name="id2604130"></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,22 +17,22 @@ 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="id2604152"></a> -I like the <span class="quote">“<span class="quote">net rpc vampire</span>”</span> on NT4, but that to my surprise does +<a class="indexterm" name="id2598067"></a> +I like the “<span class="quote">net rpc vampire</span>” 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="id2604173"></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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2604185"></a>Introduction</h2></div></div></div><p> -<a class="indexterm" name="id2604193"></a> -<a class="indexterm" name="id2604199"></a> -<a class="indexterm" name="id2604206"></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: <span class="quote">“<span class="quote">Anyone done this -before?</span>”</span> Many of us have upgraded and updated Samba without incident. +planning to make and followed with the question: “<span class="quote">Anyone done this +before?</span>” Many of us have upgraded and updated Samba without incident. Others have experienced much pain and user frustration. So it is to be hoped that the notes in this chapter will make a positive difference by assuring that someone will be saved a lot of discomfort. @@ -43,29 +43,29 @@ case it is necessary to revert to the old version. Even if you do not like 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" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> -<a class="indexterm" name="id2604237"></a> -<a class="indexterm" name="id2604244"></a> +</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> +<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="id2604259"></a> -<a class="indexterm" name="id2604266"></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" title="Cautions and Notes"><div class="titlepage"><div><div><h3 class="title"><a name="id2604281"></a>Cautions and Notes</h3></div></div></div><p> - Someone once said, <span class="quote">“<span class="quote">It is good to be sorry, but better never to need to be!</span>”</span> +</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, “<span class="quote">It is good to be sorry, but better never to need to be!</span>” These are wise words of advice to those contemplating a Samba upgrade or update. </p><p> - <a class="indexterm" name="id2604299"></a> - <a class="indexterm" name="id2604305"></a> - <a class="indexterm" name="id2604312"></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="id2604339"></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="id2604356"></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 @@ -86,17 +86,17 @@ caution was on the side of the victor. latest documentation to identify precisely how the new installation may need to be modified to preserve prior functionality. </p><p> - There is an old axiom that says, <span class="quote">“<span class="quote">The greater the volume of the documentation, + There is an old axiom that says, “<span class="quote">The greater the volume of the documentation, the greater the risk that noone will read it, but where there is no documentation, - noone can read it!</span>”</span> While true, some documentation is an evil necessity. + noone can read it!</span>” 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" title="Security Identifiers (SIDs)"><div class="titlepage"><div><div><h4 class="title"><a name="id2604385"></a>Security Identifiers (SIDs)</h4></div></div></div><p> - <a class="indexterm" name="id2604393"></a> - <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="id2604432"></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="id2604451"></a> - <a class="indexterm" name="id2604458"></a> - <a class="indexterm" name="id2604465"></a> - <a class="indexterm" name="id2604472"></a> - <a class="indexterm" name="id2604478"></a> - <a class="indexterm" name="id2604485"></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="id2604502"></a> - <a class="indexterm" name="id2604509"></a> - <a class="indexterm" name="id2604515"></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="id2604535"></a> - <a class="indexterm" name="id2604542"></a> - <a class="indexterm" name="id2604548"></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="id2604569"></a> - <a class="indexterm" name="id2604578"></a> - <a class="indexterm" name="id2604587"></a> - <a class="indexterm" name="id2604594"></a> + <a class="indexterm" name="id2598484"></a> + <a class="indexterm" name="id2598493"></a> + <a class="indexterm" name="id2598502"></a> + <a class="indexterm" name="id2598509"></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="id2604608"></a> - <a class="indexterm" name="id2604615"></a> - <a class="indexterm" name="id2604622"></a> - <a class="indexterm" name="id2604629"></a> - <a class="indexterm" name="id2604636"></a> - <a class="indexterm" name="id2604642"></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,31 +153,31 @@ 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="id2604692"></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. - </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> It is of paramount importance that the machine and domain SID be backed up so that in 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="id2604713"></a> - <a class="indexterm" name="id2604720"></a> - <a class="indexterm" name="id2604727"></a> - <a class="indexterm" name="id2604733"></a> - <a class="indexterm" name="id2604740"></a> - <a class="indexterm" name="id2604747"></a> - <a class="indexterm" name="id2604754"></a> - <a class="indexterm" name="id2604761"></a> - <a class="indexterm" name="id2604768"></a> - <a class="indexterm" name="id2604774"></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="id2604788"></a> - <a class="indexterm" name="id2604797"></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 > /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="id2604886"></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="id2604959"></a> - <a class="indexterm" name="id2604966"></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="id2605013"></a> - <a class="indexterm" name="id2605020"></a> - <a class="indexterm" name="id2605026"></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="id2605062"></a> - <a class="indexterm" name="id2605069"></a> - <a class="indexterm" name="id2605076"></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" title="Change of hostname"><div class="titlepage"><div><div><h4 class="title"><a name="id2605113"></a>Change of hostname</h4></div></div></div><p> - <a class="indexterm" name="id2605121"></a> - <a class="indexterm" name="id2605130"></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 @@ -273,26 +273,26 @@ Num local groups: 0 hostname was changed for one reason or another. Such a change will cause a new machine SID to be generated. If this happens on a domain controller, it will also change the domain SID. These SIDs can be updated (restored) using the procedure outlined previously. - </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 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" title="Change of Workgroup (Domain) Name"><div class="titlepage"><div><div><h4 class="title"><a name="id2605179"></a>Change of Workgroup (Domain) Name</h4></div></div></div><p> - <a class="indexterm" name="id2605187"></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="id2605212"></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" title="Location of config files"><div class="titlepage"><div><div><h4 class="title"><a name="sbeug1"></a>Location of config files</h4></div></div></div><p> + </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> The Samba-Team has maintained a constant default location for all Samba control files throughout the life of the project. People who have produced binary packages of Samba have varied the location of the Samba control files. This has led to some confusion for network administrators. </p><p> - <a class="indexterm" name="id2605243"></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="id2605290"></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="id2605320"></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="id2605378"></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="id2605415"></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" title="International Language Support"><div class="titlepage"><div><div><h4 class="title"><a name="id2605445"></a>International Language Support</h4></div></div></div><p> - <a class="indexterm" name="id2605453"></a> - <a class="indexterm" name="id2605460"></a> - <a class="indexterm" name="id2605467"></a> - <a class="indexterm" name="id2605474"></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="id2605488"></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="id2605505"></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="id2605519"></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" title="Updates and Changes in Idealx smbldap-tools"><div class="titlepage"><div><div><h4 class="title"><a name="id2605539"></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" title="Upgrading from Samba 1.x and 2.x to Samba-3"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2605610"></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 @@ -402,31 +402,31 @@ attempted without proper planning and preparation. There are two basic modes of use of Samba versions prior to Samba-3. The first does not use LDAP, the other does. Samba-1.9.x did not provide LDAP support. Samba-2.x could be compiled with LDAP support. -</p><div class="sect2" title="Samba 1.9.x and 2.x Versions Without LDAP"><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> +</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" title="Procedure 8.1. Upgrading from a Pre-Samba-3 Version"><a name="id2605648"></a><p class="title"><b>Procedure 8.1. Upgrading from a Pre-Samba-3 Version</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> - <a class="indexterm" name="id2605659"></a> - <a class="indexterm" name="id2605666"></a> - <a class="indexterm" name="id2605673"></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>, <code class="literal">nmbd</code>, and <code class="literal">winbindd</code>. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> Find the location of the Samba <code class="filename">smb.conf</code> file and back it up to a safe location. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Find the location of the <code class="filename">smbpasswd</code> file and back it up to a safe location. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Find the location of the <code class="filename">secrets.tdb</code> file and back it up to a safe location. - </p></li><li class="step" title="Step 5"><p> - <a class="indexterm" name="id2605754"></a> - <a class="indexterm" name="id2605761"></a> - <a class="indexterm" name="id2605768"></a> - <a class="indexterm" name="id2605775"></a> + </p></li><li><p> + <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 @@ -436,8 +436,8 @@ Samba-2.x could be compiled with LDAP support. Linux Standards Base specified location is now under the <code class="filename">/var/lib/samba</code> directory. Copy all the tdb files to a safe location. - </p></li><li class="step" title="Step 6"><p> - <a class="indexterm" name="id2605814"></a> + </p></li><li><p> + <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. @@ -446,17 +446,17 @@ Samba-2.x could be compiled with LDAP support. it is advisable either to delete the Samba old installation or to move it out of the way by renaming the directories that contain the Samba binary files. - </p></li><li class="step" title="Step 7"><p> + </p></li><li><p> When the Samba upgrade has been installed, the first step that should be completed is to identify the new target locations for the control files. Follow the steps shown in <a class="link" href="upgrades.html#sbeug1" title="Location of config files">“Location of config files”</a> to locate the correct directories to which each control file must be moved. - </p></li><li class="step" title="Step 8"><p> + </p></li><li><p> Do not change the hostname. - </p></li><li class="step" title="Step 9"><p> + </p></li><li><p> Do not change the workgroup name. - </p></li><li class="step" title="Step 10"><p> - <a class="indexterm" name="id2605869"></a> + </p></li><li><p> + <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 > smb.conf </pre><p> - <a class="indexterm" name="id2605926"></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 class="step" title="Step 11"><p> - <a class="indexterm" name="id2605948"></a> + </p></li><li><p> + <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" title="Applicable to All Samba 2.x to Samba-3 Upgrades"><div class="titlepage"><div><div><h3 class="title"><a name="id2605979"></a>Applicable to All Samba 2.x to Samba-3 Upgrades</h3></div></div></div><p> - <a class="indexterm" name="id2605987"></a> - <a class="indexterm" name="id2605994"></a> - <a class="indexterm" name="id2606000"></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="id2606015"></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">“Secure Office Networking”</a> through <a class="link" href="2000users.html" title="Chapter 6. A Distributed 2000-User Network">“A Distributed 2000-User Network”</a> in this book for examples of use of the new parameters shown here: - <a class="indexterm" name="id2606036"></a> - <a class="indexterm" name="id2606043"></a> - <a class="indexterm" name="id2606050"></a> - <a class="indexterm" name="id2606057"></a> - <a class="indexterm" name="id2606064"></a> - <a class="indexterm" name="id2606071"></a> - <a class="indexterm" name="id2606078"></a> - </p><p> - </p><table border="0" summary="Simple list" class="simplelist"><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="id2606130"></a> - <a class="indexterm" name="id2606137"></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="id2606161"></a> - <a class="indexterm" name="id2606168"></a> - <a class="indexterm" name="id2606175"></a> - <a class="indexterm" name="id2606182"></a> - <a class="indexterm" name="id2606188"></a> - <a class="indexterm" name="id2606195"></a> - <a class="indexterm" name="id2606202"></a> - <a class="indexterm" name="id2606209"></a> - <a class="indexterm" name="id2606216"></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="id2606276"></a> - <a class="indexterm" name="id2606283"></a> - <a class="indexterm" name="id2606290"></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" title="Samba-2.x with LDAP Support"><div class="titlepage"><div><div><h3 class="title"><a name="id2606312"></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">“Samba 1.9.x and 2.x Versions Without LDAP”</a> to affect a migration of all files to the correct locations. </p><p> - <a class="indexterm" name="id2606347"></a> - <a class="indexterm" name="id2606353"></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" title="Updating a Samba-3 Installation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2606494"></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="id2606510"></a> +<a class="indexterm" name="id2600425"></a> The information in <a class="link" href="upgrades.html#sbeug1" title="Location of config files">“Location of config files”</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="id2606536"></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="id2606569"></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="id2606584"></a> -<a class="indexterm" name="id2606591"></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" title="Samba-3 to Samba-3 Updates on the Same Server"><div class="titlepage"><div><div><h3 class="title"><a name="id2606604"></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" title="Updating from Samba Versions Earlier than 3.0.5"><div class="titlepage"><div><div><h4 class="title"><a name="id2606616"></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" title="Updating from Samba Versions between 3.0.6 and 3.0.10"><div class="titlepage"><div><div><h4 class="title"><a name="id2606638"></a>Updating from Samba Versions between 3.0.6 and 3.0.10</h4></div></div></div><p> - <a class="indexterm" name="id2606646"></a> - <a class="indexterm" name="id2606653"></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="id2606670"></a> - <a class="indexterm" name="id2606676"></a> - <a class="indexterm" name="id2606683"></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" title="Updating from Samba Versions after 3.0.6 to a Current Release"><div class="titlepage"><div><div><h4 class="title"><a name="id2606717"></a>Updating from Samba Versions after 3.0.6 to a Current Release</h4></div></div></div><p> - <a class="indexterm" name="id2606725"></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="id2606757"></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">“Addition of Machines to the Domain”</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" title="Migrating Samba-3 to a New Server"><div class="titlepage"><div><div><h3 class="title"><a name="id2606808"></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" title="Replacing a Domain Member Server"><div class="titlepage"><div><div><h4 class="title"><a name="id2606820"></a>Replacing a Domain Member Server</h4></div></div></div><p> - <a class="indexterm" name="id2606828"></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">“Adding Domain Member Servers and Clients”</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="id2606854"></a> - <a class="indexterm" name="id2606860"></a> - <a class="indexterm" name="id2606867"></a> - <a class="indexterm" name="id2606874"></a> - <a class="indexterm" name="id2606880"></a> - <a class="indexterm" name="id2606887"></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="id2606935"></a> - <a class="indexterm" name="id2606941"></a> - <a class="indexterm" name="id2606948"></a> - <a class="indexterm" name="id2606955"></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="id2607003"></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" title="Replacing a Domain Controller"><div class="titlepage"><div><div><h4 class="title"><a name="id2607022"></a>Replacing a Domain Controller</h4></div></div></div><p> - <a class="indexterm" name="id2607030"></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 @@ -847,7 +847,7 @@ back to searching the 'ldap suffix' in some cases. have the intent to just replace the old Samba server with a new one with the same name as the old one. In this case, simply follow the same process as for upgrading a Samba 2.x system and do the following: - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> Where UNIX (POSIX) user and group accounts are stored in the system <code class="filename">/etc/passwd</code>, <code class="filename">/etc/shadow</code>, and <code class="filename">/etc/group</code> files, be sure to add the same accounts @@ -862,19 +862,19 @@ back to searching the 'ldap suffix' in some cases. <code class="literal">slapadd</code> command. Do not forget to install and configure the <code class="literal">nss_ldap</code> tool and the <code class="filename">/etc/nsswitch.conf</code> (as shown in <a class="link" href="happy.html" title="Chapter 5. Making Happy Users">“Making Happy Users”</a>). - </p></li><li class="listitem"><p> + </p></li><li><p> Copy the <code class="filename">smb.conf</code> file from the old server to the new server into the correct location as indicated previously in this chapter. - </p></li><li class="listitem"><p> + </p></li><li><p> Copy the <code class="filename">secrets.tdb</code> file, the <code class="filename">smbpasswd</code> file (if it is used), the <code class="filename">/etc/samba/passdb.tdb</code> file (only used by the <code class="constant">tdbsam</code> backend), and all the tdb control files from the old system to the correct location on the new system. - </p></li><li class="listitem"><p> + </p></li><li><p> Before starting the Samba daemons, verify that the hostname of the new server is identical to that of the old one. Note: The IP address can be different from that of the old server. - </p></li><li class="listitem"><p> + </p></li><li><p> Copy all files from the old server to the new server, taking precaution to preserve all file ownership and permissions as well as any POSIX ACLs that may have been created on the old server. @@ -890,31 +890,31 @@ 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" title="Migration of Samba Accounts to Active Directory"><div class="titlepage"><div><div><h3 class="title"><a name="id2607222"></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" title="Procedure 8.2. Migration to Active Directory"><a name="id2607234"></a><p class="title"><b>Procedure 8.2. Migration to Active Directory</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><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 called <code class="constant">Administrator</code> in your Samba domain, with full administrative (root) rights to that domain. - </p></li><li class="step" title="Step 2"><p> + </p></li><li><p> In the Advanced/DNS section of the TCP/IP settings on your Windows workstations, make sure the <em class="parameter"><code>DNS suffix for this connection</code></em> field is blank. - </p></li><li class="step" title="Step 3"><p> + </p></li><li><p> Because you are migrating from Samba, user passwords cannot be migrated. You'll have to reset everyone's passwords. (If you were migrating from NT4 to ADS, you could migrate passwords as well.) </p><p> To date this has not been attempted with roaming profile support; it has been documented as working with local profiles. - </p></li><li class="step" title="Step 4"><p> + </p></li><li><p> Disable the Windows Firewall on all workstations. Otherwise, workstations won't be migrated to the new domain. - </p></li><li class="step" title="Step 5"><p> - <a class="indexterm" name="id2607301"></a> + </p></li><li><p> + <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,23 +922,23 @@ 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="id2607318"></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 class="itemizedlist" type="disc"><li class="listitem"><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> You can migrate workstations remotely. You can specify that SIDs be simply added instead of replaced, giving you the option of joining a workstation back to the old domain if something goes awry. The workstations will be joined to the new domain. - </p></li><li class="listitem"><p> + </p></li><li><p> Not only are user accounts migrated from the old domain to the new domain, but ACLs on the workstations are migrated as well. Like SIDs, ACLs can be added instead of replaced. - </p></li><li class="listitem"><p> + </p></li><li><p> Locally stored user profiles on workstations are migrated as well, presenting almost no disruption to the user. Saved passwords will be lost, just as when you administratively reset the password in Windows ADS. - </p></li><li class="listitem"><p> + </p></li><li><p> The ADMT lets you test all operations before actually performing the migration. Accounts and workstations can be migrated individually or in batches. User accounts can be safely migrated all at once (since no |
