source: vendor/3.5.0/docs/htmldocs/Samba3-ByExample/preface.html

Last change on this file was 414, checked in by Herwig Bauernfeind, 15 years ago

Samba 3.5.0: Initial import
File size: 29.5 KB
Line 
1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Preface</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="pr03.html" title="Foreword"><link rel="next" href="ExNetworks.html" title="Part I. Example Network Configurations"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Preface</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr03.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ExNetworks.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="preface"></a>Preface</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="preface.html#id2501251">Why Is This Book Necessary?</a></span></dt><dd><dl><dt><span class="sect2"><a href="preface.html#id2498970">Samba 3.0.20 Update Edition</a></span></dt></dl></dd><dt><span class="sect1"><a href="preface.html#id2498857">Prerequisites</a></span></dt><dt><span class="sect1"><a href="preface.html#id2498889">Approach</a></span></dt><dt><span class="sect1"><a href="preface.html#id2498954">Summary of Topics</a></span></dt><dt><span class="sect1"><a href="preface.html#id2550647">Conventions Used</a></span></dt></dl></div><p>
2 Network administrators live busy lives. We face distractions and pressures
3 that drive us to seek proven, working case scenarios that can be easily
4 implemented. Often this approach lands us in trouble. There is a
5 saying that, geometrically speaking, the shortest distance between two
6 points is a straight line, but practically we find that the quickest
7 route to a stable network solution is the long way around.
8 </p><p>
9 This book is your means to the straight path. It provides step-by-step,
10 proven, working examples of Samba deployments. If you want to deploy
11 Samba-3 with the least effort, or if you want to become an expert at deploying
12 Samba-3 without having to search through lots of documentation, this
13 book is the ticket to your destination.
14 </p><p>
15 Samba is software that can be run on a platform other than Microsoft Windows,
16 for example, UNIX, Linux, IBM System 390, OpenVMS, and other operating systems.
17 Samba uses the TCP/IP protocol that is installed on the host server. When
18 correctly configured, it allows that host to interact with a Microsoft Windows
19 client or server as if it is a Windows file and print server. This book
20 will help you to implement Windows-compatible file and print services.
21 </p><p>
22 The examples presented in this book are typical of various businesses and
23 reflect the problems and challenges they face. Care has been taken to preserve
24 attitudes, perceptions, practices, and demands from real network case studies.
25 The maximum benefit may be obtained from this book by working carefully through
26 each exercise. You may be in a hurry to satisfy a specific need, so feel
27 free to locate the example that most closely matches your need, copy it, and
28 innovate as much as you like. Above all, enjoy the process of learning the
29 secrets of MS Windows networking that is truly liberated by Samba.
30 </p><p>
31 The focus of attention in this book is Samba-3. Specific notes are made in
32 respect of how Samba may be made secure. This book does not attempt to provide
33 detailed information regarding secure operation and configuration of peripheral
34 services and applications such as OpenLDAP, DNS and DHCP, the need for which
35 can be met from other resources that are dedicated to the subject.
36 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2501251"></a>Why Is This Book Necessary?</h2></div></div></div><p>
37 This book is the result of observations and feedback. The feedback from
38 the Samba-HOWTO-Collection has been positive and complimentary. There
39 have been requests for far more worked examples, a
40 &#8220;<span class="quote">Samba Cookbook,</span>&#8221; and for training materials to
41 help kick-start the process of mastering Samba.
42 </p><p>
43 The Samba mailing lists users have asked for sample configuration files
44 that work. It is natural to question one's own ability to correctly
45 configure a complex tool such as Samba until a minimum necessary
46 knowledge level has been attained.
47 </p><p>
48 The Samba-HOWTO-Collection as does <span class="emphasis"><em>The Official Samba-3 HOWTO and
49 Reference Guide</em></span> documents Samba features and functionality in
50 a topical context. This book takes a completely different approach. It
51 walks through Samba network configurations that are working within particular
52 environmental contexts, providing documented step-by-step implementations.
53 All example case configuration files, scripts, and other tools are provided
54 on the CD-ROM. This book is descriptive, provides detailed diagrams, and
55 makes deployment of Samba-3 a breeze.
56 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2498970"></a>Samba 3.0.20 Update Edition</h3></div></div></div><p>
57 The Samba 3.0.x series has been remarkably popular. At the time this book first
58 went to print samba-3.0.2 was being released. There have been significant modifications
59 and enhancements between samba-3.0.2 and samba-3.0.14 (the current release) that
60 necessitate this documentation update. This update has the specific intent to
61 refocus this book so that its guidance can be followed for samba-3.0.20
62 and beyond. Further changes are expected as Samba-3 matures further and will
63 be reflected in future updates.
64 </p><p>
65 The changes shown in <a class="link" href="preface.html#pref-new" title="Table 1. Samba Changes 3.0.2 to 3.0.20">&#8220;Samba Changes 3.0.2 to 3.0.20&#8221;</a> are incorporated in this update.
66 </p><div class="table"><a name="pref-new"></a><p class="title"><b>Table 1. Samba Changes 3.0.2 to 3.0.20</b></p><div class="table-contents"><table summary="Samba Changes 3.0.2 to 3.0.20" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">
67 <p>
68 New Feature
69 </p>
70 </th><th align="left">
71 <p>
72 Description
73 </p>
74 </th></tr></thead><tbody><tr><td align="left">
75 <p>
76 Winbind Case Handling
77 </p>
78 </td><td align="justify">
79 <p>
80 User and group names returned by <code class="literal">winbindd</code> are now converted to lower case
81 for better consistency. Samba implementations that depend on the case of information returned
82 by winbind (such as %u and %U) must now convert the dependency to expecting lower case values.
83 This affects mail spool files, home directories, valid user lines in the <code class="filename">smb.conf</code> file, etc.
84 </p>
85 </td></tr><tr><td align="left">
86 <p>
87 Schema Changes
88 </p>
89 </td><td align="justify">
90 <p>
91 Addition of code to handle password aging, password uniqueness controls, bad
92 password instances at logon time, have made necessary extensions to the SambaSAM
93 schema. This change affects all sites that use LDAP and means that the directory
94 schema must be updated.
95 </p>
96 </td></tr><tr><td align="left">
97 <p>
98 Username Map Handling
99 </p>
100 </td><td align="justify">
101 <p>
102 Samba-3.0.8 redefined the behavior: Local authentication results in a username map file
103 lookup before authenticating the connection. All authentication via an external domain
104 controller will result in the use of the fully qualified name (i.e.: DOMAIN\username)
105 after the user has been successfully authenticated.
106 </p>
107 </td></tr><tr><td align="left">
108 <p>
109 UNIX Extension Handling
110 </p>
111 </td><td align="justify">
112 <p>
113 Symbolically linked files and directories on the UNIX host to absolute paths will
114 now be followed. This can be turned off using &#8220;<span class="quote">wide links = No</span>&#8221; in
115 the share stanza in the <code class="filename">smb.conf</code> file. Turning off &#8220;<span class="quote">wide links</span>&#8221;
116 support will degrade server performance because each path must be checked.
117 </p>
118 </td></tr><tr><td align="left">
119 <p>
120 Privileges Support
121 </p>
122 </td><td align="justify">
123 <p>
124 Versions of Samba prior to samba-3.0.11 required the use of the UNIX <code class="constant">root</code>
125 account from network Windows clients. The new &#8220;<span class="quote">enable privileges = Yes</span>&#8221; capability
126 means that functions such as adding machines to the domain, managing printers, etc. can now
127 be delegated to normal user accounts or to groups of users.
128 </p>
129 </td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498857"></a>Prerequisites</h2></div></div></div><p>
130 This book is not a tutorial on UNIX or Linux administration. UNIX and Linux
131 training is best obtained from books dedicated to the subject. This book
132 assumes that you have at least the basic skill necessary to use these operating
133 systems, and that you can use a basic system editor to edit and configure files.
134 It has been written with the assumption that you have experience with Samba,
135 have read <span class="emphasis"><em>The Official Samba-3 HOWTO and Reference Guide</em></span> and
136 the Samba-HOWTO-Collection, or that you have familiarity with Microsoft Windows.
137 </p><p>
138 If you do not have this experience, you can follow the examples in this book but may
139 find yourself at times intimidated by assumptions made. In this situation, you
140 may need to refer to administrative guides or manuals for your operating system
141 platform to find what is the best method to achieve what the text of this book describes.
142 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498889"></a>Approach</h2></div></div></div><p>
143 The first chapter deals with some rather thorny network analysis issues. Do not be
144 put off by this. The information you glean, even without a detailed understanding
145 of network protocol analysis, can help you understand how Windows networking functions.
146 </p><p>
147 Each following chapter of this book opens with the description of a networking solution
148 sought by a hypothetical site. Bob Jordan is a hypothetical decision maker
149 for an imaginary company, <code class="constant">Abmas Biz NL</code>. We will use the
150 non-existent domain name <code class="constant">abmas.biz</code>. All <span class="emphasis"><em>facts</em></span>
151 presented regarding this company are fictitious and have been drawn from a variety of real
152 business scenarios over many years. Not one of these reveal the identify of the
153 real-world company from which the scenario originated.
154 </p><p>
155 In any case, Mr. Jordan likes to give all his staff nasty little assignments.
156 Stanley Saroka is one of his proteges; Christine Roberson is the network administrator
157 Bob trusts. Jordan is inclined to treat other departments well because they finance
158 Abmas IT operations.
159 </p><p>
160 Each chapter presents a summary of the network solution we have chosen to
161 demonstrate together with a rationale to help you to understand the
162 thought process that drove that solution. The chapter then documents in precise
163 detail all configuration files and steps that must be taken to implement the
164 example solution. Anyone wishing to gain serious value from this book will
165 do well to take note of the implications of points made, so watch out for the
166 <span class="emphasis"><em>this means that</em></span> notations.
167 </p><p>
168 Each chapter has a set of questions and answers to help you to
169 to understand and digest key attributes of the solutions presented.
170 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498954"></a>Summary of Topics</h2></div></div></div><p>
171 The contents of this second edition of <span class="emphasis"><em>Samba-3 by Example</em></span>
172 have been rearranged based on feedback from purchasers of the first edition.
173 </p><p>
174 Clearly the first edition contained most of what was needed and that was missing
175 from other books that cover this difficult subject. The new arrangement adds
176 additional material to meet consumer requests and includes changes that originated
177 as suggestions for improvement.
178 </p><p>
179 Chapter 1 now dives directly into the heart of the implementation of Windows
180 file and print server networks that use Samba at the heart.
181 </p><div class="variablelist"><dl><dt><span class="term">Chapter 1 No Frills Samba Servers.</span></dt><dd><p>
182 Here you design a solution for three different business scenarios, each for a
183 company called Abmas. There are two simple networking problems and one slightly
184 more complex networking challenge. In the first two cases, Abmas has a small
185 simple office, and they want to replace a Windows 9x peer-to-peer network. The
186 third example business uses Windows 2000 Professional. This must be simple,
187 so let's see how far we can get. If successful, Abmas grows quickly and
188 soon needs to replace all servers and workstations.
189 </p><p><span class="emphasis"><em>TechInfo</em></span> This chapter demands:
190 </p><div class="itemizedlist"><ul type="disc"><li><p>Case 1: The simplest <code class="filename">smb.conf</code> file that may
191 reasonably be used. Works with Samba-2.x also. This
192 configuration uses Share Mode security. Encrypted
193 passwords are not used, so there is no
194 <code class="filename">smbpasswd</code> file.
195 </p></li><li><p>Case 2: Another simple <code class="filename">smb.conf</code> file that adds
196 WINS support and printing support. This case deals with
197 a special requirement that demonstrates how to deal with
198 purpose-built software that has a particular requirement
199 for certain share names and printing demands. This
200 configuration uses Share Mode security and also works with
201 Samba-2.x. Encrypted passwords are not used, so there is no
202 <code class="filename">smbpasswd</code> file.
203 </p></li><li><p>Case 3: This <code class="filename">smb.conf</code> configuration uses User Mode
204 security. The file share configuration demonstrates
205 the ability to provide master access to an administrator
206 while restricting all staff to their own work areas.
207 Encrypted passwords are used, so there is an implicit
208 <code class="filename">smbpasswd</code> file.
209 </p></li></ul></div><p>
210 </p></dd><dt><span class="term">Chapter 2 Small Office Networking.</span></dt><dd><p>
211 Abmas is a successful company now. They have 50 network users
212 and want a little more varoom from the network. This is a typical
213 small office and they want better systems to help them to grow. This is
214 your chance to really give advanced users a bit more functionality and usefulness.
215 </p><p><span class="emphasis"><em>TechInfo</em></span> This <code class="filename">smb.conf</code> file
216 makes use of encrypted passwords, so there is an <code class="filename">smbpasswd</code>
217 file. It also demonstrates use of the <em class="parameter"><code>valid users</code></em> and
218 <em class="parameter"><code>valid groups</code></em> to restrict share access. The Windows
219 clients access the server as Domain members. Mobile users log onto
220 the Domain while in the office, but use a local machine account while on the
221 road. The result is an environment that answers mobile computing user needs.
222 </p></dd><dt><span class="term">Chapter 3 Secure Office Networking.</span></dt><dd><p>
223 Abmas is growing rapidly now. Money is a little tight, but with 130
224 network users, security has become a concern. They have many new machines
225 to install and the old equipment will be retired. This time they want the
226 new network to scale and grow for at least two years. Start with a sufficient
227 system and allow room for growth. You are now implementing an Internet
228 connection and have a few reservations about user expectations.
229 </p><p><span class="emphasis"><em>TechInfo</em></span> This <code class="filename">smb.conf</code> file
230 makes use of encrypted passwords, and you can use a <code class="filename">tdbsam</code>
231 password backend. Domain logons are introduced. Applications are served from the central
232 server. Roaming profiles are mandated. Access to the server is tightened up
233 so that only domain members can access server resources. Mobile computing
234 needs still are catered to.
235 </p></dd><dt><span class="term">Chapter 4 The 500 User Office.</span></dt><dd><p>
236 The two-year projections were met. Congratulations, you are a star.
237 Now Abmas needs to replace the network. Into the existing user base, they
238 need to merge a 280-user company they just acquired. It is time to build a serious
239 network. There are now three buildings on one campus and your assignment is
240 to keep everyone working while a new network is rolled out. Oh, isn't it nice
241 to roll out brand new clients and servers! Money is no longer tight, you get
242 to buy and install what you ask for. You will install routers and a firewall.
243 This is exciting!
244 </p><p><span class="emphasis"><em>TechInfo</em></span> This <code class="filename">smb.conf</code> file
245 makes use of encrypted passwords, and a <code class="filename">tdbsam</code>
246 password backend is used. You are not ready to launch into LDAP yet, so you
247 accept the limitation of having one central Domain Controller with a Domain
248 Member server in two buildings on your campus. A number of clever techniques
249 are used to demonstrate some of the smart options built into Samba.
250 </p></dd><dt><span class="term">Chapter 5 Making Happy Users.</span></dt><dd><p>
251 Congratulations again. Abmas is happy with your services and you have been given another raise.
252 Your users are becoming much more capable and are complaining about little
253 things that need to be fixed. Are you up to the task? Mary says it takes her 20 minutes
254 to log onto the network and it is killing her productivity. Email is a bit <span class="emphasis"><em>
255 unreliable</em></span> have you been sleeping on the job? We do not discuss the
256 technology of email but when the use of mail clients breaks because of networking
257 problems, you had better get on top of it. It's time for a change.
258 </p><p><span class="emphasis"><em>TechInfo</em></span> This <code class="filename">smb.conf</code> file
259 makes use of encrypted passwords; a distributed <code class="filename">ldapsam</code>
260 password backend is used. Roaming profiles are enabled. Desktop profile controls
261 are introduced. Check out the techniques that can improve the user experience
262 of network performance. As a special bonus, this chapter documents how to configure
263 smart downloading of printer drivers for drag-and-drop printing support. And, yes,
264 the secret of configuring CUPS is clearly documented. Go for it; this one will
265 tease you, too.
266 </p></dd><dt><span class="term">Chapter 6 A Distributed 2000 User Network.</span></dt><dd><p>
267 Only eight months have passed, and Abmas has acquired another company. You now need to expand
268 the network further. You have to deal with a network that spans several countries.
269 There are three new networks in addition to the original three buildings at the head-office
270 campus. The head office is in New York and you have branch offices in Washington, Los Angeles, and
271 London. Your desktop standard is Windows XP Professional. In many ways, everything has changed
272 and yet it must remain the same. Your team is primed for another roll-out. You know there are
273 further challenges ahead.
274 </p><p><span class="emphasis"><em>TechInfo</em></span> Slave LDAP servers are introduced. Samba is
275 configured to use multiple LDAP backends. This is a brief chapter; it assumes that the
276 technology has been mastered and gets right down to concepts and how to deploy them.
277 </p></dd><dt><span class="term">Chapter 7 Adding UNIX/Linux Servers and Clients.</span></dt><dd><p>
278 Well done, Bob, your team has achieved much. Now help Abmas integrate the entire network.
279 You want central control and central support and you need to cut costs. How can you reduce administrative
280 overheads and yet get better control of the network?
281 </p><p>
282 This chapter has been contributed by Mark Taylor <code class="email">&lt;<a class="email" href="mailto:mark.taylor@siriusit.co.uk">mark.taylor@siriusit.co.uk</a>&gt;</code>
283 and is based on a live site. For further information regarding this example case,
284 please contact Mark directly.
285 </p><p><span class="emphasis"><em>TechInfo</em></span> It is time to consider how to add Samba servers
286 and UNIX and Linux network clients. Users who convert to Linux want to be able to log on
287 using Windows network accounts. You explore nss_ldap, pam_ldap, winbind, and a few neat
288 techniques for taking control. Are you ready for this?
289 </p></dd><dt><span class="term">Chapter 8 Updating Samba-3.</span></dt><dd><p>
290 This chapter is the result of repeated requests for better documentation of the steps
291 that must be followed when updating or upgrading a Samba server. It attempts to cover
292 the entire subject in broad-brush but at the same time provides detailed background
293 information that is not covered elsewhere in the Samba documentation.
294 </p><p><span class="emphasis"><em>TechInfo</em></span> Samba stores a lot of essential network
295 information in a large and growing collection of files. This chapter documents the
296 essentials of where those files may be located and how to find them. It also provides
297 an insight into inter-related matters that affect a Samba installation.
298 </p></dd><dt><span class="term">Chapter 9 Migrating NT4 Domain to Samba-3.</span></dt><dd><p>
299 Another six months have passed. Abmas has acquired yet another company. You will find a
300 way to migrate all users off the old network onto the existing network without loss
301 of passwords and will effect the change-over during one weekend. May the force (and caffeine) be with
302 you, may you keep your back to the wind and may the sun shine on your face.
303 </p><p><span class="emphasis"><em>TechInfo</em></span> This chapter demonstrates the use of
304 the <code class="literal">net rpc migrate</code> facility using an LDAP ldapsam backend, and also
305 using a tdbsam passdb backend. Both are much-asked-for examples of NT4 Domain migration.
306 </p></dd><dt><span class="term">Chapter 10 Migrating NetWare 4.11 Server to Samba.</span></dt><dd><p>
307 Misty Stanley-Jones has contributed information that summarizes her experience at migration
308 from a NetWare server to Samba-3.
309 </p><p><span class="emphasis"><em>TechInfo</em></span> The documentation provided demonstrates
310 how one site migrated from NetWare to Samba. Some alternatives tools are mentioned. These
311 could be used to provide another pathway to a successful migration.
312 </p></dd><dt><span class="term">Chapter 11 Active Directory, Kerberos and Security.</span></dt><dd><p>
313 Abmas has acquired another company that has just migrated to running Windows Server 2003 and
314 Active Directory. One of your staff makes offhand comments that land you in hot water.
315 A network security auditor is hired by the head of the new business and files a damning
316 report, and you must address the <span class="emphasis"><em>defects</em></span> reported. You have hired new
317 network engineers who want to replace Microsoft Active Directory with a pure Kerberos
318 solution. How will you handle this?
319 </p><p><span class="emphasis"><em>TechInfo</em></span> This chapter is your answer. Learn about
320 share access controls, proper use of UNIX/Linux file system access controls, and Windows
321 200x Access Control Lists. Follow these steps to beat the critics.
322 </p></dd><dt><span class="term">Chapter 12 Integrating Additional Services.</span></dt><dd><p>
323 The battle is almost over, Samba-3 has won the day. Your team are delighted and now you
324 find yourself at yet another cross-roads. Abmas have acquired a snack food business, you
325 made promises you must keep. IT costs must be reduced, you have new resistance, but you
326 will win again. This time you choose to install the Squid proxy server to validate the
327 fact that Samba is far more than just a file and print server. SPNEGO authentication
328 support means that your Microsoft Windows clients gain transparent proxy access.
329 </p><p><span class="emphasis"><em>TechInfo</em></span> Samba provides the <code class="literal">ntlm_auth</code>
330 module that makes it possible for MS Windows Internet Explorer to connect via the Squid Web
331 and FTP proxy server. You will configure Samba-3 as well as Squid to deliver authenticated
332 access control using the Active Directory Domain user security credentials.
333 </p></dd><dt><span class="term">Chapter 13 Performance, Reliability and Availability.</span></dt><dd><p>
334 Bob, are you sure the new Samba server is up to the load? Your network is serving many
335 users who risk becoming unproductive. What can you do to keep ahead of demand? Can you
336 keep the cost under control also? What can go wrong?
337 </p><p><span class="emphasis"><em>TechInfo</em></span> Hot tips that put chili into your
338 network. Avoid name resolution problems, identify potential causes of network collisions,
339 avoid Samba configuration options that will weigh the server down. MS distributed file
340 services to make your network fly and much more. This chapter contains a good deal of
341 &#8220;<span class="quote">Did I tell you about this...?</span>&#8221; type of hints to help keep your name on the top
342 performers list.
343 </p></dd><dt><span class="term">Chapter 14 Samba Support.</span></dt><dd><p>
344 This chapter has been added specifically to help those who are seeking professional
345 paid support for Samba. The critics of Open Source Software often assert that
346 there is no support for free software. Some critics argue that free software
347 undermines the service that proprietary commercial software vendors depend on.
348 This chapter explains what are the support options for Samba and the fact that
349 a growing number of businesses make money by providing commercial paid-for
350 Samba support.
351 </p></dd><dt><span class="term">Chapter 15 A Collection of Useful Tid-bits.</span></dt><dd><p>
352 Sometimes it seems that there is not a good place for certain odds and ends that
353 impact Samba deployment. Some readers would argue that everyone can be expected
354 to know this information, or at least be able to find it easily. So to avoid
355 offending a reader's sensitivities, the tid-bits have been placed in this chapter.
356 Do check out the contents, you may find something of value among the loose ends.
357 </p></dd><dt><span class="term">Chapter 16 Windows Networking Primer.</span></dt><dd><p>
358 Here we cover practical exercises to help us to understand how MS Windows
359 network protocols function. A network protocol analyzer helps you to
360 appreciate the fact that Windows networking is highly dependent on broadcast
361 messaging. Additionally, you can look into network packets that a Windows
362 client sends to a network server to set up a network connection. On completion,
363 you should have a basic understanding of how network browsing functions and
364 have seen some of the information a Windows client sends to
365 a file and print server to create a connection over which file and print
366 operations may take place.
367 </p></dd></dl></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2550647"></a>Conventions Used</h2></div></div></div><p>
368 The following notation conventions are used throughout this book:
369 </p><div class="itemizedlist"><ul type="disc"><li><p>
370 TOSHARG2 is used as an abbreviation for the book, &#8220;<span class="quote">The Official Samba-3
371 HOWTO and Reference Guide, Second Edition</span>&#8221; Editors: John H. Terpstra and Jelmer R. Vernooij,
372 Publisher: Prentice Hall, ISBN: 0131882228.
373 </p></li><li><p>
374 S3bE2 is used as an abbreviation for the book, &#8220;<span class="quote">Samba-3 by Example, Second Edition</span>&#8221;
375 Editors: John H. Terpstra, Publisher: Prentice Hall, ISBN: 013188221X.
376 </p></li><li><p>
377 Directories and filenames appear in mono-font. For example,
378 <code class="filename">/etc/pam.conf</code>.
379 </p></li><li><p>
380 Executable names are bolded. For example, <code class="literal">smbd</code>.
381 </p></li><li><p>
382 Menu items and buttons appear in bold. For example, click <span class="guibutton">Next</span>.
383 </p></li><li><p>
384 Selecting a menu item is indicated as:
385 <span class="guimenu">Start</span> &#8594; <span class="guimenuitem">Control Panel</span> &#8594; <span class="guimenuitem">Administrative Tools</span> &#8594; <span class="guimenuitem">Active Directory Users and Computers</span>
386 </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>
Note: See TracBrowser for help on using the repository browser.