1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE book PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
3 <chapter id="printing">
7 <firstname>Kurt</firstname><surname>Pfeifle</surname>
9 <orgname> Danka Deutschland GmbH </orgname>
10 <address><email>kpfeifle@danka.de</email></address>
15 <pubdate>May 31, 2003</pubdate>
18 <title>Classical Printing Support</title>
21 <title>Features and Benefits</title>
24 Printing is often a mission-critical service for the users. Samba can
25 provide this service reliably and seamlessly for a client network
26 consisting of Windows workstations.
30 A Samba print service may be run on a Stand-alone or Domain Member server,
31 side by side with file serving functions, or on a dedicated print server.
32 It can be made as tight or as loosely secured as needs dictate. Configurations
33 may be simple or complex. Available authentication schemes are essentially
34 the same as described for file services in previous chapters. Overall,
35 Samba's printing support is now able to replace an NT or Windows 2000
36 print server full-square, with additional benefits in many cases. Clients
37 may download and install drivers and printers through their familiar
38 <quote>Point'n'Print</quote> mechanism. Printer installations executed by
39 <quote>Logon Scripts</quote> are no problem. Administrators can upload and
40 manage drivers to be used by clients through the familiar <quote>Add Printer
41 Wizard</quote>. As an additional benefit, driver and printer management may
42 be run from the command line or through scripts, making it more efficient
43 in case of large numbers of printers. If a central accounting of print jobs
44 (tracking every single page and supplying the raw data for all sorts of
45 statistical reports) is required, this function is best supported by
46 the newer Common UNIX Printing System (CUPS)
47 as the print subsystem underneath the Samba hood.
51 This chapter deals with the foundations of Samba printing as they
52 are implemented by the more traditional UNIX (BSD- and System V-style)
53 printing systems. Many things covered in this chapter apply also to CUPS.
54 If you use CUPS, you may be tempted
55 to jump to the next chapter but you will certainly miss a few things if
56 you do. It is recommended that you read this chapter as well as <link
57 linkend="CUPS-printing">CUPS Printing Support</link>.
62 Most of the following examples have been verified on Windows XP
63 Professional clients. Where this document describes the responses to
64 commands given, bear in mind that Windows 200x/XP clients are quite
65 similar, but may differ in minor details. Windows NT is somewhat different
73 <title>Technical Introduction</title>
76 Samba's printing support always relies on the installed print subsystem
77 of the UNIX OS it runs on. Samba is a <quote>middleman.</quote> It takes
78 print files from Windows (or other SMB) clients and passes them to the real
79 printing system for further processing, therefore, it needs to communicate with
80 both sides: the Windows print clients and the UNIX printing system. Hence, we
81 must differentiate between the various client OS types, each of which behave
82 differently, as well as the various UNIX print subsystems, which themselves
83 have different features and are accessed differently.
87 This deals with the traditional way of UNIX printing. The next chapter
88 covers in great detail the more modern <emphasis>Common UNIX Printing
89 System</emphasis> (CUPS).
92 <important><para>CUPS users, be warned: do not just jump on to the next
93 chapter. You might miss important information only found here!
97 It is apparent from postings on the Samba mailing list that print configuration
98 is one of the most problematic aspects of Samba administration today. Many
99 new Samba administrators have the impression that Samba performs some sort
100 of print processing. Rest assured, Samba does not perform any type of print
101 processing. It does not do any form of print filtering.
105 Samba obtains from its clients a data stream (print job) that it spools to a
106 local spool area. When the entire print job has been received, Samba invokes
107 a local UNIX/Linux print command and passes the spooled file to it. It is
108 up to the local system printing subsystems to correctly process the print
109 job and to submit it to the printer.
113 <title>Client to Samba Print Job Processing</title>
116 Successful printing from a Windows client via a Samba print server to a UNIX
117 printer involves six (potentially seven) stages:
121 <listitem><para>Windows opens a connection to the printer share.</para></listitem>
123 <listitem><para>Samba must authenticate the user.</para></listitem>
125 <listitem><para>Windows sends a copy of the print file over the network
126 into Samba's spooling area.</para></listitem>
128 <listitem><para>Windows closes the connection.</para></listitem>
130 <listitem><para>Samba invokes the print command to hand the file over
131 to the UNIX print subsystem's spooling area.</para></listitem>
133 <listitem><para>The UNIX print subsystem processes the print job.</para></listitem>
135 <listitem><para>The print file may need to be explicitly deleted
136 from the Samba spooling area. This item depends on your print spooler
137 configuration settings.</para></listitem>
143 <title>Printing Related Configuration Parameters</title>
146 There are a number of configuration parameters to control Samba's
147 printing behavior. Please refer to the man page for &smb.conf; for an
148 overview of these. As with other parameters, there are Global Level
149 (tagged with a <emphasis>G</emphasis> in the listings) and Service Level
150 (<emphasis>S</emphasis>) parameters.
154 <varlistentry><term>Global Parameters</term>
155 <listitem><para> These <emphasis>may not</emphasis> go into
156 individual share definitions. If they go in by error,
157 the <command>testparm</command> utility can discover this
158 (if you run it) and tell you so.
162 <varlistentry><term>Service Level Parameters</term>
163 <listitem><para> These may be specified in the
164 <smbconfsection>[global]</smbconfsection> section of &smb.conf;.
165 In this case they define the default behavior of all individual
166 or service level shares (provided they do not have a different
167 setting defined for the same parameter, thus overriding the
177 <title>Simple Print Configuration</title>
180 <link linkend="simpleprc">Following example</link> shows a simple printing configuration.
181 If you compare this with your own, you may find
182 additional parameters that have been pre-configured by your OS
183 vendor. Below is a discussion and explanation of the
184 parameters. This example does not use many parameters.
185 However, in many environments these are enough to provide a valid
186 &smb.conf; file that enables all clients to print.
190 <smbconfexample id="simpleprc">
191 <title>Simple configuration with BSD printing</title>
192 <smbconfsection>[global]</smbconfsection>
193 <smbconfoption><name>printing</name><value>bsd</value></smbconfoption>
194 <smbconfoption><name>load printers</name><value>yes</value></smbconfoption>
196 <smbconfsection>[printers]</smbconfsection>
197 <smbconfoption><name>path</name><value>/var/spool/samba</value></smbconfoption>
198 <smbconfoption><name>printable</name><value>yes</value></smbconfoption>
199 <smbconfoption><name>public</name><value>yes</value></smbconfoption>
200 <smbconfoption><name>writable</name><value>no</value></smbconfoption>
201 </smbconfexample></para>
204 This is only an example configuration. Samba assigns default values to
205 all configuration parameters. The defaults are conservative
206 and sensible. When a parameter is specified in the &smb.conf; file, this
207 overwrites the default value. The <command>testparm</command> utility when
208 run as root is capable of reporting all setting, both default as well as
209 &smb.conf; file settings. <command>Testparm</command> gives warnings for all
210 mis-configured settings. The complete output is easily 340 lines and more,
211 so you may want to pipe it through a pager program.
215 The syntax for the configuration file is easy to grasp. You should
216 know that is not very picky about its syntax. As has been explained
217 elsewhere in this document, Samba tolerates some spelling errors (such
218 as <smbconfoption><name>browseable</name></smbconfoption> instead of
219 <smbconfoption><name>browseable</name></smbconfoption>), and spelling is
220 case-insensitive. It is permissible to use <parameter>Yes/No</parameter>
221 or <parameter>True/False</parameter> for Boolean settings. Lists of names
222 may be separated by commas, spaces or tabs.
226 <title>Verifying Configuration with <command>testparm</command></title>
229 To see all (or at least most) printing-related settings in Samba, including
230 the implicitly used ones, try the command outlined below. This command greps
231 for all occurrences of <constant>lp, print, spool, driver, ports</constant>
232 and <constant>[</constant> in testparms output. This provides a convenient
233 overview of the running <command>smbd</command> print configuration. This
234 command does not show individually created printer shares or the spooling
235 paths they may use. Here is the output of my Samba setup, with settings
236 shown in <link linkend="simpleprc">the example above</link>:
240 &rootprompt;<userinput>testparm -s -v | egrep "(lp|print|spool|driver|ports|\[)"</userinput>
241 Load smb config files from /etc/samba/smb.conf
242 Processing section "[homes]"
243 Processing section "[printers]"
249 printcap name = /etc/printcap
253 deleteprinter command =
254 show add printer wizard = Yes
258 max print jobs = 1000
261 print command = lpr -r -P'%p' %s
262 lpq command = lpq -P'%p'
263 lprm command = lprm -P'%p' %j
267 use client driver = No
272 path = /var/spool/samba
278 You can easily verify which settings were implicitly added by Samba's
279 default behavior. <emphasis>Remember: it may
280 be important in your future dealings with Samba.</emphasis>
283 <note><para> testparm in Samba-3 behaves differently from that in 2.2.x: used
284 without the <quote>-v</quote> switch it only shows you the settings actually
285 written into! To see the complete
286 configuration used, add the <quote>-v</quote> parameter to testparm.</para></note>
291 <title>Rapid Configuration Validation</title>
294 Should you need to troubleshoot at any stage, please always come back
295 to this point first and verify if <command>testparm</command> shows the parameters you
296 expect. To give you a warning from personal experience,
297 try to just comment out the <smbconfoption><name>load printers</name></smbconfoption>
298 parameter. If your 2.2.x system behaves like mine, you'll see this:
302 &rootprompt;grep "load printers" /etc/samba/smb.conf
303 # load printers = Yes
304 # This setting is commented out!!
306 &rootprompt;testparm -v /etc/samba/smb.conf | egrep "(load printers)"
311 I assumed that commenting out of this setting should prevent Samba from
312 publishing my printers, but it still did. It took some time to figure out
313 the reason. But I am no longer fooled ... at least not by this.
317 &rootprompt;<userinput>grep -A1 "load printers" /etc/samba/smb.conf</userinput>
319 # The above setting is what I want!
320 # load printers = Yes
321 # This setting is commented out!
323 &rootprompt;<userinput>testparm -s -v smb.conf.simpleprinting | egrep "(load printers)"</userinput>
329 Only when the parameter is explicitly set to
330 <smbconfoption><name>load printers</name><value>No</value></smbconfoption>
331 would Samba conform with my intentions. So, my strong advice is:
335 <listitem><para>Never rely on commented out parameters.</para></listitem>
337 <listitem><para>Always set parameters explicitly as you intend them to
338 behave.</para></listitem>
340 <listitem><para>Use <command>testparm</command> to uncover hidden
341 settings that might not reflect your intentions.</para></listitem>
346 The following is the most minimal configuration file:
348 &rootprompt;<userinput>cat /etc/samba/smb.conf-minimal</userinput>
353 This example should show that you can use testparm to test any Samba
354 configuration file. Actually, we encourage you <emphasis>not</emphasis>
355 to change your working system (unless you know exactly what you are
356 doing). Don't rely on the assumption that changes will only take effect after
357 you re-start smbd! This is not the case. Samba re-reads it every 60 seconds
358 and on each new client connection. You might have to face changes for your
359 production clients that you didn't intend to apply. You will now
360 note a few more interesting things; <command>testparm</command> is useful to
361 identify what the Samba print configuration would be if you used this minimalistic
362 configuration. Here is what you can expect to find:
366 &rootprompt;<userinput>testparm -v smb.conf-minimal | egrep "(print|lpq|spool|driver|ports|[)"</userinput>
367 Processing section "[printers]"
368 WARNING: [printers] service MUST be printable!
369 No path in service printers - using /tmp
373 printcap name = /etc/printcap
377 deleteprinter command =
378 show add printer wizard = Yes
382 max print jobs = 1000
385 print command = lpr -r -P%p %s
386 lpq command = lpq -P%p
388 use client driver = No
396 testparm issued two warnings:
400 <listitem><para>We did not specify the <smbconfsection>[printers]</smbconfsection> section as printable.</para></listitem>
401 <listitem><para>We did not tell Samba which spool directory to use.</para></listitem>
405 However, this was not fatal and Samba will default to values that will
406 work. Please, do not rely on this and do not use this example. This was
407 included to encourage you to be careful to design and specify your setup to do
408 precisely what you require. The outcome on your system may vary for some
409 parameters given, since Samba may have been built with different compile-time
410 options. <emphasis>Warning:</emphasis> do not put a comment sign
411 <emphasis>at the end</emphasis> of a valid line. It will cause the parameter
412 to be ignored (just as if you had put the comment sign at the front). At first
413 I regarded this as a bug in my Samba versions. But the man page clearly says:
414 <quote>Internal whitespace in a parameter value is retained verbatim.</quote>
415 This means that a line consisting of, for example:
419 <smbconfcomment>This defines LPRng as the printing system</smbconfcomment>
420 <smbconfoption><name>printing</name><value> lprng</value></smbconfoption>
421 </smbconfblock></para>
424 will regard the whole of the string after the
425 <quote><constant>=</constant></quote> sign as the value you want to
426 define. This is an invalid value that will be ignored and a default
434 <title>Extended Printing Configuration</title>
437 <link linkend="extbsdpr">Next configuration</link> shows a more verbose example configuration
438 for print-related settings in a BSD-style printing environment. What follows
439 is a discussion and explanation of the various parameters. We chose to
440 use BSD-style printing here because it is still the most commonly used
441 system on legacy UNIX/Linux installations. New installations predominantly
442 use CUPS, which is discussed in a separate chapter. The example explicitly
443 names many parameters that do not need to be specified because they are set
444 by default. You could use a much leaner &smb.conf; file. Alternately, you can use
445 <command>testparm</command> or <command>SWAT</command> to optimize the &smb.conf;
446 file to remove all parameters that are set at default.
449 <para><smbconfexample id="extbsdpr">
450 <title>Extended BSD Printing Configuration</title>
451 <smbconfsection>[global]</smbconfsection>
452 <smbconfoption><name>printing</name><value>bsd</value></smbconfoption>
453 <smbconfoption><name>load printers</name><value>yes</value></smbconfoption>
454 <smbconfoption><name>show add printer wizard</name><value>yes</value></smbconfoption>
455 <smbconfoption><name>printcap name</name><value>/etc/printcap</value></smbconfoption>
456 <smbconfoption><name>printer admin</name><value>@ntadmin, root</value></smbconfoption>
457 <smbconfoption><name>max print jobs</name><value>100</value></smbconfoption>
458 <smbconfoption><name>lpq cache time</name><value>20</value></smbconfoption>
459 <smbconfoption><name>use client driver</name><value>no</value></smbconfoption>
461 <smbconfsection>[printers]</smbconfsection>
462 <smbconfoption><name>comment</name><value>All Printers</value></smbconfoption>
463 <smbconfoption><name>printable</name><value>yes</value></smbconfoption>
464 <smbconfoption><name>path</name><value>/var/spool/samba</value></smbconfoption>
465 <smbconfoption><name>browseable</name><value>no</value></smbconfoption>
466 <smbconfoption><name>guest ok</name><value>yes</value></smbconfoption>
467 <smbconfoption><name>public</name><value>yes</value></smbconfoption>
468 <smbconfoption><name>read only</name><value>yes</value></smbconfoption>
469 <smbconfoption><name>writable</name><value>no </value></smbconfoption>
471 <smbconfsection>[my_printer_name]</smbconfsection>
472 <smbconfoption><name>comment</name><value>Printer with Restricted Access</value></smbconfoption>
473 <smbconfoption><name>path</name><value>/var/spool/samba_my_printer</value></smbconfoption>
474 <smbconfoption><name>printer admin</name><value>kurt</value></smbconfoption>
475 <smbconfoption><name>browseable</name><value>yes</value></smbconfoption>
476 <smbconfoption><name>printable</name><value>yes</value></smbconfoption>
477 <smbconfoption><name>writable</name><value>no</value></smbconfoption>
478 <smbconfoption><name>hosts allow</name><value>0.0.0.0</value></smbconfoption>
479 <smbconfoption><name>hosts deny</name><value>turbo_xp, 10.160.50.23, 10.160.51.60</value></smbconfoption>
480 <smbconfoption><name>guest ok</name><value>no</value></smbconfoption>
481 </smbconfexample></para>
484 This is an example configuration. You may not find all the settings that are in
485 the configuration file that was provided by the OS vendor. Samba configuration
486 parameters, if not explicitly set default to a sensible value.
487 To see all settings, as <constant>root</constant> use the <command>testparm</command>
488 utility. <command>testparm</command> gives warnings for mis-configured settings.
492 <title>Detailed Explanation Settings</title>
495 The following is a discussion of the settings from above shown example.
499 <title>The [global] Section</title>
502 The <smbconfsection>[global]</smbconfsection> section is one of four special
503 sections (along with [<smbconfsection>[homes]</smbconfsection>,
504 <smbconfsection>[printers]</smbconfsection>
505 and <smbconfsection>[print$]</smbconfsection>...). The
506 <smbconfsection>[global]</smbconfsection> contains all parameters which apply
507 to the server as a whole. It is the place for parameters that have only a
508 global meaning. It may also contain service level parameters that then define
509 default settings for all other sections and shares. This way you can simplify
510 the configuration and avoid setting the same value repeatedly. (Within each
511 individual section or share you may, however, override these globally set
512 share settings and specify other values).
516 <varlistentry><term><smbconfoption><name>printing</name><value>bsd </value></smbconfoption></term>
517 <listitem><para>Causes Samba to use default print commands
518 applicable for the BSD (also known as RFC 1179 style or LPR/LPD) printing
519 system. In general, the <parameter>printing</parameter> parameter informs Samba about the
520 print subsystem it should expect. Samba supports CUPS, LPD, LPRNG,
521 SYSV, HPUX, AIX, QNX, and PLP. Each of these systems defaults to a
522 different <smbconfoption><name>print command</name></smbconfoption> (and other queue control
525 <caution><para>The <smbconfoption><name>printing</name></smbconfoption> parameter is
526 normally a service level parameter. Since it is included here in the
527 <smbconfsection>[global]</smbconfsection> section, it will take effect for all
528 printer shares that are not defined differently. Samba-3 no longer
529 supports the SOFTQ printing system.</para></caution>
530 </listitem></varlistentry>
532 <varlistentry><term><smbconfoption><name>load printers</name><value>yes </value></smbconfoption></term>
533 <listitem><para>Tells Samba to create automatically all
534 available printer shares. Available printer shares are discovered by
535 scanning the printcap file. All created printer shares are also loaded
536 for browsing. If you use this parameter, you do not need to specify
537 separate shares for each printer. Each automatically created printer
538 share will clone the configuration options found in the
539 <smbconfsection>[printers]</smbconfsection> section. (The <parameter>load printers
540 = no</parameter> setting will allow you to specify each UNIX printer
541 you want to share separately, leaving out some you do not want to be
542 publicly visible and available).</para>
543 </listitem></varlistentry>
545 <varlistentry><term><smbconfoption><name>show add printer wizard</name><value>yes </value></smbconfoption></term>
546 <listitem><para>Setting is normally enabled by default (even if the parameter is not specified in &smb.conf;).
547 It causes the <guiicon>Add Printer Wizard</guiicon> icon to appear
548 in the <guiicon>Printers</guiicon> folder of the Samba host's
549 share listing (as shown in <guiicon>Network Neighborhood</guiicon> or
550 by the <command>net view</command> command). To disable it, you need to
551 explicitly set it to <constant>no</constant> (commenting it out
552 will not suffice). The <parameter>Add Printer Wizard</parameter> lets you upload printer
553 drivers to the <smbconfsection>[print$]</smbconfsection> share and associate it
554 with a printer (if the respective queue exists before the
555 action), or exchange a printer's driver against any other previously
556 uploaded driver.</para>
557 </listitem></varlistentry>
559 <varlistentry><term><smbconfoption><name>max print jobs</name><value>100 </value></smbconfoption></term>
560 <listitem><para>Sets the upper limit to 100 print jobs
561 being active on the Samba server at any one time. Should a client
562 submit a job that exceeds this number, a <quote>no more space
563 available on server</quote> type of error message will be returned by
564 Samba to the client. A setting of zero (the default) means there is
565 <emphasis>no</emphasis> limit at all.
566 </para></listitem></varlistentry>
568 <varlistentry><term><smbconfoption><name>printcap name</name><value>/etc/printcap </value></smbconfoption></term>
569 <listitem><para>Tells Samba where to look for a list of
570 available printer names. Where CUPS is used, make sure that a printcap
571 file is written. This is controlled by the <constant>Printcap</constant> directive in the
572 <filename>cupsd.conf</filename> file.
573 </para></listitem></varlistentry>
575 <varlistentry><term><smbconfoption><name>printer admin</name><value>@ntadmin </value></smbconfoption></term>
576 <listitem><para>Members of the ntadmin group should be able to add
577 drivers and set printer properties (<constant>ntadmin</constant> is only an example name,
578 it needs to be a valid UNIX group name); root is implicitly always a
579 <smbconfoption><name>printer admin</name></smbconfoption>. The @ sign precedes group names in the
580 <filename>/etc/group</filename>. A printer admin can do anything to
581 printers via the remote administration interfaces offered by MS-RPC
582 (see below). In larger installations, the <smbconfoption><name>printer admin</name></smbconfoption>
583 parameter is normally a per-share parameter. This permits different groups to administer each printer share.
584 </para></listitem></varlistentry>
586 <varlistentry><term><smbconfoption><name>lpq cache time</name><value>20 </value></smbconfoption></term>
587 <listitem><para>Controls the cache time for the results of the
588 lpq command. It prevents the lpq command being called too often and
589 reduces the load on a heavily used print server.
590 </para></listitem></varlistentry>
592 <varlistentry><term><smbconfoption><name>use client driver</name><value>no </value></smbconfoption></term>
593 <listitem><para>If set to <constant>yes</constant>, only
594 takes effect for Windows NT/200x/XP clients (and not for Win 95/98/ME). Its
595 default value is <constant>No</constant> (or <constant>False</constant>).
596 It must <emphasis>not</emphasis> be enabled on print shares
597 (with a <constant>yes</constant> or <constant>true</constant> setting) that
598 have valid drivers installed on the Samba server. For more detailed
599 explanations see the &smb.conf; man page.
600 </para></listitem></varlistentry>
606 <title>The [printers] Section</title>
609 This is the second special section. If a section with this name appears in
610 the &smb.conf;, users are able to connect to any printer specified in the
611 Samba host's printcap file, because Samba on startup then creates a printer
612 share for every printer name it finds in the printcap file. You could regard
613 this section as a general convenience shortcut to share all printers with
614 minimal configuration. It is also a container for settings that should
615 apply as default to all printers. (For more details see the &smb.conf;
616 man page.) Settings inside this container must be Share Level parameters.
620 <varlistentry><term><smbconfoption><name>comment</name><value>All printers </value></smbconfoption></term>
622 The <smbconfoption><name>comment</name></smbconfoption> is shown next to the share if
623 a client queries the server, either via <guiicon>Network Neighborhood</guiicon> or with
624 the <command>net view</command> command to list available shares.
628 <varlistentry><term><smbconfoption><name>printable</name><value>yes </value></smbconfoption></term>
630 The <smbconfsection>[printers]</smbconfsection> service <emphasis>must</emphasis>
631 be declared as printable. If you specify otherwise, smbd will refuse to load at
632 startup. This parameter allows connected clients to open, write to and submit spool files
633 into the directory specified with the <smbconfoption><name>path</name></smbconfoption>
634 parameter for this service. It is used by Samba to differentiate printer shares from
639 <varlistentry><term><smbconfoption><name>path</name><value>/var/spool/samba </value></smbconfoption></term>
641 Must point to a directory used by Samba to spool incoming print files. <emphasis>It
642 must not be the same as the spool directory specified in the configuration of your UNIX
643 print subsystem!</emphasis> The path typically points to a directory that is world
644 writable, with the <quote>sticky</quote> bit set to it.
648 <varlistentry><term><smbconfoption><name>browseable</name><value>no </value></smbconfoption></term>
650 Is always set to <constant>no</constant> if
651 <smbconfoption><name>printable</name><value>yes</value></smbconfoption>. It makes
652 the <smbconfsection>[printer]</smbconfsection> share itself invisible in the list of
653 available shares in a <command>net view</command> command or in the Explorer browse
654 list. (You will of course see the individual printers).
658 <varlistentry><term><smbconfoption><name>guest ok</name><value>yes </value></smbconfoption></term>
660 If this parameter is set to <constant>yes</constant>, no password is required to
661 connect to the printer's service. Access will be granted with the privileges of the
662 <smbconfoption><name>guest account</name></smbconfoption>. On many systems the guest
663 account will map to a user named <quote>nobody</quote>. This user will usually be found
664 in the UNIX passwd file with an empty password, but with no valid UNIX login. (On some
665 systems the guest account might not have the privilege to be able to print. Test this
666 by logging in as your guest user using <command>su - guest</command> and run a system
671 <userinput>lpr -P printername /etc/motd</userinput>
675 <varlistentry><term><smbconfoption><name>public</name><value>yes </value></smbconfoption></term>
677 Is a synonym for <smbconfoption><name>guest ok</name><value>yes</value></smbconfoption>.
678 Since we have <smbconfoption><name>guest ok</name><value>yes</value></smbconfoption>, it
679 really does not need to be here. (This leads to the interesting question: <quote>What if I
680 by accident have two contradictory settings for the same share?</quote> The answer is the
681 last one encountered by Samba wins. Testparm does not complain about different settings
682 of the same parameter for the same share. You can test this by setting up multiple
683 lines for the <parameter>guest account</parameter> parameter with different usernames,
684 and then run testparm to see which one is actually used by Samba.)
688 <varlistentry><term><smbconfoption><name>read only</name><value>yes </value></smbconfoption></term>
690 Normally (for other types of shares) prevents users from creating or modifying files
691 in the service's directory. However, in a <quote>printable</quote> service, it is
692 <emphasis>always</emphasis> allowed to write to the directory (if user privileges allow the
693 connection), but only via print spooling operations. Normal write operations are not permitted.
697 <varlistentry><term><smbconfoption><name>writable</name><value>no </value></smbconfoption></term>
699 Is a synonym for <smbconfoption><name>read only</name><value>yes</value></smbconfoption>.
706 <title>Any [my_printer_name] Section</title>
709 If a section appears in the &smb.conf; file, which when given the parameter
710 <smbconfoption><name>printable</name><value>yes</value></smbconfoption> causes Samba to configure it
711 as a printer share. Windows 9x/Me clients may have problems with connecting or loading printer drivers
712 if the share name has more than eight characters. Do not name a printer share with a name that may conflict
713 with an existing user or file share name. On Client connection requests, Samba always tries to find file
714 shares with that name first. If it finds one, it will connect to this and will not connect
715 to a printer with the same name!
719 <varlistentry><term><smbconfoption><name>comment</name><value>Printer with Restricted Access </value></smbconfoption></term>
721 The comment says it all.
725 <varlistentry><term><smbconfoption><name>path</name><value>/var/spool/samba_my_printer </value></smbconfoption></term>
727 Sets the spooling area for this printer to a directory other than the default. It is not
728 necessary to set it differently, but the option is available.
732 <varlistentry><term><smbconfoption><name>printer admin</name><value>kurt </value></smbconfoption></term>
734 The printer admin definition is different for this explicitly defined printer share from the general
735 <smbconfsection>[printers]</smbconfsection> share. It is not a requirement; we
736 did it to show that it is possible.
740 <varlistentry><term><smbconfoption><name>browseable</name><value>yes </value></smbconfoption></term>
742 This makes the printer browseable so the clients may conveniently find it when browsing the
743 <guiicon>Network Neighborhood</guiicon>.
747 <varlistentry><term><smbconfoption><name>printable</name><value>yes </value></smbconfoption></term>
749 See <link linkend="ptrsect">The [printers] Section</link>.
753 <varlistentry><term><smbconfoption><name>writable</name><value>no </value></smbconfoption></term>
755 See <link linkend="ptrsect">The [printers] Section</link>.
759 <varlistentry><term><smbconfoption><name>hosts allow</name><value>10.160.50.,10.160.51. </value></smbconfoption></term>
761 Here we exercise a certain degree of access control by using the <smbconfoption><name>hosts allow</name></smbconfoption> and <smbconfoption><name>hosts deny</name></smbconfoption>
762 parameters. This is not by any means a safe bet. It is not a way to secure your
763 printers. This line accepts all clients from a certain subnet in a first evaluation of
768 <varlistentry><term><smbconfoption><name>hosts deny</name><value>turbo_xp,10.160.50.23,10.160.51.60 </value></smbconfoption></term>
770 All listed hosts are not allowed here (even if they belong to the allowed subnets). As
771 you can see, you could name IP addresses as well as NetBIOS hostnames here.
775 <varlistentry><term><smbconfoption><name>guest ok</name><value>no </value></smbconfoption></term>
777 This printer is not open for the guest account.
784 <title>Print Commands</title>
787 In each section defining a printer (or in the <smbconfsection>[printers]</smbconfsection> section),
788 a <parameter>print command</parameter> parameter may be defined. It sets a command to process the files
789 that have been placed into the Samba print spool directory for that printer. (That spool directory was,
790 if you remember, set up with the <smbconfoption><name>path</name></smbconfoption> parameter). Typically,
791 this command will submit the spool file to the Samba host's print subsystem, using the suitable system
792 print command. But there is no requirement that this needs to be the case. For debugging or
793 some other reason, you may want to do something completely different than print the file. An example is a
794 command that just copies the print file to a temporary location for further investigation when you need
795 to debug printing. If you craft your own print commands (or even develop print command shell scripts),
796 make sure you pay attention to the need to remove the files from the Samba spool directory. Otherwise,
797 your hard disk may soon suffer from shortage of free space.
802 <title>Default UNIX System Printing Commands</title>
805 You learned earlier on that Samba, in most cases, uses its built-in settings for many parameters
806 if it cannot find an explicitly stated one in its configuration file. The same is true for the
807 <smbconfoption><name>print command</name></smbconfoption>. The default print command varies depending
808 on the <smbconfoption><name>printing</name></smbconfoption> parameter setting. In the commands listed
809 below, you will notice some parameters of the form <emphasis>%X</emphasis> where <emphasis>X</emphasis> is
810 <emphasis>p, s, J</emphasis>, and so on. These letters stand for printer name, spool-file and job ID, respectively.
811 They are explained in more detail further below. <link linkend="printOptions">Next table</link> presents an overview of key
812 printing options but excludes the special case of CUPS that is discussed in <link linkend="CUPS-printing">CUPS Printing Support</link>.
815 <table frame='all' id="printOptions">
816 <title>Default Printing Settings</title>
817 <tgroup cols='2' align='left' colsep='1' rowsep='1'>
818 <colspec align="left"/>
819 <colspec align="left"/>
822 <entry>Setting</entry>
823 <entry>Default Printing Commands</entry>
828 <entry><smbconfoption><name>printing</name><value>bsd|aix|lprng|plp</value></smbconfoption></entry>
829 <entry>print command is <command>lpr -r -P%p %s</command></entry>
832 <entry><smbconfoption><name>printing</name><value>sysv|hpux</value></smbconfoption></entry>
833 <entry>print command is <command>lp -c -P%p %s; rm %s</command></entry>
836 <entry> <smbconfoption><name>printing</name><value>qnx</value></smbconfoption></entry>
837 <entry>print command is <command>lp -r -P%p -s %s</command></entry>
840 <entry><smbconfoption><name>printing</name><value>bsd|aix|lprng|plp</value></smbconfoption></entry>
841 <entry>lpq command is <command>lpq -P%p</command></entry>
844 <entry><smbconfoption><name>printing</name><value>sysv|hpux</value></smbconfoption></entry>
845 <entry>lpq command is <command>lpstat -o%p</command></entry>
848 <entry><smbconfoption><name>printing</name><value>qnx</value></smbconfoption></entry>
849 <entry>lpq command is <command>lpq -P%p</command></entry>
852 <entry><smbconfoption><name>printing</name><value>bsd|aix|lprng|plp</value></smbconfoption></entry>
853 <entry>lprm command is <command>lprm -P%p %j</command></entry>
856 <entry><smbconfoption><name>printing</name><value>sysv|hpux</value></smbconfoption></entry>
857 <entry>lprm command is <command>cancel %p-%j</command></entry>
860 <entry><smbconfoption><name>printing</name><value>qnx</value></smbconfoption></entry>
861 <entry>lprm command is <command>cancel %p-%j</command></entry>
864 <entry><smbconfoption><name>printing</name><value>bsd|aix|lprng|plp</value></smbconfoption></entry>
865 <entry>lppause command is <command>lp -i %p-%j -H hold</command></entry>
868 <entry><smbconfoption><name>printing</name><value>sysv|hpux</value></smbconfoption></entry>
869 <entry>lppause command (...is empty)</entry>
872 <entry><smbconfoption><name>printing</name><value>qnx</value></smbconfoption></entry>
873 <entry>lppause command (...is empty)</entry>
876 <entry><smbconfoption><name>printing</name><value>bsd|aix|lprng|plp</value></smbconfoption></entry>
877 <entry>lpresume command is <command>lp -i %p-%j -H resume</command></entry>
880 <entry><smbconfoption><name>printing</name><value>sysv|hpux</value></smbconfoption></entry>
881 <entry>lpresume command (...is empty)</entry>
884 <entry><smbconfoption><name>printing</name><value>qnx</value></smbconfoption></entry>
885 <entry>lpresume command (...is empty)</entry>
892 We excluded the special case of CUPS here, because it is discussed in the next chapter. For
893 <parameter>printing = CUPS</parameter>, if Samba is compiled against libcups, it uses the CUPS API to submit
894 jobs. (It is a good idea also to set <smbconfoption><name>printcap</name><value>cups</value></smbconfoption>
895 in case your <filename>cupsd.conf</filename> is set to write its auto-generated printcap file to an
896 unusual place). Otherwise, Samba maps to the System V printing commands with the -oraw option for printing,
897 i.e., it uses <command>lp -c -d%p -oraw; rm %s</command>. With <parameter>printing = cups</parameter>,
898 and if Samba is compiled against libcups, any manually set print command will be ignored!
904 <title>Custom Print Commands</title>
907 After a print job has finished spooling to a service, the <smbconfoption><name>print command</name></smbconfoption>
908 will be used by Samba via a <emphasis>system()</emphasis> call to process the
909 spool file. Usually the command specified will submit the spool file to the host's printing subsystem. But
910 there is no requirement at all that this must be the case. The print subsystem may not remove the spool
911 file on its own. So whatever command you specify, you should ensure that the spool file is deleted after
912 it has been processed.
916 There is no difficulty with using your own customized print commands with the traditional printing
917 systems. However, if you do not wish to roll your own, you should be well informed about the default
918 built-in commands that Samba uses for each printing subsystem (see
919 Table 17.1). In all the
920 commands listed in the last paragraphs, you see parameters of the form <emphasis>%X</emphasis>. These are
921 <emphasis>macros</emphasis>, or shortcuts, used as place-holders for the names of real objects. At the time
922 of running a command with such a placeholder, Samba will insert the appropriate value automatically. Print
923 commands can handle all Samba macro substitutions. In regard to printing, the following ones do have
928 <listitem><para><parameter>%s, %f</parameter> &smbmdash; the path to the spool file name.</para></listitem>
929 <listitem><para><parameter>%p</parameter> &smbmdash; the appropriate printer name.</para></listitem>
930 <listitem><para><parameter>%J</parameter> &smbmdash; the job name as transmitted by the client.</para></listitem>
931 <listitem><para><parameter>%c</parameter> &smbmdash; the number of printed pages of the spooled job (if known).</para></listitem>
932 <listitem><para><parameter>%z</parameter> &smbmdash; the size of the spooled print job (in bytes).</para></listitem>
936 The print command must contain at least one occurrence of <parameter>%s</parameter> or
937 the <parameter>%f</parameter>. The <parameter>%p</parameter> is optional. If no printer name is supplied,
938 the <parameter>%p</parameter> will be silently removed from the print command. In this case, the job is
939 sent to the default printer.
943 If specified in the <smbconfsection>[global]</smbconfsection> section, the print command given will be
944 used for any printable service that does not have its own print command specified. If there is neither a
945 specified print command for a printable service nor a global print command, spool files will be created
946 but not processed! Most importantly, print files will not be removed, so they will consume disk space.
950 Printing may fail on some UNIX systems when using the <quote>nobody</quote> account. If this happens, create an
951 alternative guest account and give it the privilege to print. Set up this guest account in the
952 <smbconfsection>[global]</smbconfsection> section with the <parameter>guest account</parameter> parameter.
956 You can form quite complex print commands. You need to realize that print commands are just
957 passed to a UNIX shell. The shell is able to expand the included environment variables as
958 usual. (The syntax to include a UNIX environment variable <parameter>$variable</parameter>
959 in the Samba print command is <parameter>%$variable</parameter>.) To give you a working
960 <smbconfoption><name>print command</name></smbconfoption> example, the following will log a print job
961 to <filename>/tmp/print.log</filename>, print the file, then remove it. The semicolon (<quote>;</quote>
962 is the usual separator for commands in shell scripts:
966 <smbconfoption><name>print command</name><value>echo Printing %s >> \</value></smbconfoption>
967 <member><parameter>/tmp/print.log; lpr -P %p %s; rm %s</parameter></member>
968 </smbconfblock></para>
971 You may have to vary your own command considerably from this example depending on how you normally print
972 files on your system. The default for the <smbconfoption><name>print command</name></smbconfoption>
973 parameter varies depending on the setting of the <smbconfoption><name>printing</name></smbconfoption>
974 parameter. Another example is:
978 <smbconfoption><name>print command</name><value>/usr/local/samba/bin/myprintscript %p %s</value></smbconfoption>
979 </smbconfblock></para>
985 <title>Printing Developments Since Samba-2.2</title>
988 Prior to Samba-2.2.x, print server support for Windows clients was limited to <emphasis>LanMan</emphasis>
989 printing calls. This is the same protocol level as Windows 9x/Me PCs offer when they share printers.
990 Beginning with the 2.2.0 release, Samba started to support the native Windows NT printing mechanisms. These
991 are implemented via <emphasis>MS-RPC</emphasis> (RPC = <emphasis>Remote Procedure Calls</emphasis>
992 ). MS-RPCs use the <emphasis>SPOOLSS</emphasis> named pipe for all printing.
996 The additional functionality provided by the new SPOOLSS support includes:
1001 Support for downloading printer driver files to Windows 95/98/NT/2000 clients upon
1002 demand (<emphasis>Point'n'Print</emphasis>).
1006 Uploading of printer drivers via the Windows NT <emphasis>Add Printer Wizard</emphasis> (APW)
1007 or the <ulink url="http://imprints.sourceforge.net/">Imprints</ulink> tool set.
1011 Support for the native MS-RPC printing calls such as
1012 StartDocPrinter, EnumJobs(), and so on. (See the
1013 <ulink url="http://msdn.microsoft.com/">MSDN documentation</ulink> for more information on the
1014 Win32 printing API).
1018 Support for NT <emphasis>Access Control Lists</emphasis> (ACL) on printer objects.
1022 Improved support for printer queue manipulation through the use of internal databases for spooled
1023 job information (implemented by various <filename>*.tdb</filename> files).
1028 A benefit of updating is that Samba-3 is able to publish its printers to Active Directory (or LDAP).
1032 A fundamental difference exists between MS Windows NT print servers and Samba operation. Windows NT
1033 permits the installation of local printers that are not shared. This is an artifact of the fact that
1034 any Windows NT machine (server or client) may be used by a user as a workstation. Samba will publish all
1035 printers that are made available, either by default or by specific declaration via printer-specific shares.
1039 Windows NT/200x/XP Professional clients do not have to use the standard SMB printer share; they can
1040 print directly to any printer on another Windows NT host using MS-RPC. This, of course, assumes that
1041 the client has the necessary privileges on the remote host that serves the printer resource. The
1042 default permissions assigned by Windows NT to a printer gives the Print permissions to the well-known
1043 <emphasis>Everyone</emphasis> group. (The older clients of type Windows 9x/Me can only print to shared
1048 <title>Point'n'Print Client Drivers on Samba Servers</title>
1051 There is much confusion about what all this means. The question is often asked, <quote>Is it or is
1052 it not necessary for printer drivers to be installed on a Samba host in order to support printing from
1053 Windows clients?</quote> The answer to this is no, it is not necessary.
1057 Windows NT/2000 clients can, of course, also run their APW to install drivers <emphasis>locally</emphasis>
1058 (which then connect to a Samba-served print queue). This is the same method used by Windows 9x/Me
1059 clients. (However, a <emphasis>bug</emphasis> existed in Samba 2.2.0 that made Windows NT/2000 clients
1060 require that the Samba server possess a valid driver for the printer. This was fixed in Samba 2.2.1).
1064 But it is a new capability to install the printer drivers into the <smbconfsection>[print$]</smbconfsection>
1065 share of the Samba server, and a big convenience, too. Then <emphasis>all</emphasis> clients
1066 (including 95/98/ME) get the driver installed when they first connect to this printer share. The
1067 <emphasis>uploading</emphasis> or <emphasis>depositing</emphasis> of the driver into this
1068 <smbconfsection>[print$]</smbconfsection> share and the following binding of this driver to an existing
1069 Samba printer share can be achieved by different means:
1074 Running the <emphasis>APW</emphasis> on an NT/200x/XP Professional client (this does not work from 95/98/ME clients).
1078 Using the <emphasis>Imprints</emphasis> tool-set.
1082 Using the <emphasis>smbclient</emphasis> and <emphasis>rpcclient</emphasis> command-line tools.
1086 Using <emphasis>cupsaddsmb</emphasis> (only works for the CUPS
1087 printing system, not for LPR/LPD, LPRng, and so on).
1092 Samba does not use these uploaded drivers in any way to process spooled files. These drivers are utilized
1093 entirely by the clients who download and install them via the <quote>Point'n'Print</quote> mechanism
1094 supported by Samba. The clients use these drivers to generate print files in the format the printer
1095 (or the UNIX print system) requires. Print files received by Samba are handed over to the UNIX printing
1096 system, which is responsible for all further processing, as needed.
1101 <title>The Obsoleted [printer$] Section</title>
1104 Versions of Samba prior to 2.2 made it possible to use a share named
1105 <parameter>[printer$]</parameter>. This name was taken from the same named service created by
1106 Windows 9x/Me clients when a printer was shared by them. Windows 9x/Me printer servers always
1107 have a <smbconfsection>[printer$]</smbconfsection> service that provides read-only access (with
1108 no password required) to support printer driver downloads. However, Samba's initial
1109 implementation allowed for a parameter named <parameter>printer driver location</parameter> to
1110 be used on a per share basis. This specified the location of the driver files associated with
1111 that printer. Another parameter named <parameter>printer driver</parameter> provided a means of
1112 defining the printer driver name to be sent to the client.
1116 These parameters, including the <parameter>printer driver file</parameter> parameter,
1117 are now removed and cannot be used in installations of Samba-3. The share name
1118 <smbconfsection>[print$]</smbconfsection> is now used for the location of download-able printer
1119 drivers. It is taken from the <smbconfsection>[print$]</smbconfsection> service created
1120 by Windows NT PCs when a printer is shared by them. Windows NT print servers always have a
1121 <smbconfsection>[print$]</smbconfsection> service that provides read-write access (in the context
1122 of its ACLs) to support printer driver downloads and uploads. This does not mean Windows
1123 9x/Me clients are now thrown aside. They can use Samba's <smbconfsection>[print$]</smbconfsection>
1124 share support just fine.
1129 <title>Creating the [print$] Share</title>
1132 In order to support the uploading and downloading of printer driver files, you must first configure a
1133 file share named <smbconfsection>[print$]</smbconfsection>. The public name of this share is hard coded
1134 in the MS Windows clients. It cannot be renamed since Windows clients are programmed to search for a
1135 service of exactly this name if they want to retrieve printer driver files.
1139 You should modify the server's file to add the global parameters and create the
1140 <smbconfsection>[print$]</smbconfsection> file share (of course, some of the parameter values, such
1141 as <smbconfoption><name>path</name></smbconfoption> are arbitrary and should be replaced with appropriate values for your
1142 site). See <link linkend="prtdollar">next example</link>.
1146 <smbconfexample id="prtdollar">
1147 <title>[print\$] example</title>
1148 <smbconfsection>[global]</smbconfsection>
1149 <smbconfcomment>members of the ntadmin group should be able to add drivers and set</smbconfcomment>
1150 <smbconfcomment>printer properties. root is implicitly always a 'printer admin'.</smbconfcomment>
1151 <smbconfoption><name>printer admin</name><value>@ntadmin</value></smbconfoption>
1152 <member>...</member>
1153 <smbconfsection>[printers]</smbconfsection>
1154 <member>...</member>
1155 <smbconfsection>[print$]</smbconfsection>
1156 <smbconfoption><name>comment</name><value>Printer Driver Download Area</value></smbconfoption>
1157 <smbconfoption><name>path</name><value>/etc/samba/drivers</value></smbconfoption>
1158 <smbconfoption><name>browseable</name><value>yes</value></smbconfoption>
1159 <smbconfoption><name>guest ok</name><value>yes</value></smbconfoption>
1160 <smbconfoption><name>read only</name><value>yes</value></smbconfoption>
1161 <smbconfoption><name>write list</name><value>@ntadmin, root</value></smbconfoption>
1166 Of course, you also need to ensure that the directory named by the
1167 <smbconfoption><name>path</name></smbconfoption> parameter exists on the UNIX file system.
1173 <title>[print$] Section Parameters</title>
1176 The <smbconfsection>[print$]</smbconfsection> is a special section in &smb.conf;. It contains settings relevant to
1177 potential printer driver download and is used by windows clients for local print driver installation.
1178 The following parameters are frequently needed in this share section:
1182 <varlistentry><term><smbconfoption><name>comment</name><value>Printer Driver Download Area </value></smbconfoption></term>
1184 The comment appears next to the share name if it is listed in a share list (usually Windows
1185 clients will not see it, but it will also appear up in a <command>smbclient -L sambaserver
1190 <varlistentry><term><smbconfoption><name>path</name><value>/etc/samba/printers </value></smbconfoption></term>
1192 Is the path to the location of the Windows driver file deposit from the UNIX point of view.
1196 <varlistentry><term><smbconfoption><name>browseable</name><value>no </value></smbconfoption></term>
1198 Makes the <smbconfsection>[print$]</smbconfsection> share invisible to clients from the
1199 <guimenu>Network Neighborhood</guimenu>. However, you can still mount it from any client
1200 using the <command>net use g:\\sambaserver\print$</command> command in a DOS-box or the
1201 <guimenu>Connect network drive menu></guimenu> from Windows Explorer.
1205 <varlistentry><term><smbconfoption><name>guest ok</name><value>yes </value></smbconfoption></term>
1207 Gives read-only access to this share for all guest users. Access may be granted to
1208 download and install printer drivers on clients. The requirement for <parameter>guest ok
1209 = yes</parameter> depends on how your site is configured. If users will be guaranteed
1210 to have an account on the Samba host, then this is a non-issue.
1214 If all your Windows NT users are guaranteed to be authenticated by the Samba server
1215 (for example, if Samba authenticates via an NT domain server and the user has already been
1216 validated by the Domain Controller in order to logon to the Windows NT session), then guest
1217 access is not necessary. Of course, in a workgroup environment where you just want
1218 to print without worrying about silly accounts and security, then configure the share for
1219 guest access. You should consider adding <smbconfoption><name>map to guest</name><value>Bad
1220 User</value></smbconfoption> in the <smbconfsection>[global]</smbconfsection> section
1221 as well. Make sure you understand what this parameter does before using it.
1226 <varlistentry><term><smbconfoption><name>read only</name><value>yes </value></smbconfoption></term>
1228 Because we do not want everybody to upload driver files (or even change driver settings),
1229 we tagged this share as not writable.
1233 <varlistentry><term><smbconfoption><name>write list</name><value>@ntadmin, root </value></smbconfoption></term>
1235 The <smbconfsection>[print$]</smbconfsection> was made read-only by the previous
1236 setting so we should create a <parameter>write list</parameter> entry also. UNIX
1237 groups (denoted with a leading <quote>@</quote> character). Users listed here are allowed
1238 write-access (as an exception to the general public's read-only access), which they need to
1239 update files on the share. Normally, you will want to only name administrative-level user
1240 account in this setting. Check the file system permissions to make sure these accounts
1241 can copy files to the share. If this is a non-root account, then the account should also
1242 be mentioned in the global <smbconfoption><name>printer admin</name></smbconfoption>
1243 parameter. See the &smb.conf; man page for more information on configuring file shares.
1251 <title>The [print$] Share Directory</title>
1254 In order for a Windows NT print server to support the downloading of driver files by multiple client
1255 architectures, you must create several subdirectories within the <smbconfsection>[print$]</smbconfsection>
1256 service (i.e., the UNIX directory named by the <smbconfoption><name>path</name></smbconfoption>
1257 parameter). These correspond to each of the supported client architectures. Samba follows this model as
1258 well. Just like the name of the <smbconfsection>[print$]</smbconfsection> share itself, the subdirectories
1259 must be exactly the names listed below (you may leave out the subdirectories of architectures you do
1260 not need to support).
1264 Therefore, create a directory tree below the
1265 <smbconfsection>[print$]</smbconfsection> share for each architecture you wish
1266 to support like this:
1269 <para><programlisting>
1271 |--W32X86 # serves drivers to Windows NT x86
1272 |--WIN40 # serves drivers to Windows 95/98
1273 |--W32ALPHA # serves drivers to Windows NT Alpha_AXP
1274 |--W32MIPS # serves drivers to Windows NT R4000
1275 |--W32PPC # serves drivers to Windows NT PowerPC
1279 <important><title>Required permissions</title>
1281 In order to add a new driver to your Samba host, one of two conditions must hold true:
1286 The account used to connect to the Samba host must have a UID of 0 (i.e., a root account).
1290 The account used to connect to the Samba host must be named in the <emphasis>printer admin</emphasis>list.
1295 Of course, the connected account must still have write access to add files to the subdirectories beneath
1296 <smbconfsection>[print$]</smbconfsection>. Remember that all file shares are set to <quote>read-only</quote> by default.
1301 Once you have created the required <smbconfsection>[print$]</smbconfsection> service and
1302 associated subdirectories, go to a Windows NT 4.0/200x/XP client workstation. Open <guiicon>Network
1303 Neighborhood</guiicon> or <guiicon>My Network Places</guiicon> and browse for the Samba host. Once you
1304 have located the server, navigate to its <guiicon>Printers and Faxes</guiicon> folder. You should see
1305 an initial listing of printers that matches the printer shares defined on your Samba host.
1311 <title>Installing Drivers into [print$]</title>
1314 Have you successfully created the <smbconfsection>[print$]</smbconfsection> share in &smb.conf;, and have your forced Samba
1315 to re-read its &smb.conf; file? Good. But you are not yet ready to use the new facility. The client driver
1316 files need to be installed into this share. So far it is still an empty share. Unfortunately, it is
1317 not enough to just copy the driver files over. They need to be
1318 correctly installed so that appropriate
1319 records for each driver will exist in the Samba internal databases so it can provide the correct
1320 drivers as they are requested from MS Windows clients. And that is a bit tricky, to say the least. We
1321 now discuss two alternative ways to install the drivers into <smbconfsection>[print$]</smbconfsection>:
1326 Using the Samba command-line utility <command>rpcclient</command> with its various subcommands (here:
1327 <command>adddriver</command> and <command>setdriver</command>) from any UNIX workstation.
1331 Running a GUI (<guiicon>Printer Properties</guiicon> and <guiicon>Add Printer Wizard</guiicon>)
1332 from any Windows NT/200x/XP client workstation.
1337 The latter option is probably the easier one (even if the process may seem a little bit weird at first).
1341 <title>Add Printer Wizard Driver Installation</title>
1344 The initial listing of printers in the Samba host's <guiicon>Printers</guiicon> folder accessed from a
1345 client's Explorer will have no real printer driver assigned to them. By default this driver name is set
1346 to a null string. This must be changed now. The local <guiicon>Add Printer Wizard</guiicon> (APW), run from
1347 NT/2000/XP clients, will help us in this task.
1351 Installation of a valid printer driver is not straightforward. You must attempt
1352 to view the printer properties for the printer to which you want the driver assigned. Open the Windows
1353 Explorer, open <guiicon>Network Neighborhood</guiicon>, browse to the Samba host, open Samba's <guiicon>Printers</guiicon>
1354 folder, right-click on the printer icon and select <guimenu>Properties...</guimenu>. You are now trying to
1355 view printer and driver properties for a queue that has this default <constant>NULL</constant> driver
1356 assigned. This will result in the following error message:
1360 Device settings cannot be displayed. The driver for the specified printer is not installed,
1361 only spooler properties will be displayed. Do you want to install the driver now?
1365 Do not click on <guibutton>Yes</guibutton>! Instead, click on <guibutton>No</guibutton> in the error dialog.
1366 Only now you will be presented with the printer properties window. From here, the way to assign a driver
1367 to a printer is open to us. You now have the choice of:
1372 Select a driver from the pop-up list of installed drivers. Initially this list will be empty.
1376 Click on <guibutton>New Driver</guibutton> to install a new printer driver (which will
1382 Once the APW is started, the procedure is exactly the same as the one you are familiar with in Windows (we
1383 assume here that you are familiar with the printer driver installations procedure on Windows NT). Make sure
1384 your connection is, in fact, setup as a user with <smbconfoption><name>printer admin</name></smbconfoption>
1385 privileges (if in doubt, use <command>smbstatus</command> to check for this). If you wish to install
1386 printer drivers for client operating systems other than <application>Windows NT x86</application>,
1387 you will need to use the <guilabel>Sharing</guilabel> tab of the printer properties dialog.
1391 Assuming you have connected with an administrative (or root) account (as named by the
1392 <smbconfoption><name>printer admin</name></smbconfoption> parameter), you will also be able to modify
1393 other printer properties such as ACLs and default device settings using this dialog. For the default
1394 device settings, please consider the advice given further in <link linkend="inst-rpc">Installing Print Drivers Using <command>rpcclient</command></link>.
1398 <sect2 id="inst-rpc">
1399 <title>Installing Print Drivers Using <command>rpcclient</command></title>
1402 The second way to install printer drivers into <smbconfsection>[print$]</smbconfsection> and set them
1403 up in a valid way is to do it from the UNIX command line. This involves four distinct steps:
1408 Gather info about required driver files and collect the files.
1412 Deposit the driver files into the <smbconfsection>[print$]</smbconfsection> share's correct subdirectories
1413 (possibly by using <command>smbclient</command>).
1417 Run the <command>rpcclient</command> command line utility once with the <command>adddriver</command>
1422 Run <command>rpcclient</command> a second time with the <command>setdriver</command> subcommand.
1427 We provide detailed hints for each of these steps in the paragraphs that follow.
1431 <title>Identifying Driver Files</title>
1434 To find out about the driver files, you have two options. You could check the contents of the driver
1435 CDROM that came with your printer. Study the <filename>*.inf</filename> files lcoated on the CDROM. This
1436 may not be possible, since the <filename>*.inf</filename> file might be missing. Unfortunately, vendors have now started
1437 to use their own installation programs. These installations packages are often in some Windows platform
1438 archive format. Additionally, the files may be re-named during the installation process. This makes it
1439 extremely difficult to identify the driver files required.
1443 Then you only have the second option. Install the driver locally on a Windows client and
1444 investigate which file names and paths it uses after they are installed. (You need to repeat
1445 this procedure for every client platform you want to support. We show it here for the
1446 <application>W32X86</application> platform only, a name used by Microsoft for all Windows NT/200x/XP
1451 A good method to recognize the driver files is to print the test page from the driver's
1452 <guilabel>Properties</guilabel> dialog (<guilabel>General</guilabel> tab). Then look at the list of
1453 driver files named on the printout. You'll need to recognize what Windows (and Samba) are calling the
1454 <guilabel>Driver File</guilabel>, <guilabel>Data File</guilabel>, <guilabel>Config File</guilabel>,
1455 <guilabel>Help File</guilabel> and (optionally) the <guilabel>Dependent Driver Files</guilabel>
1456 (this may vary slightly for Windows NT). You need to take a note of all file names for the next steps.
1460 Another method to quickly test the driver filenames and related paths is provided by the
1461 <command>rpcclient</command> utility. Run it with <command>enumdrivers</command> or with the
1462 <command>getdriver</command> subcommand, each at the <filename>3</filename> info level. In the following example,
1463 <emphasis>TURBO_XP</emphasis> is the name of the Windows PC (in this case it was a Windows XP Professional
1464 laptop). I installed the driver locally to TURBO_XP, from a Samba server called <constant>KDE-BITSHOP</constant>.
1465 We could run an interactive <command>rpcclient</command> session; then we would get an
1466 <command>rpcclient /></command> prompt and would type the subcommands at this prompt. This is left as
1467 a good exercise to the reader. For now, we use <command>rpcclient</command> with the <option>-c</option>
1468 parameter to execute a single subcommand line and exit again. This is the method you would use if you
1469 want to create scripts to automate the procedure for a large number of printers and drivers. Note the
1470 different quotes used to overcome the different spaces in between words:
1474 &rootprompt;<userinput>rpcclient -U'Danka%xxxx' -c \
1475 'getdriver "Heidelberg Digimaster 9110 (PS)" 3' TURBO_XP</userinput>
1476 cmd = getdriver "Heidelberg Digimaster 9110 (PS)" 3
1479 Printer Driver Info 3:
1481 Driver Name: [Heidelberg Digimaster 9110 (PS)]
1482 Architecture: [Windows NT x86]
1483 Driver Path: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.DLL]
1484 Datafile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.ppd]
1485 Configfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.DLL]
1486 Helpfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.HLP]
1488 Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.DLL]
1489 Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.INI]
1490 Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.dat]
1491 Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.cat]
1492 Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.def]
1493 Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hre]
1494 Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.vnd]
1495 Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hlp]
1496 Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01Aux.dll]
1497 Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.NTF]
1504 You may notice that this driver has quite a large number of <guilabel>Dependent files</guilabel>
1505 (there are worse cases, however). Also, strangely, the
1506 <guilabel>Driver File</guilabel> is tagged here
1507 <guilabel>Driver Path</guilabel>. We do not yet have support for the so-called
1508 <application>WIN40</application> architecture installed. This name is used by Microsoft for the Windows
1509 9x/Me platforms. If we want to support these, we need to install the Windows 9x/Me driver files in
1510 addition to those for <application>W32X86</application> (i.e., the Windows NT72000/XP clients) onto a
1511 Windows PC. This PC can also host the Windows 9x/Me drivers, even if it runs on Windows NT, 2000 or XP.
1515 Since the <smbconfsection>[print$]</smbconfsection> share is usually accessible through the <guiicon>Network
1516 Neighborhood</guiicon>, you can also use the UNC notation from Windows Explorer to poke at it. The Windows
1517 9x/Me driver files will end up in subdirectory <filename>0</filename> of the <filename>WIN40</filename>
1518 directory. The full path to access them will be <filename>\\WINDOWSHOST\print$\WIN40\0\</filename>.
1522 More recent drivers on Windows 2000 and Windows XP are installed into the <quote>3</quote> subdirectory
1523 instead of the <quote>2</quote>. The version 2 of drivers, as used in Windows NT, were running in Kernel
1524 Mode. Windows 2000 changed this. While it still can use the Kernel Mode drivers (if this is enabled by
1525 the Admin), its native mode for printer drivers is User Mode execution. This requires drivers designed
1526 for this. These types of drivers install into the <quote>3</quote> subdirectory.
1531 <title>Obtaining Driver Files from Windows Client [print$] Shares</title>
1534 Now we need to collect all the driver files we identified in our previous step. Where do we get them
1535 from? Well, why not retrieve them from the very PC and the same <smbconfsection>[print$]</smbconfsection>
1536 share that we investigated in our last step to identify the files? We can use <command>smbclient</command>
1537 to do this. We will use the paths and names that were leaked to us by <command>getdriver</command>. The
1538 listing is edited to include line breaks for readability:
1542 &rootprompt;<userinput>smbclient //TURBO_XP/print\$ -U'Danka%xxxx' \
1543 -c 'cd W32X86/2;mget HD*_de.* hd*ppd Hd*_de.* Hddm*dll HDN*Aux.DLL'</userinput>
1545 added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
1546 Got a positive name query response from 10.160.50.8 ( 10.160.50.8 )
1547 Domain=[DEVELOPMENT] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
1548 <prompt>Get file Hddm91c1_de.ABD? </prompt><userinput>n</userinput>
1549 <prompt>Get file Hddm91c1_de.def? </prompt><userinput>y</userinput>
1550 getting file \W32X86\2\Hddm91c1_de.def of size 428 as Hddm91c1_de.def
1551 <prompt>Get file Hddm91c1_de.DLL? </prompt><userinput>y</userinput>
1552 getting file \W32X86\2\Hddm91c1_de.DLL of size 876544 as Hddm91c1_de.DLL
1557 After this command is complete, the files are in our current local directory. You probably have noticed
1558 that this time we passed several commands to the <option>-c</option> parameter, separated by semi-colons.
1559 This effects that all commands are executed in sequence on the remote Windows server before smbclient
1564 Remember to repeat the procedure for the <application>WIN40</application> architecture should
1565 you need to support Windows 9x/Me/XP clients. Remember too, the files for these architectures are in the
1566 <filename>WIN40/0/</filename> subdirectory. Once this is complete, we can run <command>smbclient ...
1567 put</command> to store the collected files on the Samba server's <smbconfsection>[print$]</smbconfsection>
1573 <title>Installing Driver Files into [print$]</title>
1576 We are now going to locate the driver files into the <smbconfsection>[print$]</smbconfsection>
1577 share. Remember, the UNIX path to this share has been defined
1578 previously in your words missing here. You
1579 also have created subdirectories for the different Windows client types you want to
1580 support. Supposing your <smbconfsection>[print$]</smbconfsection> share maps to the UNIX path
1581 <filename>/etc/samba/drivers/</filename>, your driver files should now go here:
1586 For all Windows NT, 2000 and XP clients into <filename>/etc/samba/drivers/W32X86/</filename> but
1587 not (yet) into the <filename>2</filename> subdirectory.
1591 For all Windows 95, 98 and ME clients into <filename>/etc/samba/drivers/WIN40/</filename> but not
1592 (yet) into the <filename>0</filename> subdirectory.
1597 We again use smbclient to transfer the driver files across the network. We specify the same files
1598 and paths as were leaked to us by running <command>getdriver</command> against the original
1599 <emphasis>Windows</emphasis> install. However, now we are going to store the files into a
1600 <emphasis>Samba/UNIX</emphasis> print server's <smbconfsection>[print$]</smbconfsection> share.
1604 &rootprompt;<userinput>smbclient //SAMBA-CUPS/print\$ -U'root%xxxx' -c \
1605 'cd W32X86; put HDNIS01_de.DLL; \
1606 put Hddm91c1_de.ppd; put HDNIS01U_de.DLL; \
1607 put HDNIS01U_de.HLP; put Hddm91c1_de.DLL; \
1608 put Hddm91c1_de.INI; put Hddm91c1KMMin.DLL; \
1609 put Hddm91c1_de.dat; put Hddm91c1_de.dat; \
1610 put Hddm91c1_de.def; put Hddm91c1_de.hre; \
1611 put Hddm91c1_de.vnd; put Hddm91c1_de.hlp; \
1612 put Hddm91c1_de_reg.HLP; put HDNIS01Aux.dll; \
1613 put HDNIS01_de.NTF'</userinput>
1615 added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
1616 Got a positive name query response from 10.160.51.162 ( 10.160.51.162 )
1617 Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
1618 putting file HDNIS01_de.DLL as \W32X86\HDNIS01_de.DLL
1619 putting file Hddm91c1_de.ppd as \W32X86\Hddm91c1_de.ppd
1620 putting file HDNIS01U_de.DLL as \W32X86\HDNIS01U_de.DLL
1621 putting file HDNIS01U_de.HLP as \W32X86\HDNIS01U_de.HLP
1622 putting file Hddm91c1_de.DLL as \W32X86\Hddm91c1_de.DLL
1623 putting file Hddm91c1_de.INI as \W32X86\Hddm91c1_de.INI
1624 putting file Hddm91c1KMMin.DLL as \W32X86\Hddm91c1KMMin.DLL
1625 putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat
1626 putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat
1627 putting file Hddm91c1_de.def as \W32X86\Hddm91c1_de.def
1628 putting file Hddm91c1_de.hre as \W32X86\Hddm91c1_de.hre
1629 putting file Hddm91c1_de.vnd as \W32X86\Hddm91c1_de.vnd
1630 putting file Hddm91c1_de.hlp as \W32X86\Hddm91c1_de.hlp
1631 putting file Hddm91c1_de_reg.HLP as \W32X86\Hddm91c1_de_reg.HLP
1632 putting file HDNIS01Aux.dll as \W32X86\HDNIS01Aux.dll
1633 putting file HDNIS01_de.NTF as \W32X86\HDNIS01_de.NTF
1636 Whew &smbmdash; that was a lot of typing! Most drivers are a lot smaller &smbmdash; many only having three generic
1637 PostScript driver files plus one PPD. While we did retrieve the files from the <filename>2</filename>
1638 subdirectory of the <filename>W32X86</filename> directory from the Windows box, we do not put them
1639 (for now) in this same subdirectory of the Samba box. This relocation will automatically be done by the
1640 <command>adddriver</command> command, which we will run shortly (and do not forget to also put the files
1641 for the Windows 9x/Me architecture into the <filename>WIN40/</filename> subdirectory should you need them).
1646 <title><command>smbclient</command> to Confirm Driver Installation</title>
1649 For now we verify that our files are there. This can be done with <command>smbclient</command>, too
1650 (but, of course, you can log in via SSH also and do this through a standard UNIX shell access):
1654 &rootprompt;<userinput>smbclient //SAMBA-CUPS/print\$ -U 'root%xxxx' \
1655 -c 'cd W32X86; pwd; dir; cd 2; pwd; dir'</userinput>
1656 added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
1657 Got a positive name query response from 10.160.51.162 ( 10.160.51.162 )
1658 Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.8a]
1660 Current directory is \\SAMBA-CUPS\print$\W32X86\
1661 . D 0 Sun May 4 03:56:35 2003
1662 .. D 0 Thu Apr 10 23:47:40 2003
1663 2 D 0 Sun May 4 03:56:18 2003
1664 HDNIS01Aux.dll A 15356 Sun May 4 03:58:59 2003
1665 Hddm91c1KMMin.DLL A 46966 Sun May 4 03:58:59 2003
1666 HDNIS01_de.DLL A 434400 Sun May 4 03:58:59 2003
1667 HDNIS01_de.NTF A 790404 Sun May 4 03:56:35 2003
1668 Hddm91c1_de.DLL A 876544 Sun May 4 03:58:59 2003
1669 Hddm91c1_de.INI A 101 Sun May 4 03:58:59 2003
1670 Hddm91c1_de.dat A 5044 Sun May 4 03:58:59 2003
1671 Hddm91c1_de.def A 428 Sun May 4 03:58:59 2003
1672 Hddm91c1_de.hlp A 37699 Sun May 4 03:58:59 2003
1673 Hddm91c1_de.hre A 323584 Sun May 4 03:58:59 2003
1674 Hddm91c1_de.ppd A 26373 Sun May 4 03:58:59 2003
1675 Hddm91c1_de.vnd A 45056 Sun May 4 03:58:59 2003
1676 HDNIS01U_de.DLL A 165888 Sun May 4 03:58:59 2003
1677 HDNIS01U_de.HLP A 19770 Sun May 4 03:58:59 2003
1678 Hddm91c1_de_reg.HLP A 228417 Sun May 4 03:58:59 2003
1679 40976 blocks of size 262144. 709 blocks available
1681 Current directory is \\SAMBA-CUPS\print$\W32X86\2\
1682 . D 0 Sun May 4 03:56:18 2003
1683 .. D 0 Sun May 4 03:56:35 2003
1684 ADOBEPS5.DLL A 434400 Sat May 3 23:18:45 2003
1685 laserjet4.ppd A 9639 Thu Apr 24 01:05:32 2003
1686 ADOBEPSU.DLL A 109568 Sat May 3 23:18:45 2003
1687 ADOBEPSU.HLP A 18082 Sat May 3 23:18:45 2003
1688 PDFcreator2.PPD A 15746 Sun Apr 20 22:24:07 2003
1689 40976 blocks of size 262144. 709 blocks available
1693 Notice that there are already driver files present in the <filename>2</filename> subdirectory (probably
1694 from a previous installation). Once the files for the new driver are there too, you are still a few
1695 steps away from being able to use them on the clients. The only thing you could do now is to retrieve
1696 them from a client just like you retrieve ordinary files from a file share, by opening print$ in Windows
1697 Explorer. But that wouldn't install them per Point'n'Print. The reason
1698 is: Samba does not yet know that
1699 these files are something special, namely <emphasis>printer driver files</emphasis> and it does not know
1700 to which print queue(s) these driver files belong.
1705 <title>Running <command>rpcclient</command> with <command>adddriver</command></title>
1708 Next, you must tell Samba about the special category of the files you just uploaded into the
1709 <smbconfsection>[print$]</smbconfsection> share. This is done by the <command>adddriver</command>
1710 command. It will prompt Samba to register the driver files into its internal TDB database files. The
1711 following command and its output has been edited, again, for readability:
1715 &rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" \
1716 "dm9110:HDNIS01_de.DLL: \
1717 Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP: \
1718 NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \
1719 Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \
1720 Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
1721 HDNIS01Aux.dll,HDNIS01_de.NTF, \
1722 Hddm91c1_de_reg.HLP' SAMBA-CUPS</userinput>
1724 cmd = adddriver "Windows NT x86" \
1725 "dm9110:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL: \
1726 HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \
1727 Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \
1728 Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
1729 HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
1731 Printer Driver dm9110 successfully installed.
1735 After this step, the driver should be recognized by Samba on the print server. You need to be very
1736 careful when typing the command. Don't exchange the order of the fields. Some changes would lead to
1737 an <computeroutput>NT_STATUS_UNSUCCESSFUL</computeroutput> error message. These become obvious. Other
1738 changes might install the driver files successfully, but render the driver unworkable. So take care!
1739 Hints about the syntax of the adddriver command are in the man page. The CUPS printing chapter
1740 provides a more detailed description, should you need it.
1745 <title>Checking <command>adddriver</command> Completion</title>
1748 One indication for Samba's recognition of the files as driver files is the <computeroutput>successfully
1749 installed</computeroutput> message. Another one is the fact that our files have been moved by the
1750 <command>adddriver</command> command into the <filename>2</filename> subdirectory. You can check this
1751 again with <command>smbclient</command>:
1755 &rootprompt;<userinput>smbclient //SAMBA-CUPS/print\$ -Uroot%xx \
1756 -c 'cd W32X86;dir;pwd;cd 2;dir;pwd'</userinput>
1757 added interface ip=10.160.51.162 bcast=10.160.51.255 nmask=255.255.252.0
1758 Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
1760 Current directory is \\SAMBA-CUPS\print$\W32X86\
1761 . D 0 Sun May 4 04:32:48 2003
1762 .. D 0 Thu Apr 10 23:47:40 2003
1763 2 D 0 Sun May 4 04:32:48 2003
1764 40976 blocks of size 262144. 731 blocks available
1766 Current directory is \\SAMBA-CUPS\print$\W32X86\2\
1767 . D 0 Sun May 4 04:32:48 2003
1768 .. D 0 Sun May 4 04:32:48 2003
1769 DigiMaster.PPD A 148336 Thu Apr 24 01:07:00 2003
1770 ADOBEPS5.DLL A 434400 Sat May 3 23:18:45 2003
1771 laserjet4.ppd A 9639 Thu Apr 24 01:05:32 2003
1772 ADOBEPSU.DLL A 109568 Sat May 3 23:18:45 2003
1773 ADOBEPSU.HLP A 18082 Sat May 3 23:18:45 2003
1774 PDFcreator2.PPD A 15746 Sun Apr 20 22:24:07 2003
1775 HDNIS01Aux.dll A 15356 Sun May 4 04:32:18 2003
1776 Hddm91c1KMMin.DLL A 46966 Sun May 4 04:32:18 2003
1777 HDNIS01_de.DLL A 434400 Sun May 4 04:32:18 2003
1778 HDNIS01_de.NTF A 790404 Sun May 4 04:32:18 2003
1779 Hddm91c1_de.DLL A 876544 Sun May 4 04:32:18 2003
1780 Hddm91c1_de.INI A 101 Sun May 4 04:32:18 2003
1781 Hddm91c1_de.dat A 5044 Sun May 4 04:32:18 2003
1782 Hddm91c1_de.def A 428 Sun May 4 04:32:18 2003
1783 Hddm91c1_de.hlp A 37699 Sun May 4 04:32:18 2003
1784 Hddm91c1_de.hre A 323584 Sun May 4 04:32:18 2003
1785 Hddm91c1_de.ppd A 26373 Sun May 4 04:32:18 2003
1786 Hddm91c1_de.vnd A 45056 Sun May 4 04:32:18 2003
1787 HDNIS01U_de.DLL A 165888 Sun May 4 04:32:18 2003
1788 HDNIS01U_de.HLP A 19770 Sun May 4 04:32:18 2003
1789 Hddm91c1_de_reg.HLP A 228417 Sun May 4 04:32:18 2003
1790 40976 blocks of size 262144. 731 blocks available
1794 Another verification is that the timestamp of the printing TDB files is now updated
1795 (and possibly their file size has increased).
1800 <title>Check Samba for Driver Recognition</title>
1803 Now the driver should be registered with Samba. We can easily verify this, and will do so in a
1804 moment. However, this driver is not yet associated with a particular printer. We may check the driver
1805 status of the files by at least three methods:
1810 From any Windows client browse Network Neighborhood, find the Samba host and open the Samba
1811 <guiicon>Printers and Faxes</guiicon> folder. Select any printer icon, right-click and select
1812 the printer <guimenuitem>Properties</guimenuitem>. Click the <guilabel>Advanced</guilabel>
1813 tab. Here is a field indicating the driver for that printer. A drop-down menu allows you to
1814 change that driver (be careful not to do this unwittingly). You can use this list to view
1815 all drivers known to Samba. Your new one should be among them. (Each type of client will only
1816 see his own architecture's list. If you do not have every driver installed for each platform,
1817 the list will differ if you look at it from Windows95/98/ME or Windows NT/2000/XP.)
1821 From a Windows 200x/XP client (not Windows NT) browse <guiicon>Network Neighborhood</guiicon>,
1822 search for the Samba server and open the server's <guiicon>Printers</guiicon> folder,
1823 right-click on the white background (with no printer highlighted). Select <guimenuitem>Server
1824 Properties</guimenuitem>. On the <guilabel>Drivers</guilabel> tab you will see the new driver
1825 listed. This view enables you to also inspect the list of files belonging to that driver
1826 (this does not work on Windows NT, but only on Windows 2000 and Windows XP; Windows NT does not
1827 provide the <guimenuitem>Drivers</guimenuitem> tab). An
1828 alternative and much quicker method for
1829 Windows 2000/XP to start this dialog is by typing into a DOS box (you must of course adapt the
1830 name to your Samba server instead of <replaceable>SAMBA-CUPS</replaceable>):
1833 <para><userinput>rundll32 printui.dll,PrintUIEntry /s /t2 /n\\<replaceable>SAMBA-CUPS</replaceable></userinput></para>
1837 From a UNIX prompt, run this command (or a variant thereof) where
1838 <replaceable>SAMBA-CUPS</replaceable> is the name of the Samba host and xxxx represents the
1839 actual Samba password assigned to root:
1842 <para><userinput>rpcclient -U'root%xxxx' -c 'enumdrivers' <replaceable>SAMBA-CUPS</replaceable></userinput></para>
1845 You will see a listing of all drivers Samba knows about. Your new one should be among
1846 them. But it is only listed under the <parameter>[Windows NT x86]</parameter> heading, not under
1847 <smbconfsection>[Windows 4.0]</smbconfsection>, since you didn't install that part. Or did you?
1848 You will see a listing of all drivers Samba knows about. Your new one should be among them. In
1849 our example it is named <constant>dm9110</constant>. Note that the third column shows the other
1850 installed drivers twice, one time for each supported architecture. Our new driver only shows up
1851 for <application>Windows NT 4.0 or 2000</application>. To have it present for <application>Windows
1852 95, 98 and ME</application>, you'll have to repeat the whole procedure with the WIN40 architecture
1859 <title>Specific Driver Name Flexibility</title>
1862 You can name the driver as you like. If you repeat the <command>adddriver</command> step with the same
1863 files as before but with a different driver name, it will work the same:
1867 &rootprompt;<userinput>rpcclient -Uroot%xxxx \
1868 -c 'adddriver "Windows NT x86" \
1869 "mydrivername:HDNIS01_de.DLL: \
1870 Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP: \
1871 NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \
1872 Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \
1873 Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
1874 HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP' SAMBA-CUPS
1877 cmd = adddriver "Windows NT x86" \
1878 "mydrivername:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:\
1879 HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \
1880 Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \
1881 Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
1882 HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
1884 Printer Driver mydrivername successfully installed.
1888 You will be able to bind that driver to any print queue (however, you are responsible that
1889 you associate drivers to queues that make sense with respect to target printers). You cannot run the
1890 <command>rpcclient</command> <command>adddriver</command> command repeatedly. Each run consumes the
1891 files you had put into the <smbconfsection>[print$]</smbconfsection> share by moving them into the
1892 respective subdirectories. So you must execute an <command>smbclient ... put</command> command before
1893 each <command>rpcclient ... adddriver</command> command.
1898 <title>Running <command>rpcclient</command> with the <command>setdriver</command></title>
1901 Samba needs to know which printer owns which driver. Create a mapping of the driver to a printer, and
1902 store this info in Samba's memory, the TDB files. The <command>rpcclient setdriver</command> command
1903 achieves exactly this:
1907 &rootprompt;<userinput>rpcclient -U'root%xxxx' -c 'setdriver dm9110 mydrivername' <replaceable>SAMBA-CUPS</replaceable></userinput>
1908 cmd = setdriver dm9110 mydrivername
1910 Successfully set dm9110 to driver mydrivername.
1914 Ah, no, I did not want to do that. Repeat, this time with the name I intended:
1918 &rootprompt;<userinput>rpcclient -U'root%xxxx' -c 'setdriver dm9110 dm9110' <replaceable>SAMBA-CUPS</replaceable></userinput>
1919 cmd = setdriver dm9110 dm9110
1920 Successfully set dm9110 to driver dm9110.
1924 The syntax of the command is:
1926 <userinput>rpcclient -U'root%<replaceable>sambapassword</replaceable>' -c 'setdriver <replaceable>printername</replaceable> \
1927 <replaceable>drivername</replaceable>' <replaceable>SAMBA-Hostname</replaceable></userinput>.
1929 Now we have done most of the work, but not all of it.
1933 The <command>setdriver</command> command will only succeed if the
1934 printer is already known to Samba. A
1935 bug in 2.2.x prevented Samba from recognizing freshly installed printers. You had to restart Samba,
1936 or at least send an HUP signal to all running smbd processes to work around this: <userinput>kill -HUP
1937 `pidof smbd`</userinput>.
1944 <title>Client Driver Installation Procedure</title>
1947 As Don Quixote said: <quote>The proof of the pudding is in the eating.</quote> The proof
1948 for our setup lies in the printing. So let's install the printer driver onto the client PCs. This is
1949 not as straightforward as it may seem. Read on.
1953 <title>First Client Driver Installation</title>
1956 Especially important is the installation onto the first client PC (for each architectural platform
1957 separately). Once this is done correctly, all further clients are easy to setup and shouldn't need further
1958 attention. What follows is a description for the recommended first procedure. You work now from a client
1959 workstation. You should guarantee that your connection is not unwittingly mapped to <emphasis>bad
1960 user</emphasis> nobody. In a DOS box type:
1963 <para><userinput>net use \\<replaceable>SAMBA-SERVER</replaceable>\print$ /user:root</userinput></para>
1966 Replace root, if needed, by another valid <smbconfoption><name>printer admin</name></smbconfoption> user as given in
1967 the definition. Should you already be connected as a different user, you will get an error message. There
1968 is no easy way to get rid of that connection, because Windows does not seem to know a concept of logging
1969 off from a share connection (do not confuse this with logging off from the local workstation; that is
1970 a different matter). On Windows NT/2K, you can force a logoff from all smb/cifs connections by restarting the
1971 <quote>workstation</quote> service. You can try to close all Windows file explorer and Internet Explorer for
1972 Windows. As a last resort, you may have to reboot. Make sure there is no automatic reconnection set up. It may be
1973 easier to go to a different workstation and try from there. After you have made sure you are connected
1974 as a printer admin user (you can check this with the <command>smbstatus</command> command on Samba),
1975 do this from the Windows workstation:
1980 Open <guiicon>Network Neighborhood</guiicon>.
1984 Browse to Samba server.
1988 Open its <guiicon>Printers and Faxes</guiicon> folder.
1992 Highlight and right-click on the printer.
1996 Select <guimenuitem>Connect</guimenuitem> (for Windows NT4/200x
1997 it is possibly <guimenuitem>Install</guimenuitem>).
2002 A new printer (named <replaceable>printername</replaceable> on Samba-server) should now have
2003 appeared in your <emphasis>local</emphasis> Printer folder (check <guimenu>Start</guimenu> --
2004 <guimenuitem>Settings</guimenuitem> -- <guimenuitem>Control Panel</guimenuitem> -- <guiicon>Printers
2005 and Faxes</guiicon>).
2009 Most likely you are now tempted to try to print a test page. After all, you now can open the printer
2010 properties, and on the <guimenu>General</guimenu> tab there is a button offering to do just that. But
2011 chances are that you get an error message saying <errorname>Unable to print Test Page</errorname>. The
2012 reason might be that there is not yet a valid Device Mode set for the driver, or that the <quote>Printer
2013 Driver Data</quote> set is still incomplete.
2017 You must make sure that a valid <parameter>Device Mode</parameter> is set for the
2018 driver. We now explain what that means.
2023 <title>Setting Device Modes on New Printers</title>
2026 For a printer to be truly usable by a Windows NT/200x/XP client, it must possess:
2031 A valid <emphasis>Device Mode</emphasis> generated by the driver for the printer (defining things
2032 like paper size, orientation and duplex settings).
2036 A complete set of <emphasis>Printer Driver Data</emphasis> generated by the driver.
2041 If either of these is incomplete, the clients can produce less than optimal output at best. In the
2042 worst cases, unreadable garbage or nothing at all comes from the printer or it produces a harvest of
2043 error messages when attempting to print. Samba stores the named values and all printing related information in
2044 its internal TDB database files <filename>(ntprinters.tdb</filename>, <filename>ntdrivers.tdb</filename>,
2045 <filename>printing.tdb</filename> and <filename>ntforms.tdb</filename>).
2049 What do these two words stand for? Basically, the Device Mode and the set of Printer Driver Data is a
2050 collection of settings for all print queue properties, initialized in a sensible way. Device Modes and
2051 Printer Driver Data should initially be set on the print server (the Samba host) to healthy
2052 values so the clients can start to use them immediately. How do we set these initial healthy values?
2053 This can be achieved by accessing the drivers remotely from an NT (or 200x/XP) client, as is discussed
2054 in the following paragraphs.
2058 Be aware that a valid Device Mode can only be initiated by a
2059 <smbconfoption><name>printer admin</name></smbconfoption>, or root
2060 (the reason should be obvious). Device Modes can only be correctly
2061 set by executing the printer driver program itself. Since Samba cannot execute this Win32 platform driver
2062 code, it sets this field initially to NULL (which is not a valid setting for clients to use). Fortunately,
2063 most drivers automatically generate the Printer Driver Data that is needed when they are uploaded to the
2064 <smbconfsection>[print$]</smbconfsection> share with the help of the APW or rpcclient.
2068 The generation and setting of a first valid Device Mode, however, requires some tickling from a client,
2069 to set it on the Samba server. The easiest means of doing so is to simply change the page orientation on
2070 the server's printer. This executes enough of the printer driver program on the client for the desired
2071 effect to happen, and feeds back the new Device Mode to our Samba server. You can use the native Windows
2072 NT/200x/XP printer properties page from a Window client for this:
2077 Browse the <guiicon>Network Neighborhood.</guiicon>
2081 Find the Samba server.
2085 Open the Samba server's <guiicon>Printers and Faxes</guiicon> folder.
2089 Highlight the shared printer in question.
2093 Right-click on the printer (you may already be here, if you followed the last section's description).
2097 At the bottom of the context menu select <guimenu>Properties</guimenu> (if the menu still offers the
2098 <guimenuitem>Connect</guimenuitem> entry further above, you
2099 need to click on that one first to achieve the driver
2100 installation as shown in the last section).
2104 Go to the <guilabel>Advanced</guilabel> tab; click on <guibutton>Printing Defaults</guibutton>.
2108 Change the <guimenuitem>Portrait</guimenuitem> page setting to <guimenuitem>Landscape</guimenuitem> (and back).
2112 Make sure to apply changes between swapping the page orientation to cause the change to actually take effect.
2116 While you are at it, you may also want to set the desired printing defaults here, which then apply to all future
2117 client driver installations on the remaining from now on.
2122 This procedure has executed the printer driver program on the client platform and fed back the correct
2123 Device Mode to Samba, which now stored it in its TDB files. Once the driver is installed on the client,
2124 you can follow the analogous steps by accessing the <emphasis>local</emphasis> <guiicon>Printers</guiicon>
2125 folder, too, if you are a Samba printer admin user. From now on, printing should work as expected.
2129 Samba includes a service level parameter name <parameter>default devmode</parameter> for generating a default
2130 Device Mode for a printer. Some drivers will function well with Samba's default set of properties. Others
2131 may crash the client's spooler service. So use this parameter with caution. It is always better to have
2132 the client generate a valid device mode for the printer and store it on the server for you.
2137 <title>Additional Client Driver Installation</title>
2140 Every additional driver may be installed, along the lines described
2141 above. Browse network, open the
2142 <guiicon>Printers</guiicon> folder on Samba server, right-click on <guiicon>Printer</guiicon> and choose
2143 <guimenuitem>Connect...</guimenuitem>. Once this completes (should be not more than a few seconds,
2144 but could also take a minute, depending on network conditions), you should find the new printer in your
2145 client workstation local <guiicon>Printers and Faxes</guiicon> folder.
2149 You can also open your local <guiicon>Printers and Faxes</guiicon> folder by
2150 using this command on Windows 200x/XP Professional workstations:
2153 <para><userinput>rundll32 shell32.dll,SHHelpShortcuts_RunDLL PrintersFolder</userinput></para>
2156 or this command on Windows NT 4.0 workstations:
2160 rundll32 shell32.dll,Control_RunDLL MAIN.CPL @2
2164 You can enter the commands either inside a <guilabel>DOS box</guilabel> window or in the <guimenuitem>Run
2165 command...</guimenuitem> field from the <guimenu>Start</guimenu> menu.
2170 <title>Always Make First Client Connection as root or <quote>printer admin</quote></title>
2173 After you installed the driver on the Samba server (in its <smbconfsection>[print$]</smbconfsection>
2174 share, you should always make sure that your first client installation completes correctly. Make it a
2175 habit for yourself to build the very first connection from a client as <smbconfoption><name>printer admin</name></smbconfoption>. This is to make sure that:
2180 A first valid <emphasis>Device Mode</emphasis> is really initialized (see above for more
2181 explanation details).
2185 The default print settings of your printer for all further client installations are as you want them.
2190 Do this by changing the orientation to landscape, click on <guiicon>Apply</guiicon>, and then change it
2191 back again. Next, modify the other settings (for example, you do not want the default media size set to
2192 <guiicon>Letter</guiicon> when you are all using <guiicon>A4</guiicon>, right? You may want to set the
2193 printer for <guiicon>duplex</guiicon> as the default, and so on).
2197 To connect as root to a Samba printer, try this command from a Windows 200x/XP DOS box command prompt:
2201 &dosprompt;<userinput>runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /p /t3 /n
2202 \\<replaceable>SAMBA-SERVER</replaceable>\<replaceable>printername</replaceable>"</userinput>
2207 You will be prompted for root's Samba-password; type it, wait a few
2208 seconds, click on <guibutton>Printing
2209 Defaults</guibutton>, and proceed to set the job options that should be used as defaults by all
2210 clients. Alternately, instead of root you can name one other member of the <smbconfoption><name>printer admin</name></smbconfoption> from the setting.
2214 Now all the other users downloading and installing the driver the same way <?latex \linebreak ?>(called
2215 <quote>Point'n'Print</quote>) will have the same defaults set for them. If you miss this step
2216 you'll get a lot of Help Desk calls from your users, but maybe you like to talk to people.
2222 <title>Other Gotchas</title>
2225 Your driver is installed. It is now ready for Point'n'Print
2226 installation by the clients. You may have tried to download and use it
2227 onto your first client machine, but
2228 wait. Let's make sure you are acquainted first with a few tips and tricks you may find useful. For example,
2229 suppose you did not set the defaults on the printer, as advised in the preceding
2230 paragraphs. Your users complain about various issues (such as, <quote>We need to set the paper size
2231 for each job from Letter to A4 and it will not store it.</quote>)
2235 <title>Setting Default Print Options for Client Drivers</title>
2238 The last sentence might be viewed with mixed feelings by some users and
2239 Admins. They have struggled for hours and could not arrive at a point
2240 where their settings seemed to be saved. It is not their fault. The confusing
2241 thing is that in the multi-tabbed dialog that pops up when you right-click
2242 on the printer name and select <guimenuitem>Properties</guimenuitem>, you
2243 can arrive at two dialogs that appear identical, each claiming that they help
2244 you to set printer options in three different ways. Here is the definite
2245 answer to the Samba default driver setting FAQ:
2248 <formalpara><title><quote>I can not set and save default print options
2249 for all users on Windows 200x/XP. Why not?</quote></title>
2252 How are you doing it? I bet the wrong way. (It is not easy to find out, though). There are three different
2253 ways to bring you to a dialog that seems to set everything. All three
2254 dialogs look the same, but only one
2255 of them does what you intend. You need to be Administrator or Print Administrator to do this for all
2256 users. Here is how I reproduce it in an XP Professional:
2258 The following list needs periods after the letters and numbers:::::::::
2259 <orderedlist numeration="upperalpha">
2260 <listitem><para>The first <quote>wrong</quote> way:
2261 <orderedlist numeration="arabic">
2262 <listitem><para>Open the <guiicon>Printers</guiicon> folder.</para></listitem>
2264 <listitem><para>Right-click on the printer (<emphasis>remoteprinter on cupshost</emphasis>) and
2265 select in context menu <guimenu>Printing Preferences...</guimenu></para></listitem>.
2267 <listitem><para>Look at this dialog closely and remember what it looks like.</para></listitem>
2268 </orderedlist></para></listitem>
2270 <listitem><para>The second <quote>wrong</quote> way:
2271 <orderedlist numeration="arabic">
2272 <listitem><para>Open the <guimenu>Printers</guimenu> folder.</para></listitem>
2274 <listitem><para>Right-click on the printer (<emphasis>remoteprinter on
2275 cupshost</emphasis>) and select in the context menu
2276 <guimenuitem>Properties</guimenuitem></para></listitem>
2278 <listitem><para>Click on the <guilabel>General</guilabel>
2279 tab</para></listitem>.
2281 <listitem><para>Click on the <guibutton>Printing
2282 Preferences...</guibutton></para></listitem> button.
2284 <listitem><para>A new dialog opens. Keep this dialog open and go back
2285 to the parent dialog.</para></listitem>
2290 The third and correct way: (should you do this from the beginning, just carry out steps 1
2291 and 2 from the second method above).
2294 <orderedlist numeration="arabic">
2295 <listitem><para>Click on the <guilabel>Advanced</guilabel>
2296 tab. (If everything is <quote>grayed out,</quote> then you are not logged
2297 in as a user with enough privileges).</para></listitem>
2299 <listitem><para>Click on the <guibutton>Printing
2300 Defaults</guibutton> button.</para></listitem>
2302 <listitem><para>On any of the two new tabs,
2304 <guilabel>Advanced</guilabel> button.</para></listitem>
2306 <listitem><para>A new dialog opens. Compare
2307 this one to the other. Are they
2308 identical looking comparing one from
2309 <quote>B.5</quote> and one from A.3".</para></listitem>
2315 Do you see any difference in the two settings dialogs? I do not either. However, only the last one, which
2316 you arrived at with steps C.1 through 6 will permanently save any settings which will then become the defaults
2317 for new users. If you want all clients to have the same defaults, you need to conduct these steps as
2318 administrator (<smbconfoption><name>printer admin</name></smbconfoption> in ) before
2319 a client downloads the driver (the clients can later set their own per-user defaults
2320 by following procedures A or B above). Windows 200x/XP allow per-user default settings and the ones the
2321 administrator gives them, before they set up their own. The parents of the identically-looking dialogs have a slight difference in their window names; one is called <computeroutput>Default Print
2322 Values for Printer Foo on Server Bar"</computeroutput> (which is the one you need) and the other is called
2323 <quote><computeroutput>Print Settings for Printer Foo on Server Bar</computeroutput></quote>. The last one is the one you
2324 arrive at when you right-click on the printer and select <guimenuitem>Print Settings...</guimenuitem>. This
2325 is the one that you were taught to use back in the days of Windows NT, so it is only natural to try the
2326 same way with Windows 200x/XP. You would not dream that there is now a different path to arrive at an
2327 identically looking, but functionally different, dialog to set defaults for all users.
2328 </para></formalpara>
2330 <tip><para>Try (on Windows 200x/XP) to run this command (as a user with the right privileges):
2334 rundll32 printui.dll,PrintUIEntry /p /t3 /n\\<replaceable>SAMBA-SERVER</replaceable>\<replaceable>printersharename</replaceable>
2338 To see the tab with the <guilabel>Printing Defaults</guilabel> button (the one you need),also run this command:
2342 rundll32 printui.dll,PrintUIEntry /p /t0 /n\\<replaceable>SAMBA-SERVER</replaceable>\<replaceable>printersharename</replaceable>
2346 To see the tab with the <guilabel>Printing Preferences</guilabel>
2347 button (the one which does not set system-wide defaults), you can
2348 start the commands from inside a DOS box" or from <guimenu>Start</guimenu> -> <guimenuitem>Run</guimenuitem>.
2355 <title>Supporting Large Numbers of Printers</title>
2358 One issue that has arisen during the recent development phase of Samba is the need to support driver
2359 downloads for hundreds of printers. Using Windows NT APW here is somewhat awkward (to say the least). If
2360 you do not want to acquire RSS pains from the printer installation clicking orgy alone, you need
2361 to think about a non-interactive script.
2365 If more than one printer is using the same driver, the <command>rpcclient setdriver</command>
2366 command can be used to set the driver associated with an installed queue. If the driver is uploaded to
2367 <smbconfsection>[print$]</smbconfsection> once and registered with the printing TDBs, it can be used by
2368 multiple print queues. In this case, you just need to repeat the <command>setprinter</command> subcommand of
2369 <command>rpcclient</command> for every queue (without the need to conduct the <command>adddriver</command>
2370 repeatedly). The following is an example of how this could be accomplished:
2374 &rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'enumdrivers'</userinput>
2378 Printer Driver Info 1:
2379 Driver Name: [infotec IS 2075 PCL 6]
2381 Printer Driver Info 1:
2382 Driver Name: [DANKA InfoStream]
2384 Printer Driver Info 1:
2385 Driver Name: [Heidelberg Digimaster 9110 (PS)]
2387 Printer Driver Info 1:
2388 Driver Name: [dm9110]
2390 Printer Driver Info 1:
2391 Driver Name: [mydrivername]
2397 &rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'enumprinters'</userinput>
2400 name:[\\SAMBA-CUPS\dm9110]
2401 description:[\\SAMBA-CUPS\dm9110,,110ppm HiVolume DANKA Stuttgart]
2402 comment:[110 ppm HiVolume DANKA Stuttgart]
2407 &rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c \
2408 'setdriver <replaceable>dm9110</replaceable> "<replaceable>Heidelberg Digimaster 9110 (PS)</replaceable>"'</userinput>
2409 cmd = setdriver dm9110 Heidelberg Digimaster 9110 (PPD)
2410 Successfully set dm9110 to driver Heidelberg Digimaster 9110 (PS).
2414 &rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'enumprinters'</userinput>
2417 name:[\\SAMBA-CUPS\dm9110]
2418 description:[\\SAMBA-CUPS\dm9110,Heidelberg Digimaster 9110 (PS),\
2419 110ppm HiVolume DANKA Stuttgart]
2420 comment:[110ppm HiVolume DANKA Stuttgart]
2425 &rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'setdriver <replaceable>dm9110</replaceable> <replaceable>mydrivername</replaceable>'</userinput>
2426 cmd = setdriver dm9110 mydrivername
2427 Successfully set dm9110 to mydrivername.
2431 &rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'enumprinters'</userinput>
2434 name:[\\SAMBA-CUPS\dm9110]
2435 description:[\\SAMBA-CUPS\dm9110,mydrivername,\
2436 110ppm HiVolume DANKA Stuttgart]
2437 comment:[110ppm HiVolume DANKA Stuttgart]
2442 It may not be easy to recognize that the first call to <command>enumprinters</command> showed the
2443 <quote>dm9110</quote> printer with an empty string where the driver should have been listed (between
2444 the 2 commas in the description field). After the <command>setdriver</command> command
2445 succeeded, all is well.
2450 <title>Adding New Printers with the Windows NT APW</title>
2453 By default, Samba exhibits all printer shares defined in &smb.conf; in the <guiicon>Printers</guiicon>
2454 folder. Also located in this folder is the Windows NT Add Printer Wizard icon. The APW will be shown only if:
2459 The connected user is able to successfully execute an <command>OpenPrinterEx(\\server)</command> with
2460 administrative privileges (i.e., root or <smbconfoption><name>printer admin</name></smbconfoption>).
2463 <tip><para> Try this from a Windows 200x/XP DOS box command prompt:
2467 runas /netonly /user:root rundll32 printui.dll,PrintUIEntry /p /t0 /n \\<replaceable>SAMBA-SERVER</replaceable>\<replaceable>printersharename</replaceable>
2471 Click on <guibutton>Printing Preferences</guibutton>.
2472 </para></tip></listitem>
2474 <listitem><para>... contains the setting
2475 <smbconfoption><name>show add printer wizard</name><value>yes</value></smbconfoption> (the
2476 default).</para></listitem>
2480 The APW can do various things:
2485 Upload a new driver to the Samba <smbconfsection>[print$]</smbconfsection> share.
2489 Associate an uploaded driver with an existing (but still driverless) print queue.
2493 Exchange the currently used driver for an existing print queue with one that has been uploaded before.
2497 Add an entirely new printer to the Samba host (only in conjunction with a working
2498 <smbconfoption><name>add printer command</name></smbconfoption>. A corresponding
2499 <smbconfoption><name>delete printer command</name></smbconfoption> for removing entries from the
2500 <guiicon>Printers</guiicon> folder may also be provided).
2505 The last one (add a new printer) requires more effort than the previous ones. To use
2506 the APW to successfully add a printer to a Samba server, the <smbconfoption><name>add printer command</name></smbconfoption> must have a defined value. The program hook must successfully
2507 add the printer to the UNIX print system (i.e., to <filename>/etc/printcap</filename>,
2508 <filename>/etc/cups/printers.conf</filename> or other appropriate files) and to &smb.conf; if necessary.
2512 When using the APW from a client, if the named printer share does not exist, smbd will execute the
2513 <smbconfoption><name>add printer command</name></smbconfoption> and re-parse to the to attempt to locate the new printer
2514 share. If the share is still not defined, an error of <errorname>Access Denied</errorname> is returned to
2515 the client. The <smbconfoption><name>add printer command</name></smbconfoption> is executed
2516 under the context of the connected user, not necessarily a root account. A <smbconfoption><name>map to guest</name><value>bad user</value></smbconfoption> may have connected you unwittingly under the wrong
2517 privilege. You should check it by using the <command>smbstatus</command> command.
2523 <title>Error Message: <quote><errorname>Cannot connect under a different Name</errorname></quote></title>
2526 Once you are connected with the wrong credentials, there is no means to reverse the situation other than
2527 to close all Explorer Windows, and perhaps reboot.
2532 The <command>net use \\SAMBA-SERVER\sharename /user:root</command> gives you an error message:
2533 <quote>Multiple connections to a server or a shared resource by the same user utilizing
2534 the several user names are not allowed. Disconnect all previous connections to the server,
2535 esp. the shared resource, and try again.</quote>
2539 Every attempt to <quote>connect a network drive</quote> to <filename>\\SAMBASERVER\\print$</filename>
2540 to <constant>z:</constant> is countered by the pertinacious message: <quote>This
2541 network folder is currently connected under different credentials (username and password).
2542 Disconnect first any existing connection to this network share in order to connect again under
2543 a different username and password</quote>.
2548 So you close all connections. You try again. You get the same message. You check from the Samba side,
2549 using <command>smbstatus</command>. Yes, there are more connections. You kill them all. The client
2550 still gives you the same error message. You watch the smbd.log file on a high debug level and try
2551 reconnect. Same error message, but not a single line in the log. You start to wonder if there was a
2552 connection attempt at all. You run ethereal and tcpdump while you try to connect. Result: not a single
2553 byte goes on the wire. Windows still gives the error message. You close all Explorer windows and start it
2554 again. You try to connect &smbmdash; and this times it works! Windows seems to cache connection information somewhere and
2555 does not keep it up-to-date (if you are unlucky you might need to reboot to get rid of the error message).
2559 The easiest way to forcefully terminate all connections from your client to a server is by executing:
2561 &dosprompt; net use * /delete
2563 This will disconnect all mapped drives also and will allow you create fresh connection as required.
2568 <title>Take Care When Assembling Driver Files</title>
2571 You need to be extremely careful when you take notes about the files and belonging to a particular
2572 driver. Don't confuse the files for driver version <quote>0</quote> (for Windows 9x/Me, going into
2573 <filename>[print$]/WIN/0/</filename>), driver version <filename>2</filename> (Kernel Mode driver for Windows NT,
2574 going into <filename>[print$]/W32X86/2/</filename> may be used on Windows 200x/XP also), and
2575 driver version <quote>3</quote> (non-Kernel Mode driver going into <filename>[print$]/W32X86/3/</filename>
2576 cannot be used on Windows NT). Quite often these different driver versions contain
2577 files that have the same name but actually are very different. If you look at them from
2578 the Windows Explorer (they reside in <filename>%WINDOWS%\system32\spool\drivers\W32X86\</filename>),
2579 you will probably see names in capital letters, while an <command>enumdrivers</command> command from Samba
2580 would show mixed or lower case letters. So it is easy to confuse them. If you install them manually using
2581 <command>rpcclient</command> and subcommands, you may even succeed without an error message. Only later,
2582 when you try install on a client, you will encounter error messages like <computeroutput>This server
2583 has no appropriate driver for the printer</computeroutput>.
2587 Here is an example. You are invited to look closely at the various files, compare their names and
2588 their spelling, and discover the differences in the composition of the version 2 and 3 sets. Note: the
2589 version 0 set contained 40 <parameter>Dependentfiles</parameter>, so I left it out for space reasons:
2593 &rootprompt;<userinput>rpcclient -U 'Administrator%<replaceable>secret</replaceable>' -c 'enumdrivers 3' 10.160.50.8 </userinput>
2595 Printer Driver Info 3:
2597 Driver Name: [Canon iR8500 PS3]
2598 Architecture: [Windows NT x86]
2599 Driver Path: [\\10.160.50.8\print$\W32X86\3\cns3g.dll]
2600 Datafile: [\\10.160.50.8\print$\W32X86\3\iR8500sg.xpd]
2601 Configfile: [\\10.160.50.8\print$\W32X86\3\cns3gui.dll]
2602 Helpfile: [\\10.160.50.8\print$\W32X86\3\cns3g.hlp]
2604 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aucplmNT.dll]
2605 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\ucs32p.dll]
2606 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\tnl32.dll]
2607 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aussdrv.dll]
2608 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cnspdc.dll]
2609 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aussapi.dat]
2610 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cns3407.dll]
2611 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\CnS3G.cnt]
2612 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\NBAPI.DLL]
2613 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\NBIPC.DLL]
2614 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcview.exe]
2615 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcdspl.exe]
2616 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcedit.dll]
2617 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcqm.exe]
2618 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcspl.dll]
2619 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cfine32.dll]
2620 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcr407.dll]
2621 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\Cpcqm407.hlp]
2622 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcqm407.cnt]
2623 Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cns3ggr.dll]
2628 Printer Driver Info 3:
2630 Driver Name: [Canon iR5000-6000 PS3]
2631 Architecture: [Windows NT x86]
2632 Driver Path: [\\10.160.50.8\print$\W32X86\2\cns3g.dll]
2633 Datafile: [\\10.160.50.8\print$\W32X86\2\IR5000sg.xpd]
2634 Configfile: [\\10.160.50.8\print$\W32X86\2\cns3gui.dll]
2635 Helpfile: [\\10.160.50.8\print$\W32X86\2\cns3g.hlp]
2637 Dependentfiles: [\\10.160.50.8\print$\W32X86\2\AUCPLMNT.DLL]
2638 Dependentfiles: [\\10.160.50.8\print$\W32X86\2\aussdrv.dll]
2639 Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cnspdc.dll]
2640 Dependentfiles: [\\10.160.50.8\print$\W32X86\2\aussapi.dat]
2641 Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cns3407.dll]
2642 Dependentfiles: [\\10.160.50.8\print$\W32X86\2\CnS3G.cnt]
2643 Dependentfiles: [\\10.160.50.8\print$\W32X86\2\NBAPI.DLL]
2644 Dependentfiles: [\\10.160.50.8\print$\W32X86\2\NBIPC.DLL]
2645 Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cns3gum.dll]
2647 Monitorname: [CPCA Language Monitor2]
2653 If we write the <quote>version 2</quote> files and the <quote>version 3</quote> files
2654 into different text files and compare the result, we see this
2659 &rootprompt;<userinput>sdiff 2-files 3-files</userinput>
2663 iR8500sg.xpd iR8500sg.xpd
2664 cns3gui.dll cns3gui.dll
2666 AUCPLMNT.DLL | aucplmNT.dll
2669 aussdrv.dll aussdrv.dll
2670 cnspdc.dll cnspdc.dll
2671 aussapi.dat aussapi.dat
2672 cns3407.dll cns3407.dll
2676 cns3gum.dll | cpcview.exe
2688 Do not be fooled! Driver files for each version with identical
2689 names may be different in their content, as you can see from this size
2694 &rootprompt;<userinput>for i in cns3g.hlp cns3gui.dll cns3g.dll; do \
2695 smbclient //10.160.50.8/print\$ -U 'Administrator%xxxx' \
2696 -c "cd W32X86/3; dir $i; cd .. ; cd 2; dir $i"; \
2699 CNS3G.HLP A 122981 Thu May 30 02:31:00 2002
2700 CNS3G.HLP A 99948 Thu May 30 02:31:00 2002
2702 CNS3GUI.DLL A 1805824 Thu May 30 02:31:00 2002
2703 CNS3GUI.DLL A 1785344 Thu May 30 02:31:00 2002
2705 CNS3G.DLL A 1145088 Thu May 30 02:31:00 2002
2706 CNS3G.DLL A 15872 Thu May 30 02:31:00 2002
2710 In my example were even more differences than shown here. Conclusion: you must be careful to select
2711 the correct driver files for each driver version. Don't rely on the
2712 names alone and don't interchange files
2713 belonging to different driver versions.
2718 <title>Samba and Printer Ports</title>
2721 Windows NT/2000 print servers associate a port with each printer. These normally take the form of
2722 <filename>LPT1:</filename>, <filename>COM1:</filename>,
2723 <filename>FILE:</filename>, and so on. Samba must also
2724 support the concept of ports associated with a printer. By default, only one printer port, named <quote>Samba
2725 Printer Port</quote>, exists on a system. Samba does not really need such a <quote>port</quote> in order
2726 to print; rather it is a requirement of Windows clients. They insist on being told about an available
2727 port when they request this information, otherwise they throw an error message at you. So Samba fakes the port
2728 information to keep the Windows clients happy.
2732 Samba does not support the concept of <constant>Printer Pooling</constant> internally either. Printer
2733 Pooling assigns a logical printer to multiple ports as a form of load balancing or fail over.
2737 If you require multiple ports be defined for some reason or another (my users and my boss should not know
2738 that they are working with Samba), configure <smbconfoption><name>enumports command</name></smbconfoption>
2739 which can be used to define an external program that generates a listing of ports on a system.
2744 <title>Avoiding Common Client Driver Mis-configuration</title>
2747 So now the printing works, but there are still problems. Most jobs print well, some do not print at
2748 all. Some jobs have problems with fonts, which do not look good. Some jobs print fast and some
2749 are dead-slow. We cannot cover it all, but we want to encourage you to read the brief paragraph about
2750 <quote>Avoiding the Wrong PostScript Driver Settings</quote> in the CUPS Printing part of this document.
2756 <title>The Imprints Tool-set</title>
2759 The Imprints tool set provides a UNIX equivalent of the Windows NT Add Printer
2760 Wizard. For complete information, please refer to the
2761 <ulink url="http://imprints.sourceforge.net/">Imprints</ulink> Web site as well as the documentation
2762 included with the imprints source distribution. This section only provides a brief introduction to
2763 the features of Imprints.
2767 Unfortunately, the Imprints tool-set is no longer maintained. As of December 2000, the project is in
2768 need of a new maintainer. The most important skill to have is Perl coding and an interest in MS-RPC-based
2769 printing used in Samba. If you wish to volunteer, please coordinate
2770 your efforts on the Samba technical
2771 mailing list. The tool-set is still in usable form, but only for a series of older printer models where
2772 there are prepared packages to use. Packages for more up-to-date print devices are needed if Imprints
2773 should have a future.
2777 <title>What is Imprints?</title>
2780 Imprints is a collection of tools for supporting these goals:
2785 Providing a central repository of information regarding Windows NT and 95/98 printer driver packages.
2789 Providing the tools necessary for creating the Imprints printer driver packages.
2793 Providing an installation client that will obtain printer drivers from a central Internet (or intranet) Imprints Server
2794 repository and install them on remote Samba and Windows NT4 print servers.
2800 <title>Creating Printer Driver Packages</title>
2803 The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt
2804 also included with the Samba distribution for more information). In short, an Imprints driver package
2805 is a gzipped tarball containing the driver files, related INF files, and a control file needed by the
2806 installation client.
2811 <title>The Imprints Server</title>
2814 The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each
2815 printer entry in the database has an associated URL for the actual downloading of the package. Each
2816 package is digitally signed via GnuPG which can be used to verify that
2817 the package downloaded is actually
2818 the one referred in the Imprints database. It is strongly recommended that this security check
2824 <title>The Installation Client</title>
2827 More information regarding the Imprints installation client is available from the the documentation file
2828 <filename>Imprints-Client-HOWTO.ps</filename> that is included with the Imprints source package. The Imprints
2829 installation client comes in two forms:
2833 <listitem><para>A set of command line Perl scripts.</para></listitem>
2834 <listitem><para>A GTK+ based graphical interface to the command line Perl scripts.</para></listitem>
2838 The installation client (in both forms) provides a means of querying the Imprints database server for
2839 a matching list of known printer model names as well as a means to download and install the drivers on
2840 remote Samba and Windows NT print servers.
2844 The basic installation process is in four steps and Perl code is wrapped around smbclient and rpcclient.
2849 For each supported architecture for a given driver:
2851 <listitem><para>rpcclient: Get the appropriate upload directory on the remote server.</para></listitem>
2852 <listitem><para>smbclient: Upload the driver files.</para></listitem>
2853 <listitem><para>rpcclient: Issues an AddPrinterDriver() MS-RPC.</para></listitem>
2857 <listitem><para>rpcclient: Issue an AddPrinterEx() MS-RPC to actually create the printer.</para></listitem>
2861 One of the problems encountered when implementing the Imprints tool set was the name space issues between
2862 various supported client architectures. For example, Windows NT includes a driver named <quote>Apple LaserWriter
2863 II NTX v51.8</quote> and Windows 95 calls its version of this driver <quote>Apple LaserWriter II NTX</quote>.
2867 The problem is how to know what client drivers have been uploaded for a printer. An astute reader will
2868 remember that the Windows NT Printer Properties dialog only includes space for one printer driver name. A
2869 quick look in the Windows NT 4.0 system registry at:
2873 HKLM\System\CurrentControlSet\Control\Print\Environment
2877 will reveal that Windows NT always uses the NT driver name. This is okay as Windows NT always requires
2878 that at least the Windows NT version of the printer driver is present. Samba does not have the
2879 requirement internally, therefore, <quote>How can you use the NT driver name if it has not already been installed?</quote>
2883 The way of sidestepping this limitation is to require that all Imprints printer driver packages include both the Intel Windows NT and
2884 95/98 printer drivers and that the NT driver is installed first.
2890 <title>Adding Network Printers without User Interaction</title>
2893 The following MS Knowledge Base article may be of some help if you need to handle Windows 2000
2894 clients: <emphasis>How to Add Printers with No User Interaction in Windows 2000,</emphasis> (<ulink
2895 url="http://support.microsoft.com/default.aspx?scid=kb;en-us;189105">http://support.microsoft.com/default.aspx?scid=kb;en-us;189105</ulink>).
2896 It also applies to Windows XP Professional clients.
2897 The ideas sketched out in this section are inspired by this article, which describes a command-line method that can be
2898 applied to install network and local printers and their drivers. This is most useful if integrated in Logon
2899 Scripts. You can see what options are available by typing in the command prompt (<command>DOS box</command>):
2902 <para><userinput>rundll32 printui.dll,PrintUIEntry /?</userinput></para>
2905 A window pops up that shows you all of the command-line switches available. An extensive list of examples
2906 is also provided. This is only for Win 200x/XP, it does not work on
2907 Windows NT. Windows NT probably has
2908 some other tools in the respective Resource Kit. Here is a suggestion about what a client logon script
2909 might contain, with a short explanation of what the lines actually do (it works if 200x/XP Windows
2910 clients access printers via Samba, and works for Windows-based print servers too):
2914 <userinput>rundll32 printui.dll,PrintUIEntry /dn /n "\\cupsserver\infotec2105-IPDS" /q</userinput>
2915 <userinput>rundll32 printui.dll,PrintUIEntry /in /n "\\cupsserver\infotec2105-PS"</userinput>
2916 <userinput>rundll32 printui.dll,PrintUIEntry /y /n "\\cupsserver\infotec2105-PS"</userinput>
2920 Here is a list of the used command-line parameters:
2924 <varlistentry><term>/dn</term>
2925 <listitem><para>deletes a network printer</para></listitem>
2927 <varlistentry><term>/q</term>
2928 <listitem><para>quiet modus</para></listitem>
2930 <varlistentry><term>/n</term>
2931 <listitem><para>names a printer</para></listitem>
2933 <varlistentry><term>/in</term>
2934 <listitem><para>adds a network printer connection</para></listitem>
2936 <varlistentry><term>/y</term>
2937 <listitem><para>sets printer as default printer</para></listitem>
2943 Line 1 deletes a possibly existing previous network printer <emphasis>infotec2105-IPDS</emphasis>
2944 (which had used native Windows drivers with LPRng that were removed from the server that was
2945 converted to CUPS). The <command>/q</command> at the end eliminates Confirm
2946 or error dialog boxes from popping up. They should not be presented to the user logging on.
2950 Line 2 adds the new printer
2951 <emphasis>infotec2105-PS</emphasis> (which actually is the same
2952 physical device but is now run by the new CUPS printing system and associated with the
2953 CUPS/Adobe PS drivers). The printer and its driver must have been added to Samba prior to
2954 the user logging in (e.g., by a procedure as discussed earlier in this chapter, or by running
2955 <command>cupsaddsmb</command>). The driver is now auto-downloaded to the client PC where the
2956 user is about to log in.
2960 Line 3 sets the default printer to this new network printer (there might be several other
2961 printers installed with this same method and some may be local as well, so we decide for a
2962 default printer). The default printer selection may, of course, be different for different users.
2967 The second line only works if the printer <emphasis>infotec2105-PS</emphasis> has an already working
2968 print queue on the <constant>cupsserver</constant>, and if the
2969 printer drivers have been successfully uploaded
2970 (via the <command>APW</command>, <command>smbclient/rpcclient</command>, or <command>cupsaddsmb</command>)
2971 into the <smbconfsection>[print$]</smbconfsection> driver repository of Samba. Some Samba versions
2972 prior to version 3.0 required a re-start of smbd after the printer install and the driver upload,
2973 otherwise the script (or any other client driver download) would fail.
2977 Since there no easy way to test for the existence of an installed network printer from the logon script,
2978 do not bother checking, just allow the de-installation/re-installation to occur every time a user logs in;
2979 it's really quick anyway (1 to 2 seconds).
2983 The additional benefits for this are:
2988 It puts in place any printer default setup changes automatically at every user logon.
2992 It allows for <quote>roaming</quote> users' login into the domain from different workstations.
2997 Since network printers are installed per user, this much simplifies the process of keeping the installation
2998 up-to-date. The few extra seconds at logon time will not really be noticeable. Printers can be centrally
2999 added, changed and deleted at will on the server with no user intervention required from the clients
3000 (you just need to keep the logon scripts up-to-date).
3005 <title>The <command>addprinter</command> Command</title>
3008 The <command>addprinter</command> command can be configured to be a shell script or program executed by
3009 Samba. It is triggered by running the APW from a client against the Samba print server. The APW asks
3010 the user to fill in several fields (such as printer name, driver to be used, comment, port monitor,
3011 and so on). These parameters are passed on to Samba by the APW. If the addprinter command is designed in a
3012 way that it can create a new printer (through writing correct printcap entries on legacy systems, or
3013 execute the <command>lpadmin</command> command on more modern systems) and create the associated share
3014 in, then the APW will in effect really create a new printer on Samba and the UNIX print subsystem!
3019 <title>Migration of Classical Printing to Samba</title>
3022 The basic NT-style printer driver management has not changed considerably in 3.0 over the 2.2.x releases
3023 (apart from many small improvements). Here migration should be quite easy, especially if you followed
3024 previous advice to stop using deprecated parameters in your setup. For migrations from an existing 2.0.x
3025 setup, or if you continued Windows 9x/Me-style printing in your Samba 2.2 installations, it is more of
3026 an effort. Please read the appropriate release notes and the HOWTO Collection for Samba-2.2.x. You can
3027 follow several paths. Here are possible scenarios for migration:
3032 You need to study and apply the new Windows NT printer and driver support. Previously used
3033 parameters <parameter>printer driver file</parameter>, <parameter>printer driver</parameter>
3034 and <parameter>printer driver location</parameter> are no longer supported.
3038 If you want to take advantage of Windows NT printer driver support, you also need to migrate the
3039 Windows 9x/Me drivers to the new setup.
3043 An existing <filename>printers.def</filename> file (the one specified in the now removed parameter
3044 <parameter>printer driver file</parameter>) will no longer work with Samba-3. In 3.0, smbd attempts
3045 to locate a Windows 9x/Me driver files for the printer in <smbconfsection>[print$]</smbconfsection>
3046 and additional settings in the TDB and only there; if it fails, it will <emphasis>not</emphasis>
3047 (as 2.2.x used to do) drop down to using a <filename>printers.def</filename> (and all associated
3048 parameters). The make_printerdef tool is removed and there is no backward compatibility for this.
3051 <listitem><para>You need to install a Windows 9x/Me driver into the
3052 <smbconfsection>[print$]</smbconfsection> share for a printer on your Samba
3053 host. The driver files will be stored in the <quote>WIN40/0</quote> subdirectory of
3054 <smbconfsection>[print$]</smbconfsection>, and some other settings and information go
3055 into the printing-related TDBs.</para></listitem>
3057 <listitem><para>If you want to migrate an existing
3058 <filename>printers.def</filename> file into the new setup, the
3060 solution is to use the Windows NT APW to install the NT drivers
3061 and the 9x/Me drivers. This can be scripted using smbclient and
3062 rpcclient. See the Imprints installation client at:
3066 <ulink noescape="1" url="http://imprints.sourceforge.net/">http://imprints.sourceforge.net/</ulink>
3070 for an example. See also the discussion of rpcclient usage in the
3071 <quote>CUPS Printing</quote> section.</para></listitem>
3076 <title>Publishing Printer Information in Active Directory or LDAP</title>
3079 This will be addressed in a later update of this document. If you wish to volunteer your services to help
3080 document this, please contact <ulink url="mail://jht@samba.org">John H Terpstra.</ulink>
3085 <title>Common Errors</title>
3088 <title>I Give My Root Password but I Do Not Get Access</title>
3091 Do not confuse the root password which is valid for the UNIX system (and in most cases stored in the
3092 form of a one-way hash in a file named <filename>/etc/shadow</filename>), with the password used to
3093 authenticate against Samba. Samba does not know the UNIX password. Root access to Samba resources
3094 requires that a Samba account for root must first be created. This is done with the <command>smbpasswd</command>
3099 &rootprompt; smbpasswd -a root
3100 New SMB password: secret
3101 Retype new SMB password: secret
3107 <title>My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</title>
3110 Do not use the existing UNIX print system spool directory for the Samba spool directory. It may seem
3111 convenient and a savings of space, but it only leads to problems. The two must be separate.