[Chapter 7] 7.2 Printing to Windows Client Printers
Date: 1999-11-05T21:34:58Z

| ## Using Samba Robert Eckstein, David Collier-Brown, Peter Kelly 1st Edition November 1999 1-56592-449-5, Order Number: 4495 416 pages, $34.95 Buy the hardcopy Table of Contents

| Chapter 7 Printing and Name Resolution |

> ## 7.2 Printing to Windows Client Printers

> If you have printers connected to clients running Windows 95/98 or NT 4.0, those printers can also be accessed from Samba. Samba comes equipped with a tool called smbprint that can be used to spool print jobs to Windows-based printers. In order to use this, however, you need to set up the printer as a shared resource on the client machine. If you haven't already done this, you can reset this from the Printers window, reached from the Start button, as shown in Figure 7.7.

> #### Figure 7.7: The Printers window

> Select a printer that's locally connected (for example, ours is the Canon printer), press the right mouse button to bring up a menu, and select Sharing. This will give you the Sharing tab of the Printer Properties frame, as shown in Figure 7.8. If you want it available to everybody on your LAN as the Windows guest user, enter a blank password.

> #### Figure 7.8: The Sharing tab of the printer

> Once you've got this working, you can add your printer to the list of standard printers and Samba can make it available to all the other PCs in the workgroup. To make installation on Unix easier, the Samba distribution provides two sample scripts: smbprint and smbprint.sysv. The first works with BSD-style printers; the second is designed for System V printers.

> ### 7.2.1 BSD printers

> There are two steps you need to have a BSD Unix recognize a remote printer:

> 1. Place an entry for the printer in the /etc/printcap file (or equivalent).

> 2. Place a configuration file in the /var/spool directory for the printer.

> First, edit your /etc/printcap file and add an entry for the remote printer. Note that the input filter (`if`) entry needs to point to the smbprint program if the machine is on Windows 95/98. The following set of lines will accomplish on a Linux machine, for example:

>     laserjet:\
>       :sd=/var/spool/lpd/laser:\

>     # spool directory
>       :mx#0:\

>     # maximum file size (none)
>       :sh:\

>     # surpress burst header (no)
>       :if=/usr/local/samba/bin/smbprint:

>     # text filter

> After that, you need to create a configuration file in the spool directory that you specified with the `sd` parameter above. (You may need to create that directory.) The file must have the name .config and should contain the following information:

> - The NetBIOS name of the Windows machine with the printer

> - The service name that represents the printer

> - The password used to access that service

> The last two parameters were set up in the Sharing dialog for the requested resource on the Windows machine. In this case, the .config file would have three lines:

>     server = phoenix
>     service = CANON
>     password = ""

> After you've done that, reset the Samba server machine and try printing to it using any standard Unix program.

> ### 7.2.2 System V printers

> Sending print jobs from a System V Unix system is a little easier. Here, you need to get obtain the smbprint.sysv script in the /usr/local/samba/examples/printing directory and do the following:

> 1. Change the `server`, `service`, and `password` parameters in the script to match the NetBIOS machine, its shared printer service, and its password, respectively. For example, the following entries would be correct for the service in the previous example:

>     server = phoenix
>     service = CANON
>     password = ""

> 2. Run the following commands, which create a reference for the printer in the printer capabilities file. Note that the new Unix printer entry `canon_printer` is named:

>     # lpadmin -p canon_printer -v /dev/null -i ./smbprint.sysv
>     # enable canon_printer
>     # accept canon_printer

> After you've done that, restart the Samba daemons and try printing to it using any standard Unix program. You should now be able to send data to a printer on a Windows client across the network.

> ### 7.2.3 Samba Printing Options

> Table 7.2 summarizes the Samba printing options.

> Table 7.2: Printing Configuration Options
> Option | Parameters | Function | Default | Scope
> --- | --- | --- | --- | ---
> `printing` | `bsd`, `sysv`, `hpux`, `aix`, `qnx`, `plp`, `softq`, or `lprng` | Sets the print system type for your Unix system. | System dependent | Share
> `printable (print ok)` | boolean | Marks a share as a printing share. | `no` | Share
> `printer (printer name)` | string (Unix printer name) | Sets the name of the printer to be shown to clients. | System dependent | Share
> `printer driver` | string (printer driver name) | Sets the driver name that should be used by the client to send data to the printer. | None | Share
> `printer driver file` | string (fully-qualified pathname) | Sets the name of the printer driver file. | None | Global
> `printer driver location` | string (network pathname) | Specifies the pathname of the share for the printer driver file. | None | Share
> `lpq cache time` | numeric (time in seconds) | Sets the amount of time in seconds that Samba will cache the lpq status. | `10` | Global
> `postscript` | boolean | Treats all print jobs sent as postscript by prepending `%!` at the beginning of each file. | `no` | Share
> `load printers` | boolean | Automatically loads each of the printers in the printcap file as printing shares. | `no` | Global
> `print command` | string (shell command) | Sets the Unix command to perform printing. | See below | Share
> `lpq command` | string (shell command) | Sets the Unix command to return the status of the printing queue. | See below | Share
> `lprm command` | string (shell command) | Sets the Unix command to remove a job from the printing queue. | See below | Share
> `lppause command` | string (shell command) | Sets the Unix command to pause a job on the printing queue. | See below | Share
> `lpresume command` | string (shell command) | Sets the Unix command to resume a paused job on the printing queue. | See below | Share
> `printcap name` `(printcap)` | string (fully-qualified pathname) | Specifies the location of the printer capabilities file. | System dependent | Global
> `min print space` | numeric (size in kilobytes) | Sets the minimum amount of disk free space that must be present to print. | `0` | Share
> `queuepause command` | string (shell command) | Sets the Unix command to pause a queue. | See below | Share
> `queueresume command` | string (shell command) | Sets the Unix command to resume a queue. | See below | Share

> #### 7.2.3.1 printing

> The `printing` configuration option tells Samba a little about your Unix printing system, in this case which printing parser to use. With Unix, there are several different families of commands to control printing and print statusing. Samba supports seven different types, as shown in Table 7.3.

> Table 7.3: Printing Types
> Variable | Definition
> --- | ---
> BSD | Berkeley Unix system
> SYSV | System V
> AIX | AIX Operating System (IBM)
> HPUX | Hewlett-Packard Unix
> QNX | QNX Realtime Operating System (QNX)
> LPRNG | LPR Next Generation (Powell)
> SOFTQ | SOFTQ system
> PLP | Portable Line Printer (Powell)

> The value for this optio.n will be one of these seven options. For example:

>     printing = SYSV

> The default value of this option is system dependent and is configured when Samba is first compiled. For most systems, the configure script will automatically detect the printing system to be used and configure it properly in the Samba makefile. However, if your system is a PLP, LPRNG, or QNX printing system, you will need to explicitly specify this in the makefile or the printing share.

> The most common system types are BSD and SYSV. Each of the printers on a BSD Unix server are described in the printer capabilities file - normally /etc/printcap.

> Setting the `printing` configuration option automatically sets at least three other printing options for the service in question: `print` `command`, `lpq` `command`, and `lprm` `command`. If you are running Samba on a system that doesn't support any of these printing styles, simply set the commands for each of these manually.

> #### 7.2.3.2 printable

> The printable option must be set to `yes` in order to flag a share as a printing service. If this option is not set, the share will be treated as a disk share instead. You can set the option as follows:

>     [printer1]
>     	printable = yes

> #### 7.2.3.3 printer

> The option, sometimes called `printer` `name`, specifies the name of the printer on the server to which the share points. This option has no default and should be set explicitly in the configuration file, even though Unix systems themselves often recognize a default name such as `lp` for a printer. For example:

>     [deskjet]
>     	printer = hpdkjet1

> #### 7.2.3.4 printer driver

> The `printer` `driver` option sets the string that Samba uses to tell Windows what the printer is. If this option is set correctly, the Windows Printer Wizard will already know what the printer is, making installation easier for end users by giving them one less dialog to worry about. The string given should match the string that shows up in the Printer Wizard, as shown in Figure 7.9. For example, an Apple LaserWriter typically uses `Apple` `LaserWriter`; a Hewlett Packard Deskjet 560C uses `HP` `DeskJet` `560C` `Printer`.

> #### Figure 7.9: The Add Printer Wizard dialog box in Windows 98

> Automatically configuring printer drivers with Samba is explained in greater detail in the section Section 7.1.7, Automatically Setting Up Printer Drivers, earlier in this chapter.

> #### 7.2.3.5 printer driver file

> This global option gives the location of the Windows 95/98 printer driver definition file, which is needed to give printer drivers to clients using a Samba printer. The default value of this option is /usr/local/samba/lib/printers.def. You can override this default as shown below:

>     [deskjet]
>     	printer driver file = /var/printers/printers.def

> This option is explained in greater detail in the section Section 7.1.7, earlier in this chapter.

> #### 7.2.3.6 printer driver location

> This option specifies a specific share that contains Windows 95 and 98 printer driver and definition files. There is no default parameter for this value. You can specify the location as a network pathname. A frequent approach is to use a share on your own machine, as shown here:

>     [deskjet]
>     	printer driver location = \\%L\PRINTER$

> This option is also explained in greater detail in the section Section 7.1.7, earlier in this chapter.

> #### 7.2.3.7 lpq cache time

> The global `lpq` `cache` `time` option allows you to set the number of seconds that Samba will remember the current printer status. After this time elapses, Samba will issue an lpq command (or whatever command you specify with the `lpq` `command` option) to get a more up-to-date status. This defaults to 10 seconds, but can be increased if your `lpq` `command` takes an unusually long time to run or you have lots of clients. The following example resets the time to 30 seconds:

>     [deskjet]
>     	lpq cache time = 30

> #### 7.2.3.8 postscript

> The `postscript` option forces the printer to treat all data sent to it as Postscript. It does this by prepending the characters `%!` at the beginning of the first line of each job. It is normally used with PCs that insert a `^D` (control-D or end-of-file mark) in front of the first line of a PostScript file. It will not, obviously, turn a non-PostScript printer into a PostScript one. The default value of this options is `no`. You can override it as follows:

>     [deskjet]
>     	postscript = yes

> #### 7.2.3.9 print command, lpq command, lprm command, lppause command, lpresume command

> These options tell Samba which Unix commands used to control and send data to the printer. The Unix commands involved are: lpr (send to Line PRinter), lpq (List Printer Queue), lprm (Line printer ReMove), and optionally lppause and lpresume. Samba provides an option named after each of these commands, in case you need to override any of the system defaults. For example, consider:

>     lpq command = /usr/ucb/lpq %p

> This would set the `lpq command` to use /usr/ucb/lpq. Similarly:

>     lprm command = /usr/local/lprm -P%p %j

> would set the Samba printer remove command to /usr/local/lprm, and provide it the print job number using the `%j` variable.

> The default values for each of these options are dependent on the value of the `printing` option. Table 7.4 shows the default commands for each of the printing options. The most popular printing system is BSD.

> Table 7.4: Default Commands for Various Printing Commands
> Option | BSD, AIX, PLP, LPRNG | SYSV, HPUX | QNX | SOFTQ
> --- | --- | --- | --- | ---
> `print command` | `lpr -r -P%p %s` | `lp -c -d%p %s; rm %s` | `lp -r -P%p %s` | `lp -d%p -s %s; rm %s`
> `lpq command` | `lpq -P%p` | `lpstat -o%p` | `lpq -P%p` | `lpstat -o%p`
> `lprm command` | `lprm -P%p %j` | `cancel %p-%j` | `cancel %p-%j` | `cancel %p-%j`
> `lppause command` | `lp -i %p-%j -H hold` (SYSV only) | None | None | None
> `lpresume command` | `lp -i %p-%j -H resume`(SYSV only) | None | None | `qstat -s -j%j -r`

> It is typically not necessary to reset these options in Samba, with the possible exception of `print` `command`. This option may need to be explicitly set if your printing system doesn't have a `-r` (remove after printing) option on the printing command. For example:

>     /usr/local/lpr -P%p %s; /bin/rm %s

> With a bit of judicious programming, these smb.conf options can also used for debugging:

>     print command = cat %s >>/tmp/printlog; lpr -r -P%p %s

> For example, this configuration can verify that files are actually being delivered to the Samba server. If they are, their contents will show up in the /tmp/printlog file.

> After BSD, the next most popular kind of printing system is SYSV (or System V) printing, plus some SYSV variants for IBM's AIX and Hewlett-Packard's HP-UX. These system do not have an /etc/printcap file. Instead, the `printcap` `file` option can be set to an appropriate lpstat command for the system. This tells Samba to get a list of printers from the lpstat command. Alternatively, you can set the global configuration option `printcap` `name` to the name of a dummy printcap file you provide. In the latter case, the file must contain a series of lines such as:

>     lp|print1|My Printer 1
>     print2|My Printer 2
>     print3|My Printer 3

> Each line names a printer, and provides aliases for it. In this example, the first printer is called `lp`, `print1`, or `My` `Printer` `1`, whichever the user prefers to use. The first name will be used in place of `%p` in any command Samba executes for that printer.

> Two additional printer types are also supported by Samba: LPRNG (LPR New Generation) and PLP (Public Line Printer). These are public domain and Open Source printing systems, and are used by many sites to overcome problems with vendor-supplied software. In addition, the SOFTQ and QNX realtime operating systems are supported by Samba.

> #### 7.2.3.10 load printers

> The `load` `printers` option tells Samba to create shares for all known printer names and load those shares into the browse list. Samba will create and list a printer share for each printer name in /etc/printcap (or system equivalent). For example, if your printcap file looks like this:[2]

> > [2] We have placed annotated comments off to the side in case you've never dealt with this file before.

>     lp:\
>       :sd=/var/spool/lpd/lp:\

>     # spool directory
>       :mx#0:\

>     # maximum file size (none)
>       :sh:\

>     # surpress burst header (no)
>       :lp=/dev/lp1:\

>     # device name for output
>       :if=/var/spool/lpd/lp/filter:

>     # text filter

>     laser:\
>       :sd=/var/spool/lpd/laser:\

>     # spool directory
>       :mx#0:\

>     # maximum file size (none)
>       :sh:\

>     # surpress burst header (no)
>       :lp=/dev/laser:\

>     # device name for output
>       :if=/var/spool/lpd/lp/filter:

>     # text filter

> and you specify:

>     load printers = yes

> the shares `[lp]` and `[laser]` will automatically be created as valid print shares when Samba is started. Both shares will borrow the configuration options specified in the `[printers]` section to configure themselves, and will be available in the browse list for the Samba server.

> #### 7.2.3.11 printcap name

> If the `printcap` `name` option (also called `printcap`) appears in a printing share, Samba will use the file specified as the system printer capabilities file. This is normally /etc/printcap. However, you can reset it to a file consisting of only the printers you want to share over the network. The value must be a fully-qualified filename of a printer capabilities file on the server:

>     [deskjet]
>     	printcap name = /usr/local/printcap

> #### 7.2.3.12 min print space

> The `min` `print` `space` option sets the amount of spool space that must be available on the disk before printing is allowed. Setting it to zero (the default) turns the check off; setting it to any other number sets the amount of free space in kilobytes required. This option helps avoid having print jobs fill up the remaining disk space on the server, which may cause other processes to fail:

>     [deskjet]
>     	min print space = 4000

> #### 7.2.3.13 queuepause command

> This configuration option specifies a command that tells Samba how to pause a print queue entirely, as opposed to a single job on the queue. The default value depends on the printing type chosen. You should not need to alter this option.

> #### 7.2.3.14 queueresume command

> This configuration option specifies a command that tells Samba how to resume a paused print queue, as opposed to resuming a single job on the print queue. The default value depends on the printing type chosen. You should not need to alter this option.

7.1 Sending Print Jobs to Samba |  | 7.3 Name Resolution with Samba

O'Reilly Home | O'Reilly Bookstores | How to Order | O'Reilly Contacts
International | About O'Reilly | Affiliated Companies

© 1999, O'Reilly & Associates, Inc.