|
From Windows Clients to a CUPS/Samba Print Server
Here is a simple recipe showing how you can take advantage of CUPS's
powerful features for the benefit of your Windows network printing
clients:
This requires the clients to use a PostScript driver (even if the
printer is a non-PostScript model. It also requires that you have a
driver on the CUPS server.
First, to enable CUPS-based printing through Samba, the following options should be set in your smb.conf
file
[global]
section:
printing = cups
|
printcap = cups
|
When these parameters are specified, all manually set print directives (like
print command or
lppause command) in smb.conf (as well as in Samba itself) will be
ignored. Instead, Samba will directly interface with CUPS through its application program interface (API), as
long as Samba has been compiled with CUPS library (libcups) support. If Samba has not been compiled with CUPS
support, and if no other print commands are set up, then printing will use the
System V
AT&T command set, with the -oraw option automatically passing through (if you want your own defined print
commands to work with a Samba server that has CUPS support compiled in, simply use
classicalprinting = sysv). This is illustrated in
the Printing via
CUPS/Samba Server diagram.
|
