- PC Printing History
- Printer Communication Protocols and Hardware
- Network Printing Basics
- Setting Up Line Printer Remote on Windows Clients
- Printing PostScript and DOS Command Files
- Checking PostScript Printer Capabilities
- Setting Up LPR/LPD on FreeBSD
- Printer Accounting
- Microsoft Networking Client Printing with Samba
- Printing Between NT Server or NetWare and FreeBSD
- Printing from UNIX
- Managing the UNIX Print Queue
Microsoft Networking Client Printing with Samba
Although LPR is a time-tested and truly cross-platform printing solution, sites with a majority of Windows clients running Microsoft Networking have an alternate printing mechanismSamba. Samba can provide print services to clients running SMB-compatible network clients. With a running Samba installation, the administrator may share out printers as well as filesystem directories from the FreeBSD system (Figure 8.6).
Printers accessed with Samba must be defined in both the /etc/printcap file and the /usr/local/etc/smb.conf file. If the individual printers are defined in the smb.conf file with the printer driver= statement set to the exact model name of the printer, the "Auto printer driver install" feature of Windows NT and Win95/98 is activated. This automatically loads the correct printer driver if the user clicks on the print queue in Network Neighborhood under Win95 or NT 4.0. The restriction, of course, is that the printer model must be in the Windows client driver database.
The smb.conf file also defines the print command used to pass jobs to the UNIX print spool. It is a good idea to redefine this via the print command option to lpr -s -P %p %s; rm %s. This turns on soft linking, so that large print jobs don't get truncated.
In operation, the SMB-networking client builds the print job on itself and then transfers the entire job over the network to the Samba server. On the server, Samba has its own temporary print spool directory to which the job is copied. Once the job has been completely received, it is then passed to the UNIX print spooler.
Client Access Issues
Because a Windows client formats print jobs before sending them to the server, the administrator may want to hide some of the specialty print queues on the server. For example, the queue that converts LF to CRLF for UNIX text printouts would probably not be shared out. To make such queues invisible, the browseable=no option can be turned on in the smb.conf file. Also, the load printers option must be set to no to allow individual printer definitions.
Note - In general, the only print queues that should be visible through Samba are the "raw" print queues that are set up by the administrator to allow incoming preformatted print jobs.
Windows clients that print to Samba print queues on the UNIX system can view and cancel print jobs in the print queue. They cannot pause them, however, which is a difference between Novell and Windows NT Server print queues. They also cannot prioritize print jobs from the print queue window, although the administrator can reprioritize print jobs that are in the queue from a command shell on the FreeBSD server.
Printer Entries in Configuration Files
Following are listings of sample /etc/printcap and smb.conf files used on the system to provide print services. An explanation of the interaction of these files follows.
Listing 8.1 /etc/printcap
# # # The printer in lpt0 is a PostScript printer. The nec-crlf entry # is for testing the printer when it is switched into HP LaserJet III # mode. # lp|local line printer: :lp=/dev/lpt0:sd=/var/spool/output/lpd: :lf=/var/log/lpd-errs:sh:mx#0: # nec-crlf|NEC Silentwriter 95 in ASCII mode with UNIX text filter: :lp=/dev/lpt0:sd=/usr/lpdspool/nec-crlf: :lf=/var/log/lpd-errs:sh:mx#0: :if=/usr/local/libexec/crlfilter:tr=\f: # nec-raw|NEC Silentwriter 95 used for PostScript passthrough printing: :lp=/dev/lpt0:sd=/usr/lpdspool/nec-raw: :lf=/var/log/lpd-errs:sh:mx#0: # nec-ps-banner|NEC Silentwriter 95 with Postscript banner page created: :lp=/dev/lpt0:sd=/usr/lpdspool/nec-ps-banner: :lf=/var/log/lpd-errs:sh:mx#0:if=/usr/local/libexec/psbanner: # #
Listing 8.2 /usr/local/etc/smb.conf
[global] comment = FreeBSD - Samba %v log file = /var/log/samba.log dont descend = /dev,/proc,/root,/stand print command = lpr -s -P %p %s; rm %s interfaces = 10.0.0.1 (the system IP number goes here) printing = bsd map archive = no status = yes public = yes read only = no preserve case = yes strip dot = yes security = share guest ok = no password level = 1 dead time = 15 domain master = yes workgroup = WORKGROUP [homes] browseable = no comment = User Home Directory create mode = 0775 public = no [printers] path = /var/spool comment = Printers create mode = 0700 browseable = no read only = yes public = no [lp] printable = yes browseable = no [nec-raw] comment = Main Postscript printer driver for Windows clients printer driver = NEC SilentWriter 95 printable = yes browseable = yes [wwwroot] path = /usr/local/www read only = no create mode = 0775 comment = Internal Web Server
Following is the output of a net view command executed at a DOS prompt under Windows 95.
Shared resources at \\SERVER Sharename Type Comment ----------------------------------------------------- nec-crlf Print NEC Silentwriter 95 in ASCII mode nec-raw Print Main PostScript printer driver tedm Disk User Home Directory wwwroot Disk Internal Web Server The command was completed successfully.
In the /etc/printcap file four print queues are defined, all tied to the printer plugged in to the parallel port on the FreeBSD server. The first is lp, the generic local line printer. Since this print queue generally has a filter placed on it to format jobs from the UNIX print queue properly, it should not be visible on the SMB network (i.e., visible in Network Neighborhood). The second queue, nec-crlf, has a filter that converts UNIX text to text that prints without stairstepping, so it also should be hidden from the SMB network. The third, nec-raw, should be visible on the network because this is the spool that the Windows clients use. The last queue, nec-ps-banner, is another specialty queue for UNIX local printing and thus should not be visible.
When the smb.conf file is parsed, the default entry [printers] is first read and used as a set of defaults for printers that are going to be shared out. Next, the /etc/printcap file is read to get a list of all printers on the server. Last, each printer is checked for a service name in the smb.conf file that contains settings to override the set of defaults.
In the listing of what resources are visible on the network, both nec-crlf and nec-raw print queues are visible, and lp and nec-ps-banner are not. lp is not visible because there is a specific entry, [lp], in the smb.conf file that blocks it. nec-ps-banner doesn't have such an entry, but because the print queue name is not a legal length for an SMB name, it isn't shared out either.
The nec-crlf printer is visible so as to illustrate another pointcomments. If a print queue has no entry in the smb.conf file and is built by scanning the /etc/printcap file and using the [printers] defaults, the comment is taken from the /etc/printcap file next to the queue definition name. Otherwise, if an entry is made for the printer in the smb.conf file, the comment is taken from the entry in smb.conf.