Setting up Samba as a Print Server
- 1 Using printers connected to the Samba server
- 2 Providing Printer Drivers to Windows clients with the [print$] share
- 3 Using printers connected to another Samba or Windows server
Using printers connected to the Samba server
In most of the cases you want to use printers which are directly connected to the samba server. A printer can be connected via various hardware devices (i.e. parallel port, usb, scsi and so forth). But thats not all, you have to take care about the fact that two users can request a print job at the same time. To serve this, you need a software which controls the printer.
CUPS is currently the most widely used spool system in Unix environments. Samba has built in support and defaults to CUPS if the develepment package (aka header files and librarys) could be found at compile time. The home of CUPS is []. Basically all sorts of files can be printed with CUPS, but using a Postscript printer driver will give you the most benefit and the client can controll the settings for the printers. A multi purpose printer driver for Windows can be found at the Adobe site, see []. The very big advantage of using Postscript as the printing language is that it doesn't matter wether your job has to be printed on a cheap inkjet or a big laser.
This is the first widely used printing system. It is very simple and doesnt use Postscript. But it is binary clean, so you can print to it directly via client side installed printer drivers.
Uploading a printer driver
Directory structure in drivers directory
Using printers connected to another Samba or Windows server
Using a printer connected to another Samba server
It is most likely that the other server is running CUPS to. So you only have to forward the print jobs to the other CUPS service. This is a simple to do in CUPS.
Using a printer connected to a Windows server
You also can use CUPS for it. More to come.