| blob | c1a992ca06ca66cdfff601b908450bb2ebf558f7 |
1 <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.70.1"><link rel="start" 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#id2558580">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2558603">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2558670">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2558724">Technical Issues</a></span></dt><dt><span class="sect2"><a href="small.html#id2558936">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2558957">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2560702">Validation</a></span></dt><dt><span class="sect2"><a href="small.html#id2561389">Notebook Computers: A Special Case</a></span></dt><dt><span class="sect2"><a href="small.html#id2561414">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2561490">Questions and Answers</a></span></dt></dl></div><p>
2 <a href="simple.html" title="Chapter 1. No-Frills Samba Servers">???</a> focused on the basics of simple yet effective
3 network solutions. Network administrators who take pride in their work
4 (that's most of us, right?) take care to deliver what our users want,
5 but not too much more. If we make things too complex, we confound our users
6 and increase costs of network ownership. A professional network manager
7 avoids the temptation to put too much pizazz into the way that the network
8 operates. Some creativity is helpful, but keep it under control
9 good advice that the following two scenarios illustrate.
10 </p><p>
12 In one case the network administrator of a mid-sized company spent three
13 months building a new network to replace an old Netware server. What he
14 delivered had all the bells and whistles he could muster. There were a
15 few teething problems during the changeover, nothing serious but a little
16 disruptive all the same. Users were exposed to many changes at once. The
17 network administrator was asked to resign two months after implementing
18 the new system because so many staff complained they had lost time and
19 were not happy with the new network. Everything was automated, and he
20 delivered more features than any advanced user could think of. He was
21 just too smart for his own good.
22 </p><p>
23 In the case of the other company, a new network manager was appointed
24 to oversee the replacement of a LanTastic network with an MS Windows
25 NT 4.0 network. He had the replacement installed and operational within
26 two weeks. Before installation and changeover, he called a meeting to
27 explain to all users what was going to happen, how it would affect them,
28 and that he would be available 24 hours a day to help them transition.
29 One week after conversion, he held another meeting asking for cooperation
30 in the introduction of a few new features that would help to make life
31 easier. Network users were thrilled with the help he provided. The network
32 he implemented was nowhere near as complex as in the first example, had fewer
33 features, and yet he had happy users. Months later he was still adding
34 new innovations. He always asked the users if a
35 particular feature was what they wanted. He asked his boss for a raise
38 get on with our next exercise.
39 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558580"></a>Introduction</h2></div></div></div><p>
40 Abmas Accounting has grown. Mr. Meany likes you and says he knew you
41 were the right person for the job. That's why he asked you to install the
42 new server. The past few months have been hard work. You advised Mr. Meany
43 that it is time for a change. Abmas now has 52 users, having acquired an
44 investment consulting business recently. The new users were added to the
45 network without any problems.
46 </p><p>
47 Some of the Windows clients are nearly past their use-by date.
48 You found damaged and unusable software on some of the workstations
49 that came with the acquired business and found some machines
50 in need of both hardware and software maintenance.
51 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558603"></a>Assignment Tasks</h3></div></div></div><p>
53 Mr. Meany is retiring in 12 months. Before he goes, he wants you to help ensure
54 that the business is running efficiently. Many of the new staff want notebook
55 computers. They visit customer business premises and need to use local network
56 facilities; these users are technically competent. The company uses a
57 business application that requires Windows XP Professional. In short, a complete
58 client upgrade is about to happen. Mr. Meany told you that he is working
59 on another business acquisition and that by the time he retires there will be
61 </p><p>
62 Mr. Meany is not concerned about security. He wants to make it easier for
63 staff to do their work. He has hired you to help him appoint a full-time
64 network manager before he retires. Above all, he says he is investing in
65 the ability to grow. He is determined to live his lifelong dream and
66 hand the business over to a bright and capable executive who can make
67 things happen. This means your network design must cope well with
68 growth.
69 </p><p>
70 In a few months, Abmas will require an Internet connection for email and so
71 that staff can easily obtain software updates. Mr. Meany is warming up to
72 the installation of antivirus software but is not yet ready to approve
73 this expense. He told you to spend the money a virus scanner costs
74 on better quality notebook computers for mobile users.
75 </p><p>
76 One of Mr. Meany's golfing partners convinced him to buy new laser
77 printers, one black only, the other a color laser printer. Staff support
78 the need for a color printer so they can present more attractive proposals
79 and reports.
80 </p><p>
81 Mr. Meany also asked if it would be possible for one of the staff to manage
82 user accounts from the Windows desktop. That person will be responsible for
83 basic operations.
84 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558670"></a>Dissection and Discussion</h2></div></div></div><p>
85 What are the key requirements in this business example? A quick review indicates
86 a need for
89 </p></li><li><p>
90 Mobile computing capability
92 </p></li><li><p>
93 Improved reliability and usability
94 </p></li><li><p>
95 Easier administration
96 </p></li></ul></div><p>
97 In this instance the installed Linux system is assumed to be a Red Hat Linux Fedora Core2 server
100 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558724"></a>Technical Issues</h3></div></div></div><p>
107 smbpasswd</code> (default) backend. You should implement a DHCP server. There is no need to
108 run DNS at this time, but the system will use WINS. The domain name will be <code class="constant">
109 BILLMORE</code>. This time, the name of the server will be <code class="constant">SLEETH</code>.
110 </p><p>
111 All printers will be configured as DHCP clients. The DHCP server will assign
112 the printer a fixed IP address by way of its Ethernet interface (MAC) address.
113 See <a href="small.html#dhcp01" title="Example 2.2. Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf">???</a>.
114 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
115 The <code class="filename">smb.conf</code> file you are creating in this exercise can be used with equal effectiveness
116 with Samba-2.2.x series releases. This is deliberate so that in the next chapter it is
117 possible to start with the installation that you have created here, migrate it
118 to a Samba-3 configuration, and then secure the system further. Configurations following
119 this one utilize features that may not be supported in Samba-2.2.x releases.
120 However, you should note that the examples in each chapter start with the assumption
121 that a fresh new installation is being effected.
122 </p></div><p>
123 Later on, when the Internet connection is implemented, you will add DNS as well as
124 other enhancements. It is important that you plan accordingly.
125 </p><p>
127 You have split the network into two separate areas. Each has its own Ethernet switch.
129 network. The server has two network interfaces, one serving each network. The
130 network printers will be located in a central area. You plan to install the new
131 printers and keep the old printer in use also.
132 </p><p>
133 You will provide separate file storage areas for each business entity. The old system
134 will go away, accounting files will be handled under a single directory, and files will
135 be stored under customer name, not under a personal work area. Staff will be made
136 responsible for file location, so the old share point must be maintained.
137 </p><p>
138 Given that DNS will not be used, you will configure WINS name resolution for UNIX
139 hostname name resolution.
140 </p><p>
143 It is necessary to map Windows Domain Groups to UNIX groups. It is
144 advisable to also map Windows Local Groups to UNIX groups. Additionally, the two
145 key staff groups in the firm are accounting staff and financial services staff.
146 For these, it is necessary to create UNIX groups as well as Windows Domain Groups.
147 </p><p>
148 In the sample <code class="filename">smb.conf</code> file, you have configured Samba to call the UNIX
149 <span><strong class="command">groupadd</strong></span> to add group entries. This utility does not permit
150 the addition of group names that contain uppercase characters or spaces. This
152 <span><strong class="command">shadow-utils</strong></span> open source software package. A later release
153 of this package may have been patched to resolve this bug. If your operating
154 platform has this bug, it means that attempts to add a Windows Domain Group that
155 has either a space or uppercase characters in it will fail. See
157 more information.
158 </p><p>
160 Vendor-supplied printer drivers will be installed on each client. The CUPS print
162 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558936"></a>Political Issues</h3></div></div></div><p>
163 Mr. Meany is an old-school manager. He sets the rules and wants to see compliance.
164 He is willing to spend money on things he believes are of value. You need more
165 time to convince him of real priorities.
166 </p><p>
167 Go ahead, buy better notebooks. Wouldn't it be neat if they happened to be
168 supplied with antivirus software? Above all, demonstrate good purchase value and remember
169 to make your users happy.
170 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558957"></a>Implementation</h2></div></div></div><p>
172 In this example, the assumption is made that this server is being configured from a clean start.
173 The alternate approach could be to demonstrate the migration of the system that is documented
174 in <a href="simple.html#AcctgNet" title="Implementation">???</a> to meet the new requirements. The decision to treat this case, as with
175 future examples, as a new installation is based on the premise that you can determine
176 the migration steps from the information provided in <a href="ntmigration.html" title="Chapter 9. Migrating NT4 Domain to Samba-3">???</a>.
177 Additionally, a fresh installation makes the example easier to follow.
178 </p><p>
180 Each user will be given a home directory on the UNIX system, which will be available as a private
181 share. Two additional shares will be created, one for the accounting department and the other for
182 the financial services department. Network users will be given access to these shares by way
183 of group membership.
184 </p><p>
186 UNIX group membership is the primary mechanism by which Windows Domain users will be granted
187 rights and privileges within the Windows environment.
188 </p><p>
190 The user <span><strong class="command">alanm</strong></span> will be made the owner of all files. This will be preserved
191 by setting the sticky bit (set UID/GID) on the top-level directories.
192 </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="id2559087"></a><p class="title"><b>Procedure 2.1. Server Installation Steps</b></p><ol type="1"><li><p>
194 </p></li><li><p>
196 Place an entry for the machine <code class="constant">sleeth</code> in the <code class="filename">/etc/hosts</code>.
197 The printers are network attached, so there should be entries for the
200 192.168.1.1 sleeth sleeth1
201 192.168.2.1 sleeth2
202 192.168.1.10 hplj6
203 192.168.1.11 hplj4
204 192.168.2.10 qms
205 </pre><p>
206 </p></li><li><p>
207 Install the Samba-3 binary RPM from the Samba-Team FTP site.
208 </p></li><li><p>
209 Install the ISC DHCP server using the UNIX/Linux system tools available to you.
210 </p></li><li><p>
215 Because Samba will be operating over two network interfaces and clients on each side
216 may want to be able to reach clients on the other side, it is imperative that IP forwarding
217 is enabled. Use the system tool of your choice to enable IP forwarding. In the
218 absence of such a tool on the Linux system, add to the <code class="filename">/etc/rc.d/rc.local</code>
219 file an entry as follows:
222 </pre><p>
223 This causes the Linux kernel to forward IP packets so that it acts as a router.
224 </p></li><li><p>
225 Install the <code class="filename">smb.conf</code> file as shown in <a href="small.html#acct2conf" title="Example 2.3. Accounting Office Network smb.conf File [globals] Section">???</a> and
226 <a href="small.html#acct3conf" title="Example 2.4. Accounting Office Network smb.conf File Services and Shares Section">???</a>. Combine these two examples to form a single
228 </p></li><li><p>
233 New SMB password: XXXXXXX
234 Retype new SMB password: XXXXXXX
236 </pre><p>
238 This is the Windows Domain Administrator password. Never delete this account from
239 the password backend after Windows Domain Groups have been initialized. If you delete
240 this account, your system is crippled. You cannot restore this account,
241 and your Samba server can no longer be administered.
242 </p></li><li><p>
244 Create the username map file to permit the <code class="constant">root</code> account to be called
245 <code class="constant">Administrator</code> from the Windows network environment. To do this, create
248 ####
249 # User mapping file
250 ####
251 # File Format
252 # -----------
253 # Unix_ID = Windows_ID
254 #
255 # Examples:
256 # root = Administrator
257 # janes = "Jane Smith"
258 # jimbo = Jim Bones
259 #
260 # Note: If the name contains a space it must be double quoted.
261 # In the example above the name 'jimbo' will be mapped to Windows
262 # user names 'Jim' and 'Bones' because the space was not quoted.
263 #######################################################################
264 root = Administrator
265 ####
266 # End of File
267 ####
268 </pre><p>
269 </p></li><li><p>
271 Create and map Windows Domain Groups to UNIX groups. A sample script is provided in
272 <a href="small.html#initGrps" title="Example 2.1. Script to Map Windows NT Groups to UNIX Groups">???</a>. Create a file containing this script. We called ours
274 and then execute the script. Sample output should be as follows:
276 </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="id2559381"></a><pre class="screen">
277 #!/bin/bash
278 #
279 # initGrps.sh
280 #
282 # Create UNIX groups
283 groupadd acctsdep
284 groupadd finsrvcs
286 # Map Windows Domain Groups to UNIX groups
291 # Add Functional Domain Groups
300 Updated mapping entry for Domain Admins
301 Updated mapping entry for Domain Users
302 Updated mapping entry for Domain Guests
303 No rid or sid specified, choosing algorithmic mapping
304 Successfully added group Accounts Dept to the mapping db
305 No rid or sid specified, choosing algorithmic mapping
306 Successfully added group Domain Guests to the mapping db
324 </pre><p>
325 </p></li><li><p>
329 For each user who needs to be given a Windows Domain account, make an entry in the
331 Use the system tool of your choice to create the UNIX system accounts, and use the Samba
332 <span><strong class="command">smbpasswd</strong></span> program to create the Domain user accounts.
333 </p><p>
337 There are a number of tools for user management under UNIX, such as
338 <span><strong class="command">useradd</strong></span> and <span><strong class="command">adduser</strong></span>, as well as a plethora of custom
339 tools. With the tool of your choice, create a home directory for each user.
340 </p></li><li><p>
341 Using the preferred tool for your UNIX system, add each user to the UNIX groups created
342 previously, as necessary. File system access control will be based on UNIX group membership.
343 </p></li><li><p>
344 Create the directory mount point for the disk subsystem that is mounted to provide
345 data storage for company files. In this case the mount point is indicated in the <code class="filename">smb.conf</code>
346 file is <code class="filename">/data</code>. Format the file system as required, mount the formatted
349 </p></li><li><p>
350 Create the top-level file storage directories are follows:
357 </pre><p>
358 Each department is responsible for creating its own directory structure within its
359 share. The directory root of the <span><strong class="command">accounts</strong></span> share is <code class="filename">/data/accounts</code>.
360 The directory root of the <span><strong class="command">finsvcs</strong></span> share is <code class="filename">/data/finsvcs</code>.
361 </p></li><li><p>
362 Configure the printers with the IP addresses as shown in <a href="small.html#acct2net" title="Figure 2.1. Abmas Accounting 52-User Network Topology">???</a>.
363 Follow the instructions in the manufacturers' manuals to permit printing to port 9100.
364 This allows the CUPS spooler to print using raw mode protocols.
367 </p></li><li><p>
370 Configure the CUPS Print Queues as follows:
375 </pre><p>
377 This creates the necessary print queues with no assigned print filter.
378 </p></li><li><p>
384 application/octet-stream application/vnd.cups-raw 0 -
385 </pre><p>
386 </p></li><li><p>
390 application/octet-stream
391 </pre><p>
392 </p></li><li><p>
394 Using your favorite system editor, create an <code class="filename">/etc/dhcpd.conf</code> with the
395 contents as shown in <a href="small.html#dhcp01" title="Example 2.2. Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf">???</a>.
396 </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="id2559860"></a><pre class="screen">
397 default-lease-time 86400;
398 max-lease-time 172800;
399 default-lease-time 86400;
401 option ntp-servers 192.168.1.1;
402 option domain-name "abmas.biz";
405 option netbios-node-type 8;
406 ### NOTE ###
407 # netbios-node-type=8 means set clients to Hybrid Mode
408 # so they will use Unicast communication with the WINS
409 # server and thus reduce the level of UDP broadcast
410 # traffic by up to 90%.
411 ############
414 range dynamic-bootp 192.168.1.128 192.168.1.254;
415 option subnet-mask 255.255.255.0;
416 option routers 192.168.1.1;
417 allow unknown-clients;
418 host hplj4 {
420 fixed-address 192.168.1.10;
421 }
422 host hplj6 {
424 fixed-address 192.168.1.11;
425 }
426 }
428 range dynamic-bootp 192.168.2.128 192.168.2.254;
429 option subnet-mask 255.255.255.0;
430 option routers 192.168.2.1;
431 allow unknown-clients;
432 host qms {
434 fixed-address 192.168.1.10;
435 }
436 }
438 }
440 </p></li><li><p>
441 Use the standard system tool to start Samba and CUPS and configure them to start
442 automatically at every system reboot. For example,
443 </p><p>
456 </pre><p>
457 </p></li><li><p>
464 Configure the name service switch (NSS) to handle WINS-based name resolution.
465 Since this system does not use a DNS server, it is safe to remove this option from
469 hosts: files wins
470 </pre><p>
471 </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="id2560090"></a><em class="parameter"><code>workgroup = BILLMORE</code></em></td></tr><tr><td><a class="indexterm" name="id2560103"></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="id2560117"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2560130"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2560142"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2560156"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2560168"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2560182"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2560195"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2560208"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2560221"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2560235"></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="id2560248"></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="id2560262"></a><em class="parameter"><code>logon script = scripts\login.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2560275"></a><em class="parameter"><code>logon path = </code></em></td></tr><tr><td><a class="indexterm" name="id2560288"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2560301"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560313"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560326"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560339"></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="id2560385"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2560398"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2560411"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2560423"></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="id2560445"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2560458"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2560471"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560483"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560496"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560509"></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="id2560530"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2560543"></a><em class="parameter"><code>path = /data/%U</code></em></td></tr><tr><td><a class="indexterm" name="id2560556"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2560569"></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="id2560590"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2560603"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2560616"></a><em class="parameter"><code>valid users = %G</code></em></td></tr><tr><td><a class="indexterm" name="id2560629"></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="id2560650"></a><em class="parameter"><code>comment = Financial Service Files</code></em></td></tr><tr><td><a class="indexterm" name="id2560663"></a><em class="parameter"><code>path = /data/finsvcs</code></em></td></tr><tr><td><a class="indexterm" name="id2560676"></a><em class="parameter"><code>valid users = %G</code></em></td></tr><tr><td><a class="indexterm" name="id2560689"></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="id2560702"></a>Validation</h3></div></div></div><p>
472 Does everything function as it ought? That is the key question at this point.
473 Here are some simple steps to validate your Samba server configuration.
474 </p><div class="procedure"><a name="id2560714"></a><p class="title"><b>Procedure 2.2. Validation Steps</b></p><ol type="1"><li><p>
476 If your <code class="filename">smb.conf</code> file has bogus options or parameters, this may cause Samba
477 to refuse to start. The first step should always be to validate the contents
478 of this file by running:
481 Load smb config files from smb.conf
482 Processing section "[homes]"
483 Processing section "[printers]"
484 Processing section "[netlogon]"
485 Processing section "[accounts]"
486 Processing section "[service]"
487 Loaded services file OK.
488 # Global parameters
489 [global]
490 workgroup = BILLMORE
491 passwd chat = *New*Password* \
492 %n\n *Re-enter*new*password* %n\n *Password*changed*
493 username map = /etc/samba/smbusers
494 syslog = 0
495 name resolve order = wins bcast hosts
496 printcap name = CUPS
497 show add printer wizard = No
498 add user script = /usr/sbin/useradd -m '%u'
499 delete user script = /usr/sbin/userdel -r '%u'
500 add group script = /usr/sbin/groupadd '%g'
501 delete group script = /usr/sbin/groupdel '%g'
502 add user to group script = /usr/sbin/usermod -G '%g' '%u'
503 add machine script = /usr/sbin/useradd
504 -s /bin/false -d /var/lib/nobody '%u'
505 logon script = scripts\logon.bat
506 logon path =
507 logon drive = X:
508 domain logons = Yes
509 preferred master = Yes
510 wins support = Yes
511 ...
512 ### Remainder cut to save space ###
513 </pre><p>
514 The inclusion of an invalid parameter (say one called dogbert) would generate an
515 error as follows:
517 Unknown parameter encountered: "dogbert"
518 Ignoring unknown parameter "dogbert"
519 </pre><p>
520 Clear away all errors before proceeding, and start or restart samba as necessary.
521 </p></li><li><p>
526 Check that the Samba server is running:
533 $rootprompt; ps ax | grep winbind
536 </pre><p>
537 The <span><strong class="command">winbindd</strong></span> daemon is running in split mode (normal), so there are also
538 two instances of it. For more information regarding <span><strong class="command">winbindd</strong></span>, see
539 <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 23, Section 23.3. The single instance of
541 </p></li><li><p>
543 Check that an anonymous connection can be made to the Samba server:
547 Sharename Type Comment
548 --------- ---- -------
549 netlogon Disk Network Logon Service
550 accounts Disk Accounting Files
551 finsvcs Disk Financial Service Files
552 IPC$ IPC IPC Service (Samba3)
553 ADMIN$ IPC IPC Service (Samba3)
554 hplj4 Printer Hewlett-Packard LaserJet 4
555 hplj6 Printer Hewlett-Packard LaserJet 6
556 qms Printer QMS Magicolor Laser Printer XXXX
558 Server Comment
559 --------- -------
560 SLEETH Samba 3.0.20
562 Workgroup Master
563 --------- -------
564 BILLMORE SLEETH
565 </pre><p>
566 This demonstrates that an anonymous listing of shares can be obtained. This is the equivalent
567 of browsing the server from a Windows client to obtain a list of shares on the server.
568 The <code class="constant">-U%</code> argument means to send a <code class="constant">NULL</code> username and
570 </p></li><li><p>
574 Verify that the printers have the IP addresses assigned in the DHCP server configuration file.
575 The easiest way to do this is to ping the printer name. Immediately after the ping response
576 has been received, execute <span><strong class="command">arp -a</strong></span> to find the MAC address of the printer
577 that has responded. Now you can compare the IP address and the MAC address of the printer
578 with the configuration information in the <code class="filename">/etc/dhcpd.conf</code> file. They
579 should, of course, match. For example,
587 </pre><p>
589 IP address from which the printer has responded and the entry for it in the
591 </p></li><li><p>
593 Make an authenticated connection to the server using the <span><strong class="command">smbclient</strong></span> tool:
596 Password: XXXXXXX
597 smb: \> dir
607 smb: \> q
608 </pre><p>
609 </p></li></ol></div></div><div class="procedure"><a name="id2561050"></a><p class="title"><b>Procedure 2.3. Windows XP Professional Client Configuration</b></p><ol type="1"><li><p>
610 Configure clients to the network settings shown in <a href="small.html#acct2net" title="Figure 2.1. Abmas Accounting 52-User Network Topology">???</a>.
611 All clients use DHCP for TCP/IP protocol stack configuration.
614 DHCP configures all Windows clients to use the WINS Server address <code class="constant">192.168.1.1</code>.
615 </p></li><li><p>
616 Join the Windows Domain called <code class="constant">BILLMORE</code>. Use the Domain Administrator
618 A detailed step-by-step procedure for joining a Windows 200x/XP Professional client to
619 a Windows Domain is given in <a href="appendix.html" title="Chapter 15. A Collection of Useful Tidbits">???</a>, <a href="appendix.html#domjoin" title="Joining a Domain: Windows 200x/XP Professional">???</a>.
620 Reboot the machine as prompted and then log on using a Domain User account.
621 </p></li><li><p>
626 and that it is possible to open that share to reveal its contents.
627 </p></li><li><p>
628 Instruct all users to log onto the workstation using their assigned username and password.
629 </p></li><li><p>
630 Install a printer on each using the following steps:
632 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>.
634 </p></li><li><p>
639 </p></li><li><p>
642 <span class="guibutton">Next</span>. When asked, “<span class="quote">Would you like to print a
645 </p></li><li><p>
646 You may be prompted for the name of a file to print to. If so, close the
647 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>.
648 </p></li><li><p>
651 Click <span class="guibutton">OK</span>+<span class="guibutton">OK</span> to complete the installation.
652 </p></li><li><p>
653 Repeat the printer installation steps above for the HP LaserJet 6 printer
654 as well as for the QMS Magicolor XXXX laser printer.
655 </p></li></ol></div></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561389"></a>Notebook Computers: A Special Case</h3></div></div></div><p>
656 As a network administrator, you already know how to create local machine accounts for Windows 200x/XP
657 Professional systems. This is the preferred solution to provide continuity of work for notebook users
658 so that absence from the office network environment does not become a barrier to productivity.
659 </p><p>
660 By creating a local machine account that has the same username and password as you create for that
661 user in the Windows Domain environment, the user can log onto the machine locally and still
662 transparently access network resources as if logged onto the domain itself. There are some trade-offs
663 that mean that as the network is more tightly secured, it becomes necessary to modify Windows client
664 configuration somewhat.
665 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561414"></a>Key Points Learned</h3></div></div></div><p>
666 In this network design and implementation exercise, you created a Windows NT4-style Domain
667 Controller using Samba-3.0.20. Following these guidelines, you experienced
668 and implemented several important aspects of Windows networking. In the next chapter,
669 you build on the experience. These are the highlights from this chapter:
672 You implemented a DHCP server, and Microsoft Windows clients were able to obtain all necessary
673 network configuration settings from this server.
674 </p></li><li><p>
676 You created a Windows Domain Controller. You were able to use the network logon service
677 and successfully joined Windows 200x/XP Professional clients to the Domain.
678 </p></li><li><p>
680 You created raw print queues in the CUPS printing system. You maintained a simple
681 printing system so that all users can share centrally managed printers. You installed
682 native printer drivers on the Windows clients.
683 </p></li><li><p>
684 You experienced the benefits of centrally managed user accounts on the server.
685 </p></li><li><p>
686 You offered Mobile notebook users a solution that allows them to continue to work
687 while away from the office and not connected to the corporate network.
688 </p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561490"></a>Questions and Answers</h2></div></div></div><p>
689 Your new Domain Controller is ready to serve you. What does it mean? Here are some questions and answers that
690 may help.
692 What is the key benefit of using DHCP to configure Windows client TCP/IP stacks?
694 Are there any DHCP server configuration parameters in the /etc/dhcpd.conf
695 that should be noted in particular?
697 Is it possible to create a Windows Domain account that is specifically called Administrator?
699 Why is it necessary to give the Windows Domain Administrator a UNIX UID of 0?
701 One of my junior staff needs the ability to add machines to the Domain, but I do not want to give him
702 root access. How can we do this?
704 Why must I map Windows Domain Groups to UNIX groups?
706 I deleted my root account and now I cannot add it back! What can I do?
708 When I run net groupmap list, it reports a group called Administrators
709 as well as Domain Admins. What is the difference between them?
711 What is the effect of changing the name of a Samba server or of changing the Domain name?
713 How can I manage user accounts from my Windows XP Professional workstation?
714 </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="id2561504"></a><a name="id2561506"></a><b>1.</b></td><td align="left" valign="top"><p>
715 What is the key benefit of using DHCP to configure Windows client TCP/IP stacks?
716 </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
717 First and foremost, portability. It means that notebook users can move between
718 the Abmas office and client offices (so long as they, too, use DHCP) without having to manually
719 reconfigure their machines. It also means that when they work from their home environments
720 either using DHCP assigned addressing or when using dial-up networking, settings such as
721 default routes and DNS server addresses that apply only to the Abmas office environment do
722 not interfere with remote operations. This is an extremely important feature of DHCP.
723 </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2561540"></a><a name="id2561542"></a><b>2.</b></td><td align="left" valign="top"><p>
724 Are there any DHCP server configuration parameters in the <code class="filename">/etc/dhcpd.conf</code>
725 that should be noted in particular?
726 </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
727 Yes. The configuration you created automatically provides each client with the IP address
728 of your WINS server. It also configures the client to preferentially register NetBIOS names
729 with the WINS server, and then instructs the client to first query the WINS server when a
730 NetBIOS machine name needs to be resolved to an IP Address. This configuration
731 results in far lower UDP broadcast traffic than would be the case if WINS was not used.
732 </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2561572"></a><a name="id2561574"></a><b>3.</b></td><td align="left" valign="top"><p>
733 Is it possible to create a Windows Domain account that is specifically called <code class="constant">Administrator</code>?
734 </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
735 You can surely create a Windows Domain account called <code class="constant">Administrator</code>. It is also
736 possible to map that account so that it has the effective UNIX UID of 0. This way it isn't
737 necessary to use the <em class="parameter"><code>username map</code></em> facility to map this account to the UNIX
739 </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2561610"></a><a name="id2561613"></a><b>4.</b></td><td align="left" valign="top"><p>
740 Why is it necessary to give the Windows Domain <code class="constant">Administrator</code> a UNIX UID of 0?
741 </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
742 The Windows Domain <code class="constant">Administrator</code> account is the most privileged account that
743 exists on the Windows platform. This user can change any setting, add, delete, or modify user
744 accounts, and completely reconfigure the system. The equivalent to this account in the UNIX
745 environment is the <code class="constant">root</code> account. If you want to permit the Windows Domain
746 Administrator to manage accounts as well as permissions, privileges, and security
747 settings within the Domain and on the Samba server, equivalent rights must be assigned. This is
749 </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2561652"></a><a name="id2561654"></a><b>5.</b></td><td align="left" valign="top"><p>
750 One of my junior staff needs the ability to add machines to the Domain, but I do not want to give him
752 </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
753 Users who are members of the <code class="constant">Domain Admins</code> group can add machines to the
754 Domain. This group is mapped to the UNIX group account called <code class="constant">root</code>
755 (or the equivalent <code class="constant">wheel</code> on some UNIX systems) that has a GID of 0.
756 This must be the primary GID of the account of the user who is a member of the Windows <code class="constant">
757 Domain Admins</code> account.
758 </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2561694"></a><a name="id2561696"></a><b>6.</b></td><td align="left" valign="top"><p>
759 Why must I map Windows Domain Groups to UNIX groups?
760 </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
761 Samba-3 does not permit a Domain Group to become visible to Domain network clients unless the account
762 has a UNIX group account equivalent. The Domain groups that should be given UNIX equivalents are
763 <span class="guimenu">Domain Guests</span>, <span class="guimenu">Domain Users</span>, and <span class="guimenu">Domain Admins</span>.
764 </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2561732"></a><a name="id2561735"></a><b>7.</b></td><td align="left" valign="top"><p>
765 I deleted my <code class="constant">root</code> account and now I cannot add it back! What can I do?
766 </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
767 This is a nasty problem. Fortunately, there is a solution.
769 Back up your existing configuration files in case you need to restore them.
770 </p></li><li><p>
772 </p></li><li><p>
774 </p></li><li><p>
776 </p></li></ol></div></td></tr><tr class="question"><td align="left" valign="top"><a name="id2561805"></a><a name="id2561807"></a><b>8.</b></td><td align="left" valign="top"><p>
777 When I run <span><strong class="command">net groupmap list</strong></span>, it reports a group called <span class="guimenu">Administrators</span>
779 </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
780 The group called <span class="guimenu">Administrators</span> is representative of the same account that would be
781 present as the Local Group account on a Domain Member server or workstation. Samba uses only Domain
782 Groups at this time. A Workstation or Server Local Group has no meaning in a Samba context. This
783 may change at some later date. These accounts are provided only so that security objects are correctly shown.
784 </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2561854"></a><a name="id2561856"></a><b>9.</b></td><td align="left" valign="top"><p>
785 What is the effect of changing the name of a Samba server or of changing the Domain name?
786 </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
787 If you elect to change the name of the Samba server, on restarting <span><strong class="command">smbd</strong></span>,
788 Windows security identifiers are changed. In the case of a standalone server or a Domain Member server,
789 the machine SID is changed. This may break Domain membership. In the case of a change of the Domain name
790 (Workgroup name), the Domain SID is changed. This affects all Domain memberships.
791 </p><p>
792 If it becomes necessary to change either the server name or the Domain name, be sure to back up the respective
793 SID before the change is made. You can back up the SID using the <span><strong class="command">net getlocalsid</strong></span> (Samba-3)
794 or the <span><strong class="command">smbpasswd</strong></span> (Samba-2.2.x). To change the SID, you use the same tool. Be sure
795 to check the man page for this command for detailed instructions regarding the steps involved.
796 </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2561905"></a><a name="id2561907"></a><b>10.</b></td><td align="left" valign="top"><p>
797 How can I manage user accounts from my Windows XP Professional workstation?
798 </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
799 Samba-3 implements a Windows NT4-style security domain architecture. This type of Domain cannot
800 be managed using tools present on a Windows XP Professional installation. You may download from the
801 Microsoft Web site the SRVTOOLS.EXE package. Extract it into the directory from which you wish to use
802 it. This package extracts the tools: <span><strong class="command">User Manager for Domains</strong></span>, <span><strong class="command">Server Manager</strong></span>, and <span><strong class="command">Event
803 Viewer</strong></span>. You may use the <span class="guimenu">User Manager for Domains</span> to manage your Samba-3
804 Domain user and group accounts. Of course, you do need to be logged on as the <code class="constant">Administrator</code>
805 for the Samba-3 Domain. It may help to log on as the <code class="constant">root</code> account.
806 </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="simple.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="secure.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 1. No-Frills Samba Servers </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 3. Secure Office Networking</td></tr></table></div></body></html>