1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
4 <title>No-Frills Samba Servers</title>
6 <?latex \pagenumbering{arabic} ?>
9 This is the start of the real journey toward the successful deployment of Samba. For some this chapter
10 is the end of the road because their needs will have been adequately met. For others, this chapter is
11 the beginning of a journey that will take them well past the contents of this book. This book provides
12 example configurations of, for the greater part, complete networking solutions. The intent of this book
13 is to help you to get your Samba installation working with least amount of pain and aggravation.
17 <title>Introduction</title>
20 This chapter lays the groundwork for understanding the basics of Samba operation.
21 Instead of a bland technical discussion, each principle is demonstrated by way of a
22 real-world scenario for which a working solution<footnote><para>The examples given mirror those documented
23 in The Official Samba-3 HOWTO and Reference Guide (TOSHARG) Chapter 2, Section 2.3.1. You may gain additional
24 insight from the standalone server configurations covered in TOSHARG, sections 2.3.1.2 through 2.3.1.4.
25 </para></footnote> is fully described.
29 The practical exercises take you on a journey through a drafting office, a charity administration
30 office, and an accounting office. You may choose to apply any or all of these exercises to your own environment.
34 Every assignment case can be implemented far more creatively, but remember that the solutions you
35 create are designed to demonstrate a particular solution possibility. With experience, you should
36 find much improved solutions compared with those presented here. By the time you complete this book,
37 you should aim to be a Samba expert, so do attempt to find better solutions and try them as you work your
38 way through the examples.
43 <title>Assignment Tasks</title>
46 Each case presented highlights different aspects of Windows networking for which a simple
47 Samba-based solution can be provided. Each has subtly different requirements taken from real-world cases.
48 The cases are briefly reviewed to cover important points. Instructions are based
49 on the assumption that the official Samba Team RPM package has been installed.
53 This chapter has three assignments built around fictitious companies:
58 <listitem><para>A drafting office</para></listitem>
59 <listitem><para>A charity administration office</para></listitem>
60 <listitem><para>An accounting office</para></listitem>
69 <title>Drafting Office</title>
72 Our fictitious company is called <emphasis>Abmas Design, Inc.</emphasis> This is a three-person
73 computer-aided design (CAD) business that often has more work than can be handled. The
74 business owner hires contract draftspeople from wherever he can. They bring their own
75 notebook computers into the office. There are four permanent drafting machines. Abmas has a
76 collection of over 10 years of plans that must be available for all draftsmen to reference.
77 Abmas hires the services of an experienced network engineer to update the
78 plans that are stored on a central server one day per month. She knows how to upload
79 plans from each machine. The files available from the server must remain read-only.
80 Anyone should be able to access the plans at any time and without barriers or difficulty.
83 <para><indexterm><primary>Red Hat</primary></indexterm>
84 <indexterm><primary>Fedora</primary></indexterm>
85 Mr. Bob Jordan has asked you to install the new server as economically as possible. The central
86 server has a Pentium-IV 1.6GHz CPU, 768MB RAM, a 20GB IDE boot drive, a 160GB IDE second disk
87 to store plans, and a 100-base-T Ethernet card. You have already installed Red Hat Fedora CoreX and
88 have upgraded Samba to version 3.0.20 using the RPM package that is provided from the Samba
89 <ulink url="http://www.samba.org">FTP</ulink> sites. (Note: Fedora CoreX indicates your favorite
94 <primary>consultant</primary>
96 The four permanent drafting machines (Microsoft Windows workstations) have attached printers
97 and plotters that are shared on a peer-to-peer basis by any and all network users. The intent
98 is to continue to share printers in this manner. The three permanent staff work together with
99 all contractors to store all new work on one PC. A daily copy is made of the work storage
100 area to another PC for safekeeping. When the network consultant arrives, the weekly work
101 area is copied to the central server and the files are removed from the main weekly storage
102 machine. The office works best with this arrangement and does not want to change anything.
103 Old habits are too ingrained.
107 <title>Dissection and Discussion</title>
110 <indexterm><primary>file server</primary><secondary>read-only</secondary></indexterm>
111 The requirements for this server installation demand simplicity. An anonymous read-only
112 file server adequately meets all needs. The network consultant determines how
113 to upload all files from the weekly storage area to the server. This installation should
114 focus only on critical aspects of the installation.
118 It is not necessary to have specific users on the server. The site has a method for storing
119 all design files (plans). Each plan is stored in a directory that is named YYYYWW,<footnote><para>
120 This information is given purely as an example of how data may be stored in such a way that it
121 will be easy to locate records at a later date. The example is not meant to imply any instructions
122 that may be construed as essential to the design of the solution; this is something you will almost
123 certainly want to determine for yourself.</para></footnote> where
124 YYYY is the year, and WW is the week of the year. This arrangement allows work to be stored
125 by week of year to preserve the filing technique the site is familiar with.
126 There is also a customer directory that is alphabetically listed. At the top level are 26
127 directories (A-Z), in each is a second-level of directory for the first plus second letters of the name
128 (A-Z); inside each is a directory by the customers' name. Inside each directory is a symbolic
129 link to each design drawing or plan. This way of storing customer data files permits all
130 plans to be located both by customer name and by the date the work was performed, without
131 demanding the disk space that would be needed if a duplicate file copy were to be stored.
132 The share containing the plans is called <emphasis>Plans</emphasis>.
138 <title>Implementation</title>
141 It is assumed that the server is fully installed and ready for installation and
142 configuration of Samba 3.0.20 and any support files needed. All TCP/IP addresses
143 have been hard-coded. In our case the IP address of the Samba server is
144 <constant>192.168.1.1</constant> and the netmask is <constant>255.255.255.0</constant>.
145 The hostname of the server used is <constant>server</constant>.
149 <title>Samba Server Configuration</title>
152 Download the Samba-3 RPM packages for Red Hat Fedora Core2 from the Samba
153 <ulink url="http://www.samba.org">FTP servers.</ulink>
157 <indexterm><primary>RPM</primary><secondary>install</secondary></indexterm>
158 <indexterm><primary>package</primary></indexterm>
159 Install the RPM package using either the Red Hat Linux preferred GUI
160 tool or the <command>rpm</command>:
162 &rootprompt; rpm -Uvh samba-3.0.20-1.i386.rpm
167 Create a mount point for the file system that will be used to store all data files.
168 You can create a directory called <filename>/plans</filename>:
170 &rootprompt; mkdir /plans
171 &rootprompt; chmod 755 /plans
173 The 755 permissions on this directory (mount point) permit the owner to read, write,
174 and execute, and the group and everyone else to read and execute only.
178 <indexterm><primary>file system</primary><secondary>Ext3</secondary></indexterm>
179 Use Red Hat Linux system tools (refer to Red Hat instructions)
180 to format the 160GB hard drive with a suitable file system. An Ext3 file system
181 is suitable. Configure this drive to automatically mount using the <filename>/plans</filename>
182 directory as the mount point.
186 Install the &smb.conf; file shown in <link linkend="draft-smbconf"/> in the
187 <filename>/etc/samba</filename> directory.
189 <smbconfexample id="draft-smbconf">
190 <title>Drafting Office &smb.conf; File</title>
191 <smbconfcomment>Global Parameters</smbconfcomment>
192 <smbconfsection name="[global]"/>
193 <smbconfoption name="workgroup">MIDEARTH</smbconfoption>
194 <smbconfoption name="security">SHARE</smbconfoption>
196 <smbconfsection name="[Plans]"/>
197 <smbconfoption name="path">/plans</smbconfoption>
198 <smbconfoption name="read only">Yes</smbconfoption>
199 <smbconfoption name="guest ok">Yes</smbconfoption>
204 <indexterm><primary>/etc/hosts</primary></indexterm>
205 Verify that the <filename>/etc/hosts</filename> file contains the following entry:
215 <indexterm><primary>samba</primary><secondary>starting samba</secondary></indexterm>
216 <indexterm><primary>chkconfig</primary></indexterm>
217 <indexterm><primary>starting samba</primary></indexterm>
218 Use the standard system tool to start Samba and to configure it to restart
219 automatically at every system reboot. For example,
221 &rootprompt; chkconfig smb on
222 &rootprompt; /etc/rc.d/init.d/smb restart
229 <title>Windows Client Configuration</title>
232 Make certain that all clients are set to the same network address range as
233 used for the Samba server. For example, one client might have an IP
234 address 192.168.1.10.
238 <indexterm><primary>netmask</primary></indexterm>
239 Ensure that the netmask used on the Windows clients matches that used
240 for the Samba server. All clients must have the same netmask, such as
245 <indexterm><primary>workgroup</primary></indexterm>
246 Set the workgroup name on all clients to <constant>MIDEARTH</constant>.
250 Verify on each client that the machine called <constant>SERVER</constant>
251 is visible in the <guimenu>Network Neighborhood</guimenu>, that it is
252 possible to connect to it and see the share <guimenuitem>Plans</guimenuitem>,
253 and that it is possible to open that share to reveal its contents.
260 <sect3 id="validate1">
261 <title>Validation</title>
264 <indexterm><primary>validation</primary></indexterm>
265 The first priority in validating the new Samba configuration should be to check
266 that Samba answers on the loop-back interface. Then it is time to check that Samba
267 answers its own name correctly. Last, check that a client can connect to the Samba
273 <indexterm><primary>smbd</primary></indexterm>
274 <indexterm><primary>daemon</primary></indexterm>
275 <indexterm><primary>smbclient</primary></indexterm>
276 To check the ability to access the <command>smbd</command> daemon
277 services, execute the following:
279 &rootprompt; smbclient -L localhost -U%
280 Sharename Type Comment
281 --------- ---- -------
283 IPC$ IPC IPC Service (Samba 3.0.20)
284 ADMIN$ IPC IPC Service (Samba 3.0.20)
294 <indexterm><primary>loopback</primary></indexterm>
295 <indexterm><primary>NULL connection</primary></indexterm>
296 This indicates that Samba is able to respond on the loopback interface to
297 a NULL connection. The <parameter>-U%</parameter> means send an empty
298 username and an empty password. This command should be repeated after
299 Samba has been running for 15 minutes.
303 Now verify that Samba correctly handles being passed a username
304 and password, and that it answers its own name. Execute the following:
306 &rootprompt; smbclient -L server -Uroot%password
308 The output should be identical to the previous response. Samba has been
309 configured to ignore all usernames given; instead it uses the
310 <parameter>guest account</parameter> for all connections.
314 <indexterm><primary>Windows Explorer</primary></indexterm>
315 <indexterm><primary>Network Neighborhood</primary></indexterm>
316 From the Windows 9x/Me client, launch Windows Explorer:
318 <guiicon>[Desktop: right-click] Network Neighborhood</guiicon>
319 <guimenu>Explore</guimenu>
320 <guimenuitem>[Left Panel] [+] Entire Network</guimenuitem>
321 <guimenuitem>[Left Panel] [+] Server</guimenuitem>
322 <guimenuitem>[Left Panel] [+] Plans</guimenuitem>
323 </menuchoice>. In the right panel you should see the files and directories
324 (folders) that are in the <guiicon>Plans</guiicon> share.
333 <title>Charity Administration Office</title>
336 The fictitious charity organization is called <emphasis>Abmas Vision NL</emphasis>. This office
337 has five networked computers. Staff are all volunteers, staff changes are frequent.
338 Ms. Amy May, the director of operations, wants a no-hassle network. Anyone should be able to
339 use any PC. Only two Windows applications are used: a custom funds tracking and management package
340 that stores all files on the central server and Microsoft Word. The office prepares mail-out
341 letters, invitations, and thank-you notes. All files must be stored in perpetuity.
342 The custom funds tracking and management (FTM) software is configured to use a server named
343 <constant>SERVER</constant>, a share named <constant>FTMFILES</constant>, and a printer queue
344 named <constant>PRINTQ</constant> that uses preprinted stationery, thus demanding a
345 dedicated printer. This printer does not need to be mapped to a local printer on the workstations.
349 The FTM software has been in use since the days of Windows 3.11. The software was configured
350 by the vendor who has since gone out of business. The identities of the file
351 server and the printer are hard-coded in a configuration file that was created using a
352 setup tool that the vendor did not provide to Abmas Vision NL or to its predecessors. The
353 company that produced the software is no longer in business. In order to avoid risk of
354 any incompatibilities, the share name and the name of the target print queue must be set
355 precisely as the application expects. In fact, share names and print queue names
356 should be treated as case insensitive (i.e., case does not matter), but Abmas Vision advises
357 that if the share name is not in lowercase, the application claims it cannot find the
362 <indexterm><primary>print queue</primary></indexterm>
363 <indexterm><primary>print spooler</primary></indexterm>
364 Printer handling in Samba results in a significant level of confusion. Samba presents to the
365 MS Windows client only a print queue. The Samba <command>smbd</command> process passes a
366 print job sent to it from the Windows client to the native UNIX printing system. The native
367 UNIX printing system (spooler) places the job in a print queue from which it is
368 delivered to the printer. In this book, network diagrams refer to a printer by the name
369 of the print queue that services that printer. It does not matter what the fully qualified
370 name (or the hostname) of a network-attached printer is. The UNIX print spooler is configured
371 to correctly deliver all jobs to the printer.
375 This organization has a policy forbidding use of privately owned computers on site as a measure
376 to prevent leakage of confidential information. Only the five PCs owned by Abmas Vision NL are
377 used on this network.
381 <indexterm><primary>SUSE Enterprise Linux Server</primary></indexterm>
382 The central server was donated by a local computer store. It is a dual processor Pentium-III
383 server, has 1GB RAM, a 3-Ware IDE RAID Controller that has four 200GB IDE hard drives, and a
384 100-base-T network card. The office has 100-base-T permanent network connections that go to
385 a central hub, and all equipment is new. The five network computers all are equipped with Microsoft
386 Windows Me. Funding is limited, so the server has no operating system on it. You have approval
387 to install Samba on Linux, provided it works without problems. There are two HP LaserJet
388 5 PS printers that are network connected. The second printer is to be used for general
389 office and letter printing. Your recommendation to allow only the Linux server to print directly
390 to the printers was accepted. You have supplied SUSE Enterprise Linux Server 9 and
391 have upgraded Samba to version 3.0.20.
395 <title>Dissection and Discussion</title>
398 <indexterm><primary>force user</primary></indexterm>
399 <indexterm><primary>nt acl support</primary></indexterm>
400 <indexterm><primary>UID</primary></indexterm>
401 <indexterm><primary>Posix</primary></indexterm>
402 This installation demands simplicity. Frequent turnover of volunteer staff indicates that
403 a network environment that requires users to logon might be problematic. It is suggested that the
404 best solution for this office would be one where the user can log onto any PC with any username
405 and password. Samba can accommodate an office like this by using the <parameter>force user</parameter>
406 parameter in share and printer definitions. Using the <parameter>force user</parameter>
407 parameter ensures that all files are owned by same user identifier (UID) and thus that there
408 will never be a problem with file access due to file access permissions. Additionally, you elect
409 to use the <parameter>nt acl support = No</parameter> option to ensure that
410 access control lists (Posix type) cannot be written to any file or directory. This prevents
411 an inadvertent ACL from overriding actual file permissions.
415 <indexterm><primary>SUID</primary></indexterm>
416 <indexterm><primary>SGID</primary></indexterm>
417 <indexterm><primary>security</primary><secondary>share mode</secondary></indexterm>
418 This organization is a prime candidate for Share Mode security. The <parameter>force user</parameter>
419 allows all files to be owned by the same user and group. In addition, it would not hurt to
420 set SUID and set SGID shared directories. This means that all new files that are created, no matter
421 who creates it, are owned by the owner or group of the directory in which they are created.
422 For further information regarding the significance of the SUID/SGID settings, see Appendix A,
423 <link linkend="ch12-SUIDSGID"/>.
427 <indexterm><primary>CUPS</primary></indexterm>
428 <indexterm><primary>printing</primary><secondary>raw</secondary></indexterm>
429 <indexterm><primary>Red Hat Linux</primary></indexterm>
430 <indexterm><primary>SUSE Linux</primary></indexterm>
431 All client workstations print to a print queue on the server. This ensures that print jobs
432 continue to print in the event that a user shuts down the workstation immediately after
433 sending a job to the printer. Today, both Red Hat Linux and SUSE Linux use CUPS-based printing.
434 Older Linux systems offered a choice between the LPRng printing system or CUPS. It appears, however,
435 that CUPS has become the leading UNIX printing technology.
439 <indexterm><primary>print queue</primary></indexterm>
440 The print queues are set up as <constant>Raw</constant> devices, which means that CUPS will
441 not do intelligent print processing, and vendor-supplied drivers must be installed locally on the
446 The hypothetical software, FTM, is representative of
447 custom-built software that directly uses a NetBIOS interface. Most such software originated in
448 the days of MS/PC DOS. NetBIOS names are uppercase (and functionally are case insensitive),
449 so some old software applications would permit only uppercase names to be entered.
450 Some such applications were later ported to MS Windows but retain the uppercase network
451 resource naming conventions because customers are familiar with that. We made the decision
452 to name shares and print queues for this application in uppercase for the same reason.
453 Nothing would break if we were to use lowercase names, but that decision might create a need
454 to retrain staff &smbmdash; something well avoided at this time.
458 NetBIOS networking does not print directly to a printer. Instead, all printing is done to a
459 print queue. The print spooling system is responsible for communicating with the physical
460 printer. In this example, therefore, the resource called <constant>PRINTQ</constant>
461 really is just a print queue. The name of the print queue is representative of
462 the device to which the print spooler delivers print jobs.
468 <title>Implementation</title>
471 It is assumed that the server is fully installed and ready for configuration of
472 Samba 3.0.20 and for necessary support files. All TCP/IP addresses should be hard-coded.
473 In our case, the IP address of the Samba server is 192.168.1.1 and the netmask is
474 255.255.255.0. The hostname of the server used is <constant>server</constant>.
475 The office network is built as shown in <link linkend="charitynet"/>.
478 <image id="charitynet">
479 <imagedescription>Charity Administration Office Network</imagedescription>
480 <imagefile scale="80">Charity-Network</imagefile>
486 <title>Samba Server Configuration</title>
489 <indexterm><primary>groupadd</primary></indexterm>
490 Create a group account for office file storage:
492 &rootprompt; groupadd office
497 <indexterm><primary>useradd</primary></indexterm>
498 <indexterm><primary>passwd</primary></indexterm>
499 Create a user account for office file storage:
501 &rootprompt; useradd -m abmas
502 &rootprompt; passwd abmas
503 Changing password for abmas.
504 New password: XXXXXXXX
505 Re-enter new password: XXXXXXXX
508 where XXXXXXXX is a secret password.
512 Use the 3-Ware IDE RAID Controller firmware utilities to configure the four 200GB
513 drives as a single RAID level 5 drive, with one drive set aside as the hot spare.
514 (Refer to the 3-Ware RAID Controller Manual for the manufacturer's preferred procedure.)
515 The resulting drive has a capacity of approximately 500GB of usable space.
519 <indexterm><primary>permissions</primary></indexterm>
520 Create a mount point for the file system that can be used to store all data files.
521 Create a directory called <filename>/data</filename>:
523 &rootprompt; mkdir /data
524 &rootprompt; chmod 755 /data
526 The 755 permissions on this directory (mount point) permit the owner to read, write, and execute,
527 and the group and everyone else to read and execute only.
531 Use SUSE Linux system tools (refer to the SUSE Administrators Guide for correct
532 procedures) to format the partition with a suitable file system. The reiserfs file system
533 is suitable. Configure this drive to automount using the <filename>/data</filename>
534 directory as the mount point. It must be mounted before proceeding.
538 Under the directory called <filename>/data</filename>, create two directories
539 named <filename>ftmfiles</filename> and <filename>officefiles</filename>, and set
540 ownership and permissions:
542 &rootprompt; mkdir -p /data/{ftmfiles,officefiles/{letters,invitations,misc}}
543 &rootprompt; chown -R abmas:office /data
544 &rootprompt; chmod -R ug+rwxs,o-w,o+rx /data
546 These demonstrate compound operations. The <command>mkdir</command> command
547 creates in one step these directories:
551 /data/officefiles/letters
552 /data/officefiles/invitations
553 /data/officefiles/misc
555 <indexterm><primary>TOSHARG</primary></indexterm>
556 The <command>chown</command> operation sets the owner to the user <constant>abmas</constant>
557 and the group to <constant>office</constant> on all directories just created. It recursively
558 sets the permissions so that the owner and group have SUID/SGID with read, write, and execute
559 permission, and everyone else has read and execute permission. This means that all files and
560 directories are created with the same owner and group as the directory in which they are
561 created. Any new directories created still have the same owner, group, and permissions as the
562 directory they are in. This should eliminate all permissions-based file access problems. For
563 more information on this subject, refer to TOSHARG<footnote>The Official Samba-3 HOWTO and
564 Reference Guide, Chapter 15, File, Directory and Share Access Controls.</footnote> or refer
565 to the UNIX man page for the <command>chmod</command> and the <command>chown</command> commands.
569 Install the &smb.conf; file shown in <link linkend="charity-smbconfnew"/> in the
570 <filename>/etc/samba</filename> directory. This newer &smb.conf; file uses user-mode security
571 and is more suited to the mode of operation of Samba-3 that the older share-mode security
572 configuration that was shown in the first edition of this book.
576 Note: If you want to use the older style configuration that uses share-mode security, you
577 can install the file shown in <link linkend="charity-smbconf"/> in the
578 <filename>/etc/samba</filename> directory.
582 <indexterm><primary>smbd</primary></indexterm>
583 We must ensure that the <command>smbd</command> can resolve the name of the Samba
584 server to its IP address. Verify that the <filename>/etc/hosts</filename> file
585 contains the following entry:
592 Configure the printers with the IP address as shown in <link linkend="charitynet"/>.
593 Follow the instructions in the manufacturer's manual to permit printing to port 9100
594 so that the CUPS spooler can print using raw mode protocols.
598 <indexterm><primary>lpadmin</primary></indexterm>
599 Configure the CUPS Print Queues:
601 &rootprompt; lpadmin -p PRINTQ -v socket://192.168.1.20:9100 -E
602 &rootprompt; lpadmin -p hplj5 -v socket://192.168.1.30:9100 -E
604 This creates the necessary print queues with no assigned print filter.
608 <indexterm><primary>mime type</primary></indexterm>
609 <indexterm><primary>/etc/cups/mime.convs</primary></indexterm>
610 <indexterm><primary>application/octet-stream</primary></indexterm>
611 Edit the file <filename>/etc/cups/mime.convs</filename> to uncomment the line:
613 application/octet-stream application/vnd.cups-raw 0 -
618 <indexterm><primary>/etc/cups/mime.types</primary></indexterm>
619 Edit the file <filename>/etc/cups/mime.types</filename> to uncomment the line:
621 application/octet-stream
626 <indexterm><primary>starting samba</primary></indexterm>
627 Use the standard system tool to start Samba and CUPS to configure them to restart
628 automatically at every system reboot. For example,
632 <indexterm><primary>starting samba</primary></indexterm>
633 <indexterm><primary>starting CUPS</primary></indexterm>
634 <indexterm><primary>chkconfig</primary></indexterm>
636 &rootprompt; chkconfig smb on
637 &rootprompt; chkconfig cups on
638 &rootprompt; /etc/rc.d/init.d/smb restart
639 &rootprompt; /etc/rc.d/init.d/cups restart
645 <smbconfexample id="charity-smbconfnew">
646 <title>Charity Administration Office &smb.conf; File</title>
647 <smbconfcomment>Global Parameters - Newer Configuration</smbconfcomment>
648 <smbconfsection name="[global]"/>
649 <smbconfoption name="workgroup">MIDEARTH</smbconfoption>
650 <smbconfoption name="printing">CUPS</smbconfoption>
651 <smbconfoption name="printcap name">CUPS</smbconfoption>
652 <smbconfoption name="map to guest">Bad User</smbconfoption>
653 <smbconfoption name="show add printer wizard">No</smbconfoption>
654 <smbconfoption name="wins support">yes</smbconfoption>
656 <smbconfsection name="[FTMFILES]"/>
657 <smbconfoption name="comment">Funds Tracking & Management Files</smbconfoption>
658 <smbconfoption name="path">/data/ftmfiles</smbconfoption>
659 <smbconfoption name="read only">No</smbconfoption>
660 <smbconfoption name="force user">abmas</smbconfoption>
661 <smbconfoption name="force group">office</smbconfoption>
662 <smbconfoption name="guest ok">Yes</smbconfoption>
663 <smbconfoption name="nt acl support">No</smbconfoption>
665 <smbconfsection name="[office]"/>
666 <smbconfoption name="comment">General Office Files</smbconfoption>
667 <smbconfoption name="path">/data/officefiles</smbconfoption>
668 <smbconfoption name="read only">No</smbconfoption>
669 <smbconfoption name="force user">abmas</smbconfoption>
670 <smbconfoption name="force group">office</smbconfoption>
671 <smbconfoption name="guest ok">Yes</smbconfoption>
672 <smbconfoption name="nt acl support">No</smbconfoption>
674 <smbconfsection name="[printers]"/>
675 <smbconfoption name="comment">Print Temporary Spool Configuration</smbconfoption>
676 <smbconfoption name="path">/var/spool/samba</smbconfoption>
677 <smbconfoption name="printable">Yes</smbconfoption>
678 <smbconfoption name="guest ok">Yes</smbconfoption>
679 <smbconfoption name="use client driver">Yes</smbconfoption>
680 <smbconfoption name="browseable">No</smbconfoption>
683 <smbconfexample id="charity-smbconf">
684 <title>Charity Administration Office &smb.conf; File</title>
685 <smbconfcomment>Global Parameters - Older Style Configuration</smbconfcomment>
686 <smbconfsection name="[global]"/>
687 <smbconfoption name="workgroup">MIDEARTH</smbconfoption>
688 <smbconfoption name="security">SHARE</smbconfoption>
689 <smbconfoption name="printing">CUPS</smbconfoption>
690 <smbconfoption name="printcap name">CUPS</smbconfoption>
691 <smbconfoption name="disable spoolss">Yes</smbconfoption>
692 <smbconfoption name="show add printer wizard">No</smbconfoption>
693 <smbconfoption name="wins support">yes</smbconfoption>
695 <smbconfsection name="[FTMFILES]"/>
696 <smbconfoption name="comment">Funds Tracking & Management Files</smbconfoption>
697 <smbconfoption name="path">/data/ftmfiles</smbconfoption>
698 <smbconfoption name="read only">No</smbconfoption>
699 <smbconfoption name="force user">abmas</smbconfoption>
700 <smbconfoption name="force group">office</smbconfoption>
701 <smbconfoption name="guest ok">Yes</smbconfoption>
702 <smbconfoption name="nt acl support">No</smbconfoption>
704 <smbconfsection name="[office]"/>
705 <smbconfoption name="comment">General Office Files</smbconfoption>
706 <smbconfoption name="path">/data/officefiles</smbconfoption>
707 <smbconfoption name="read only">No</smbconfoption>
708 <smbconfoption name="force user">abmas</smbconfoption>
709 <smbconfoption name="force group">office</smbconfoption>
710 <smbconfoption name="guest ok">Yes</smbconfoption>
711 <smbconfoption name="nt acl support">No</smbconfoption>
713 <smbconfsection name="[printers]"/>
714 <smbconfoption name="comment">Print Temporary Spool Configuration</smbconfoption>
715 <smbconfoption name="path">/var/spool/samba</smbconfoption>
716 <smbconfoption name="printable">Yes</smbconfoption>
717 <smbconfoption name="guest ok">Yes</smbconfoption>
718 <smbconfoption name="use client driver">Yes</smbconfoption>
719 <smbconfoption name="browseable">No</smbconfoption>
723 <title>Windows Client Configuration</title>
726 Configure clients to the network settings shown in <link linkend="charitynet"/>.
730 Ensure that the netmask used on the Windows clients matches that used
731 for the Samba server. All clients must have the same netmask, such as
732 <constant>255.255.255.0</constant>.
736 <indexterm><primary>WINS</primary></indexterm>
737 On all Windows clients, set the WINS Server address to <constant>192.168.1.1</constant>,
738 the IP address of the server.
742 Set the workgroup name on all clients to <constant>MIDEARTH</constant>.
746 <indexterm><secondary>logon</secondary></indexterm>
747 Install the <quote>Client for Microsoft Networks.</quote> Ensure that the only option
748 enabled in its properties is the option <quote>Logon and restore network connections.</quote>
752 Click <guibutton>OK</guibutton> when you are prompted to reboot the system. Reboot the
753 system, then log on using any username and password you choose.
757 <indexterm><primary>My Network Places</primary></indexterm>
758 Verify on each client that the machine called <constant>SERVER</constant>
759 is visible in <guimenu>My Network Places</guimenu>, that it is
760 possible to connect to it and see the share <guimenuitem>office</guimenuitem>,
761 and that it is possible to open that share to reveal its contents.
765 <indexterm><primary>password caching</primary></indexterm>
766 <indexterm><primary>regedit</primary></indexterm>
767 Disable password caching on all Windows 9x/Me machines using the registry change file
768 shown in <link linkend="MEreg"/>. Be sure to remove all files that have the
769 <filename>PWL</filename> extension that are in the <filename>C:\WINDOWS</filename>
772 <title>Windows Me &smbmdash; Registry Edit File: Disable Password Caching</title>
776 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
777 Windows\CurrentVersion\Policies\Network]
778 "DisablePwdCaching"=dword:00000001
781 The best way to apply this change is to save the patch in a file called
782 <filename>ME-dpwc.reg</filename> and then execute:
784 C:\WINDOWS: regedit ME-dpwc.reg
789 Instruct all users to log onto the workstation using a name and password of their own
790 choosing. The Samba server has been
791 configured to ignore the username and password given.
795 On each Windows Me workstation, configure a network drive mapping to drive <filename>G:</filename>
796 that redirects to the uniform naming convention (UNC) resource
797 <filename>\\server\office</filename>. Make this a permanent drive connection:
802 Right-click <guimenu>My Network</guimenu>
803 <guimenuitem>Map Network Drive...</guimenuitem>
808 In the box labeled <quote>Drive:</quote>, type G.
812 In the box labeled <quote>Path:</quote>, enter
813 <filename>\\server\officefiles</filename>.
817 Click <guimenuitem>Reconnect at logon</guimenuitem>.
818 Click <guibutton>OK</guibutton>.
825 On each workstation, install the FTM software following the
826 manufacturer's instructions.
830 During installation, you are prompted for the name of the Windows 98
831 server. Enter the name <constant>SERVER</constant>.
834 You are prompted for the name of the data share.
835 The prompt defaults to <constant>FTMFILES</constant>. Press enter to accept the default value.
838 You are now prompted for the print queue name. The default prompt is the name of
839 the server you entered (<constant>SERVER</constant> as follows:
840 <constant>\\SERVER\PRINTQ</constant>). Simply accept the default and press enter to
841 continue. The software now completes the installation.
847 Install an office automation software package of the customer's choice. Either Microsoft
848 Office 2003 Standard or OpenOffice 1.1.0 suffices for any functions the office may
849 need to perform. Repeat this on each workstation.
853 Install a printer on each workstation using the following steps:
859 <guimenu>Start</guimenu>
860 <guimenuitem>Settings</guimenuitem>
861 <guimenuitem>Printers</guimenuitem>
862 <guiicon>Add Printer</guiicon>
863 <guibutton>Next</guibutton>
864 </menuchoice>. Do not click <guimenuitem>Network printer</guimenuitem>.
865 Ensure that <guimenuitem>Local printer</guimenuitem> is selected.
869 Click <guibutton>Next</guibutton>. In the Manufacturer: panel, select
870 <constant>HP</constant>. In the Printers: panel, select the printer called
871 <constant>HP LaserJet 5/5M Postscript</constant>. Click <guibutton>Next</guibutton>.
875 In the Available ports: panel, select <constant>FILE:</constant>. Accept the
876 default printer name by clicking <guibutton>Next</guibutton>. When asked,
877 <quote>Would you like to print a test page?</quote>, click
878 <guimenuitem>No</guimenuitem>. Click <guibutton>Finish</guibutton>.
882 You may be prompted for the name of a file to print to. If so, close the
883 dialog panel. Right-click <menuchoice>
884 <guiicon>HP LaserJet 5/5M Postscript</guiicon>
885 <guimenuitem>Properties</guimenuitem>
886 <guisubmenu>Details (Tab)</guisubmenu>
887 <guimenuitem>Add Port</guimenuitem>
892 In the Network panel, enter the name of
893 the print queue on the Samba server as follows: <constant>\\SERVER\hplj5</constant>.
895 <guibutton>OK</guibutton>
896 <guibutton>OK</guibutton>
897 </menuchoice> to complete the installation.
901 It is a good idea to test the functionality of the complete installation before
902 handing the newly configured network over to the Charity Administration Office
915 <title>Validation</title>
918 Use the same validation process as was followed in <link linkend="validate1"/>.
925 <sect2 id="AccountingOffice">
926 <title>Accounting Office</title>
929 Abmas Accounting is a 40-year-old family-run business. There are nine permanent
930 computer users. The network clients were upgraded two years ago. All computers run Windows 2000
931 Professional. This year the server will be upgraded from an old Windows NT4 server (actually
932 running Windows NT4 Workstation, which worked fine for fewer than 10 users) that has
933 run in workgroup (standalone) mode, to a new Linux server running Samba.
937 The office does not want a Domain Server. Mr. Alan Meany wants to keep the Windows 2000 Professional
938 clients running as workgroup machines so that any staff member can take a machine home and keep
939 working. It has worked well so far, and your task is to replace the old server. All users have
940 their own workstation logon (you configured it that way when the machines were installed).
941 Mr. Meany wants the new system to operate the same way as the old Windows NT4 server &smbmdash; users
942 cannot access each others' files, but he can access everyone's files. Each person's work files are
943 in a separate share on the server. Users log on to their Windows workstation with their username
944 and enter an assigned password; they do not need to enter a password when accessing their files
949 <indexterm><primary>Red Hat Linux</primary></indexterm>
950 The new server will run Red Hat Fedora Core2. You should install Samba-3.0.20 and
951 copy all files from the old system to the new one. The existing Windows NT4 server has a parallel
952 port HP LaserJet 4 printer that is shared by all. The printer driver is installed on each
953 workstation. You must not change anything on the workstations. Mr. Meany gave instructions to
954 replace the server, <quote>but leave everything else alone to avoid staff unrest.</quote>
958 You have tried to educate Mr. Meany and found that he has no desire to understand networking.
959 He believes that Windows for Workgroups 3.11 was <quote>the best server Microsoft ever sold
960 </quote> and that Windows NT and 2000 are <quote>too fang-dangled complex!</quote>
964 <title>Dissection and Discussion</title>
967 <indexterm><primary>security</primary><secondary>user mode</secondary></indexterm>
968 The requirements of this network installation are not unusual. The staff are not interested in the
969 details of networking. Passwords are never changed. In this example solution, we demonstrate the use
970 of User Mode security in a simple context. Directories should be set SGID to ensure that members
971 of a common group can access the contents. Each user has his or her own share to which only they
972 can connect. Mr. Meany's share will be a top-level directory above the share point for each employee.
973 Mr. Meany is a member of the same group as his staff and can access their work files.
974 The well-used HP LaserJet 4 is available as a service called <constant>hplj</constant>.
978 You have finished configuring the new hardware and have just completed installation of Red Hat
979 Fedora Core2. Roll up your sleeves and let's get to work.
984 <sect3 id="AcctgNet">
985 <title>Implementation</title>
988 The workstations have fixed IP addresses. The old server runs Windows NT4 Workstation, so it
989 cannot be running as a WINS server. It is best that the new configuration preserves the same
990 configuration. The office does not use Internet access, so security really is not an issue.
994 The core information regarding the users, their passwords, the directory share point, and the
995 share name is given in <link linkend="acctingnet"/>. The overall network topology is shown in
996 <link linkend="acctingnet2"/>. All machines have been configured as indicated prior to the
997 start of Samba configuration. The following prescriptive steps may now commence.
1000 <image id="acctingnet2">
1001 <imagedescription>Accounting Office Network Topology</imagedescription>
1002 <imagefile scale="85">AccountingNetwork</imagefile>
1005 <table id="acctingnet">
1006 <title>Accounting Office Network Information</title>
1008 <colspec align="left"/>
1009 <colspec align="left"/>
1010 <colspec align="left"/>
1011 <colspec align="left"/>
1012 <colspec align="left"/>
1013 <colspec align="left"/>
1017 <entry>Login-ID</entry>
1018 <entry>Password</entry>
1019 <entry>Share Name</entry>
1020 <entry>Directory</entry>
1026 <entry>Alan Meany</entry>
1028 <entry>alm1961</entry>
1030 <entry>/data</entry>
1034 <entry>James Meany</entry>
1035 <entry>james</entry>
1036 <entry>jimm1962</entry>
1037 <entry>james</entry>
1038 <entry>/data/james</entry>
1042 <entry>Jeannie Meany</entry>
1043 <entry>jeannie</entry>
1044 <entry>jema1965</entry>
1045 <entry>jeannie</entry>
1046 <entry>/data/jeannie</entry>
1050 <entry>Suzy Millicent</entry>
1052 <entry>suzy1967</entry>
1054 <entry>/data/suzy</entry>
1058 <entry>Ursula Jenning</entry>
1060 <entry>ujen1974</entry>
1061 <entry>ursula</entry>
1062 <entry>/data/ursula</entry>
1066 <entry>Peter Pan</entry>
1067 <entry>peter</entry>
1068 <entry>pete1984</entry>
1069 <entry>peter</entry>
1070 <entry>/data/peter</entry>
1074 <entry>Dale Roland</entry>
1076 <entry>dale1986</entry>
1078 <entry>/data/dale</entry>
1082 <entry>Bertrand E Paoletti</entry>
1084 <entry>eric1993</entry>
1086 <entry>/data/eric</entry>
1090 <entry>Russell Lewis</entry>
1092 <entry>russ2001</entry>
1093 <entry>russell</entry>
1094 <entry>/data/russell</entry>
1104 <title>Migration from Windows NT4 Workstation System to Samba-3</title>
1106 <step><para><indexterm>
1107 <primary>migration</primary>
1109 Rename the old server from <constant>CASHPOOL</constant> to <constant>STABLE</constant>
1110 by logging onto the console as the <constant>Administrator</constant>. Restart the machine
1111 following system prompts.
1115 Name the new server <constant>CASHPOOL</constant> using the standard configuration method.
1116 Restart the machine following system prompts.
1120 Install the latest Samba-3 binary Red Hat Linux RPM that is available from the
1125 <indexterm><primary>group account</primary></indexterm>
1126 <indexterm><primary>groupadd</primary></indexterm>
1127 Add a group account for the office to use. Execute the following:
1129 &rootprompt; groupadd accts
1134 Install the &smb.conf; file shown<footnote><para>This example uses the
1135 <parameter>smbpasswd</parameter> file in an obtuse way, since the use of
1136 the <parameter>passdb backend</parameter> has not been specified in the &smb.conf;
1137 file. This means that you are depending on correct default behavior.</para></footnote>
1138 in <link linkend="acctconf"/>.
1142 <indexterm><primary>useradd</primary></indexterm>
1143 <indexterm><primary>passwd</primary></indexterm>
1144 <indexterm><primary>smbpasswd</primary></indexterm>
1145 For each user who uses this system (see <link linkend="acctingnet"/>),
1146 execute the following:
1148 &rootprompt; useradd -m -G accts -c "Name of User" "LoginID"
1149 &rootprompt; passwd "LoginID"
1150 Changing password for user "LoginID"
1151 New Password: XXXXXXXXX <-- the password from the table
1152 Retype new password: XXXXXXXXX
1153 &rootprompt; smbpasswd -a "LoginID"
1154 New SMB password: XXXXXXXXX <-- the password from the table
1155 Retype new SMB password: XXXXXXXXX
1156 Added user "LoginID"
1161 <indexterm><primary>data storage</primary></indexterm>
1162 Create the directory structure for the file shares by executing the following:
1164 &rootprompt; mkdir -p /data
1165 &rootprompt; chown alan /data
1166 &rootprompt; for i in james suzy ursula peter dale eric jeannie russell
1171 &rootprompt; chgrp -R accts /data
1172 &rootprompt; chmod -R ug+rwxs,o-r+x /data
1174 The data storage structure is now prepared for use.
1178 <indexterm><primary>lpadmin</primary></indexterm>
1179 Configure the CUPS Print Queues:
1181 &rootprompt; lpadmin -p hplj -v parallel:/dev/lp0 -E
1183 This creates the necessary print queues with no assigned print filter.
1187 <indexterm><primary>mime types</primary></indexterm>
1188 <indexterm><primary>/etc/cups/mime.convs</primary></indexterm>
1189 Edit the file <filename>/etc/cups/mime.convs</filename> to uncomment the line:
1191 application/octet-stream application/vnd.cups-raw 0 -
1196 <indexterm><primary>/etc/cups/mime.types</primary></indexterm>
1197 <indexterm><primary>application/octet-stream</primary></indexterm>
1198 Edit the file <filename>/etc/cups/mime.types</filename> to uncomment the line:
1200 application/octet-stream
1205 <indexterm><primary>starting samba</primary></indexterm>
1206 Use the standard system tool to start Samba and CUPS to configure them to restart
1207 automatically at every system reboot. For example,
1211 <indexterm><primary>starting samba</primary></indexterm>
1212 <indexterm><primary>startingCUPS</primary></indexterm>
1213 <indexterm><primary>chkconfig</primary></indexterm>
1215 &rootprompt; chkconfig smb on
1216 &rootprompt; chkconfig cups on
1217 &rootprompt; /etc/rc.d/init.d/smb restart
1218 &rootprompt; /etc/rc.d/init.d/cups restart
1223 On Alan's workstation, use Windows Explorer to migrate the files from the old server
1224 to the new server. The new server should appear in the <guimenu>Network Neighborhood</guimenu>
1225 with the name of the old server (<constant>CASHPOOL</constant>).
1231 Log on to Alan's workstation as the user <constant>alan</constant>.
1235 Launch a second instance of Windows Explorer and navigate to the share called
1236 <guiicon>files</guiicon> on the server called <guimenu>STABLE</guimenu>.
1240 Click in the right panel, and press <guimenu>Ctrl-A</guimenu> to select all files and
1241 directories. Press <guimenu>Ctrl-C</guimenu> to instruct Windows that you wish to
1242 copy all selected items.
1246 Launch the Windows Explorer, and navigate to the share called <guiicon>files</guiicon>
1247 on the server called <guimenu>CASHPOOL</guimenu>. Click in the right panel, and then press
1248 <guimenu>Ctrl-V</guimenu> to commence the copying process.
1255 Verify that the files are being copied correctly from the Windows NT4 machine to the Samba-3 server.
1256 This is best done on the Samba-3 server. Check the contents of the directory tree under
1257 <filename>/data</filename> by executing the following command:
1259 &rootprompt; ls -aR /data
1261 Make certain to check the ownership and permissions on all files. If in doubt, execute the following:
1263 &rootprompt; chown alan /data
1264 &rootprompt; for i in james suzy ursula peter dale eric jeannie russell
1268 &rootprompt; chgrp -R accts /data
1269 &rootprompt; chmod -R ug+rwxs,o-r+x /data
1274 The migration of all data should now be complete. It is time to validate the installation.
1275 For this, you should make sure all applications, including printing, work before asking the
1276 customer to test drive the new network.
1281 <smbconfexample id="acctconf">
1282 <title>Accounting Office Network &smb.conf; Old Style Configuration File</title>
1283 <smbconfcomment>Global parameters</smbconfcomment>
1284 <smbconfsection name="[global]"/>
1285 <smbconfoption name="workgroup">BILLMORE</smbconfoption>
1286 <smbconfoption name="printcap name">CUPS</smbconfoption>
1287 <smbconfoption name="disable spoolss">Yes</smbconfoption>
1288 <smbconfoption name="show add printer wizard">No</smbconfoption>
1289 <smbconfoption name="printing">cups</smbconfoption>
1291 <smbconfsection name="[files]"/>
1292 <smbconfoption name="comment">Work area files</smbconfoption>
1293 <smbconfoption name="path">/data/%U</smbconfoption>
1294 <smbconfoption name="read only">No</smbconfoption>
1296 <smbconfsection name="[master]"/>
1297 <smbconfoption name="comment">Master work area files</smbconfoption>
1298 <smbconfoption name="path">/data</smbconfoption>
1299 <smbconfoption name="valid users">alan</smbconfoption>
1300 <smbconfoption name="read only">No</smbconfoption>
1302 <smbconfsection name="[printers]"/>
1303 <smbconfoption name="comment">Print Temporary Spool Configuration</smbconfoption>
1304 <smbconfoption name="path">/var/spool/samba</smbconfoption>
1305 <smbconfoption name="printable">Yes</smbconfoption>
1306 <smbconfoption name="guest ok">Yes</smbconfoption>
1307 <smbconfoption name="use client driver">Yes</smbconfoption>
1308 <smbconfoption name="browseable">No</smbconfoption>
1316 <title>Questions and Answers</title>
1319 The following questions and answers draw from the examples in this chapter.
1320 Many design decisions are impacted by the configurations chosen. The intent
1321 is to expose some of the hidden implications.
1324 <qandaset defaultlabel="chap02qa">
1329 What makes an anonymous Samba server more simple than a non-anonymous Samba server?
1336 In the anonymous server, the only account used is the <constant>guest</constant> account.
1337 In a non-anonymous configuration, it is necessary to add real user accounts to both the
1338 UNIX system and to the Samba configuration. Non-anonymous servers require additional
1349 How is the operation of the parameter <parameter>force user</parameter> different from
1350 setting the root directory of the share SUID?
1357 The parameter <parameter>force user</parameter> causes all operations on the share to assume the UID
1358 of the forced user. The new default GID that applies is the primary GID of the forced user.
1359 This gives all users of this resource the actual privilege of the forced user.
1363 When a directory is set SUID, the operating system forces files that are written within it
1364 to be owned by the owner of the directory. While this happens, the user who is using the share
1365 has only the level of privilege he or she is assigned within the operating system context.
1369 The parameter <parameter>force user</parameter> has potential security implications that go
1370 beyond the actual share root directory. Be careful and wary of using this parameter.
1380 When would you both use the per share parameter <parameter>force user</parameter> and set
1381 the share root directory SUID?
1388 You would use both parameters when it is necessary to guarantee that all share handling operations
1389 are conducted as the forced user, while all file and directory creation are done as the SUID
1400 What is better about CUPS printing than LPRng printing?
1407 CUPS is a print spooling system that has integrated remote management facilities, provides completely
1408 automated print processing/preprocessing, and can be configured to automatically
1409 apply print preprocessing filters to ensure that a print job submitted is correctly rendered for the
1410 target printer. CUPS includes an image file RIP that supports printing of image files to
1411 non-PostScript printers. CUPS has lots of bells and whistles and is more like a supercharged MS Windows
1412 NT/200x print monitor and processor. Its complexity can be eliminated or turbocharged to suit
1417 The LPRng software is an enhanced, extended, and portable implementation of the Berkeley LPR print
1418 spooler functionality. It provides the same interface and meets RFC1179 requirements. LPRng can be
1419 configured to act like CUPS, but it is in principle a replacement for the old Berkeley lpr/lpd
1420 spooler. LPRng is generally preferred by those who are familiar with Berkeley lpr/lpd.
1424 Which spooling system is better is a matter of personal taste. It depends on what you want to do and how you want to
1425 do it and manage it. Most modern Linux systems ship with CUPS as the default print management system.
1435 When should Windows client IP addresses be hard-coded?
1442 When there are few MS Windows clients, little client change, no mobile users, and users are not
1443 inclined to tamper with network settings, it is a safe and convenient matter to hard-code Windows
1444 client TCP/IP settings. Given that it is possible to lock down the Windows desktop and remove
1445 user ability to access network configuration controls, fixed configuration eliminates the need
1446 for a DHCP server. This reduces maintenance overheads and eliminates a possible point of network
1457 Under what circumstances is it best to use a DHCP server?
1464 In network configurations where there are mobile users, or where Windows client PCs move around
1465 (particularly between offices or between subnets), it makes complete sense to control all Windows
1466 client configurations using a DHCP server. Additionally, when users do tamper with the network
1467 settings, DHCP can be used to normalize all client settings.
1471 One underappreciated benefit of using a DHCP server to assign all network client
1472 device TCP/IP settings is that it makes it a pain-free process to change network TCP/IP
1473 settings, change network addressing, or enhance the ability of client devices to
1474 benefit from new network services.
1478 Another benefit of modern DHCP servers is their ability to register dynamically
1479 assigned IP addresses with the DNS server. The benefits of Dynamic DNS (DDNS) are considerable in
1480 a large Windows network environment.
1490 What is the purpose of setting the parameter <parameter>guest ok</parameter> on a share?
1497 If this parameter is set to yes for a service, then no password is required to connect to the service.
1498 Privileges are those of the guest account.
1508 When would you set the global parameter <parameter>disable spoolss</parameter>?
1515 Setting this parameter to <constant>Yes</constant> disables Samba's support for the SPOOLSS set of
1516 MS-RPCs and yields behavior identical to Samba 2.0.x. Windows NT/2000 clients can downgrade to
1517 using LanMan style printing commands. Windows 9x/Me are unaffected by the parameter. However, this
1518 disables the ability to upload printer drivers to a Samba server via the Windows NT/200x Add Printer
1519 Wizard or by using the NT printer properties dialog window. It also disables the capability of
1520 Windows NT/200x clients to download print drivers from the Samba host on demand. Be extremely careful about
1521 setting this parameter.
1525 The alternate parameter <parameter>use client driver</parameter> applies only to Windows NT/200x clients. It has no
1526 effect on Windows 95/98/Me clients. When serving a printer to Windows NT/200x clients without first installing a valid
1527 printer driver on the Samba host, the client is required to install a local printer driver. From this point on,
1528 the client treats the printer as a local printer and not a network printer connection. This is much the same behavior
1529 that occurs when <parameter>disable spoolss = yes</parameter>.
1533 Under normal circumstances, the NT/200x client attempts to open the network printer using MS-RPC. Because the client
1534 considers the printer to be local, it attempts to issue the <parameter>OpenPrinterEx()</parameter> call requesting
1535 access rights associated with the logged on user. If the user possesses local administrator rights but not root
1536 privilege on the Samba host (often the case), the <parameter>OpenPrinterEx()</parameter> call fails. The result is
1537 that the client now displays an <quote>Access Denied; Unable to connect</quote> message in the printer queue window
1538 (even though jobs may be printed successfully). This parameter MUST not be enabled on a print share that has a valid
1539 print driver installed on the Samba server.
1549 Why would you disable password caching on Windows 9x/Me clients?
1556 Windows 9x/Me workstations that are set at default (password caching enabled) store the username and
1557 password in files located in the Windows master directory. Such files can be scavenged (read off a client
1558 machine) and decrypted, thus revealing the user's access credentials for all systems the user may have accessed.
1559 It is most insecure to allow any Windows 9x/Me client to operate with password caching enabled.
1569 The example of Abmas Accounting uses User Mode security. How does this provide anonymous access?
1576 The example used does not provide anonymous access. Since the clients are all Windows 2000 Professional,
1577 and given that users are logging onto their machines, by default the client attempts to connect to
1578 a remote server using currently logged in user credentials. By ensuring that the user's login ID and
1579 password are the same as those set on the Samba server, access is transparent and does not require
1580 separate user authentication.