Difference between revisions of "Setting up Samba as a Print Server"

(CUPS)
(Fixed incorrect location of the "printing" parameter. It must be set in [global], not in [printers].)
 
(75 intermediate revisions by 11 users not shown)
Line 1: Line 1:
==Using printers connected to the Samba server==
+
= Introduction =
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===
 
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 [[http://www.cups.org]]. 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 [[http://www.adobe.com/products/printerdrivers/main.html]]. The very big advantage of using Postscript as the printing language is that it doesn't matter whether your job has to be printed on a cheap inkjet or a big laser.
 
  
===LPD===
+
If you set up Samba as a print server, clients in your network are able to send print jobs to the Samba host using the server message block (SMB) protocol. The examples shown in this documentation use a raw printer in the back end. This configuration requires that the print job is formatted by a driver on the client and thus can be processed by the printer without further processing or filtering.
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.
 
==Providing Printer Drivers to Windows clients with the [print$] share==
 
===Uploading a printer driver===
 
===Directory structure in drivers directory===
 
The normal directory structure for your printer drivers looks like
 
<pre>drwxr-xr-x  2 root root  96 Feb 24 20:02 COLOR
 
drwxr-xr-x  2 root root  48 Feb 24 20:02 IA64
 
drwxr-xr-x  2 root root  48 Feb 24 20:02 W32ALPHA
 
drwxr-xr-x  2 root root  48 Feb 24 20:02 W32MIPS
 
drwxr-xr-x  2 root root  48 Feb 24 20:02 W32PPC
 
drwxr-xr-x  3 root root  72 Feb 24 20:02 W32X86
 
drwxr-xr-x  2 root root  48 Feb 24 20:02 WIN40
 
drwxr-xr-x  2 root root  48 Feb 24 20:02 x64
 
</pre>
 
You have to create it yourself. Here is a command line which does it. You only have to change the value of BASEDIR:
 
<pre>BASEDIR=/var/lib/samba/drivers;
 
for X in COLOR IA64 W32ALPHA W32MIPS W32PPC W32X86 WIN40 x64; do
 
  mkdir -p $BASEDIR/$X;
 
done</pre>
 
  
==Special settings on printer and faxes==
 
===Enabling new papersizes===
 
Only standardsizes of formulars are known. You have to add the neccessary sizes by hand.
 
  
# connect to the server \\<SambaServer>>
 
# printer -> Server Propertes -> Forms
 
# Create new form
 
::[[Image:SambaFormA0.png]]
 
:: A0 With 84,10 cm Height 118,90 cm
 
::[[Image:SambaFormA1.png]]
 
:: A1 With 59,40 cm cm Height 84,10 cm
 
# After this steps the large papersizes a shown in the different dialogs
 
  
The Size of the formulars depends on the ppds
 
  
==Using printers connected to another Samba or Windows server==
+
= Supported Print Server Back Ends =
===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.
+
Samba supports the multiple print server back ends, such as [https://www.cups.org/ CUPS] and [http://www.lprng.com/ LPRng]. For a complete list, see the <code>printing</code> parameter in the <code>smb.conf(5)</code> man page.
 +
 
 +
{{Imbox
 +
| type = note
 +
| text = You must set up the printer server back end locally on the Samba host. Samba cannot forward print jobs to a remote host. However, you can configure the local printer server back end to forward the job to a remote print server.
 +
}}
 +
 
 +
For details how to set up the back end, see the print server's documentation.
 +
 
 +
 
 +
 
 +
== Samba <code>CUPS</code> or <code>IPRINT</code> Back End Support ==
 +
 
 +
When using the <code>CUPS</code> or <code>IPRINT</code> print server back end, Samba must have been built with CUPS support enabled. To verify, enter:
 +
 
 +
# smbd -b | grep "HAVE_CUPS"
 +
    HAVE_CUPS
 +
 
 +
If no output is displayed:
 +
* Samba was built using the <code>--disable-cups</code> parameter.
 +
* The Samba <code>configure</code> script was unable to locate the required libraries for CUPS support. For details, see [[Package Dependencies Required to Build Samba]].
 +
 
 +
 
 +
 
 +
 
 +
 
 +
= Adding a printer to the Print Server Back End =
 +
 
 +
== CUPS ==
 +
 
 +
To add a raw printer to an CUPS print server:
 +
 
 +
* Open the CUPS admin web interface in your browser. For example, <nowiki>https://servername:631/admin</nowiki>
 +
 
 +
* Select the <code>Administration</code> tab and click <code>Add Printer</code>.
 +
 
 +
* Select the connection type and enter the corresponding URL to the printer's queue or to the remote print server queue. For example:
 +
:* LPD-based printers: <code>lpd://''printer_name''/''queue''</code>
 +
:* IPP (Internet Printing Protocol)-based printers: <code>ipp://''printer_name''/ipp/port</code>
 +
:* SMB (Server Message Block)-based printers: <code>smb://''username'':''password''@''domain''/''windows_print_server_host_name''/''printer_name''</code>
 +
:: Note that forwarding a job to a print server running Windows Vista or newer, or Windows Server 2008 or newer requires authentication.
 +
 
 +
* Enter a name for the printer. This name is used in the <code>smb.conf</code> when sharing the printer using Samba.
 +
 
 +
* Select the <code>Raw</code> printer vendor and model.
 +
 
 +
* Save the settings.
 +
 
 +
 
 +
 
 +
== LPRng ==
 +
 
 +
To add a raw printer to a LPRng print server:
 +
 
 +
* Add the following line to the <code>/etc/printcap</code> file:
 +
 
 +
''printer_name'':sd=/var/spool/lpd/''printer_name''/:sh:mx=0:mc=0:rm=''Printer_DNS_name_or_IP_address''
 +
: The printer name is used in the smb.conf when sharing the printer using Samba.
 +
: For further details about the options used, see the <code>printcap(5)</code> man page.
 +
 
 +
* To create the spool directory, enter:
 +
 
 +
# checkpc -f
 +
 
 +
* Restart the LPRng service.
 +
 
 +
 
 +
 
 +
 
 +
 
 +
= Enabling the <code>spoolssd</code> Service =
 +
 
 +
The Samba <code>spoolssd</code> is a service that is integrated into the smbd service. If you configured Samba as a print server, you can additionally enable <code>spoolssd</code> to:
 +
* Support package-aware Windows drivers.
 +
* Increase performance on print servers with a high number of jobs or printers.
 +
: Without <code>spoolssd</code>, Samba forks the <code>smbd</code> process or each print job and initializes the <code>printcap</code> cache. In case of a large number of printers, the <code>smbd</code> service can become unresponsive for multiple seconds when initializing the cache. The <code>spoolssd</code> service enables you to start pre-forked <code>smbd</code> processes that are processing print jobs without any delay. The main <code>spoolssd</code> <code>smbd</code> process uses a low amount of memory, and forks and terminates child processes
 +
 
 +
To enable the <code>spoolssd</code> service:
 +
 
 +
* Edit the <code>[global]</code> section in your <code>smb.conf</code> file:
 +
 
 +
:* Add the following parameters:
 +
 
 +
rpc_server:spoolss = external
 +
rpc_daemon:spoolssd = fork
 +
 
 +
:* Optionally, you can set the following parameters:
 +
::{| class="wikitable"
 +
!Parameter
 +
!Default
 +
!Description
 +
|-
 +
|spoolssd:prefork_min_children
 +
|5
 +
|Minimum number of child processes
 +
|-
 +
|spoolssd:prefork_max_children
 +
|25
 +
|Maximum number of child processes
 +
|-
 +
|spoolssd:prefork_spawn_rate
 +
|5
 +
|Samba forks this number of new child processes, up to the value set in <code>spoolssd:prefork_max_children</code>, if a new connection is established
 +
|-
 +
|spoolssd:prefork_max_allowed_clients
 +
|100
 +
|Number of clients, a child process serves
 +
|-
 +
|spoolssd:prefork_child_min_life
 +
|60
 +
|Minimum lifetime of a child process in seconds. 60 seconds is the minimum.
 +
|}
 +
 
 +
* Restart Samba.
 +
 
 +
After the restart, Samba automatically starts <code>smbd</code> sub-processes:
 +
# ps axf
 +
...
 +
30903 smbd
 +
30912  \_ smbd
 +
30913      \_ smbd
 +
30914      \_ smbd
 +
30915      \_ smbd
 +
...
 +
 
 +
 
 +
 
 +
 
 +
 
 +
= Enabling the Print Server Support in Samba =
 +
 
 +
To enable the print server support:
 +
 
 +
* Set the printing back end in the <code>printing</code> parameter of the <code>[global]</code> section in your <code>smb.conf</code> file. For example:
 +
printing = CUPS
 +
 
 +
* Add the following section to your <code>smb.conf</code>:
 +
 
 +
[printers]
 +
        path = /var/spool/samba/
 +
        printable = yes
 +
 
 +
* Create the spool directory set in the <code>path</code> parameter:
 +
 
 +
# mkdir -p /var/spool/samba/
 +
# chmod 1777 /var/spool/samba/
 +
 
 +
* Reload Samba:
 +
 
 +
# smbcontrol all reload-config
 +
 
 +
 
 +
 
 +
 
 +
 
 +
= Sharing a Printer =
 +
 
 +
== Automatic Sharing of All Printers Configured in the Print Server Back End ==
 +
 
 +
Using the default setting, all printers configured in the print server back end are automatically shared.
 +
 
 +
 
 +
 
 +
=== Disabling the Automatic Printer Sharing ===
 +
 
 +
To disable the automatic printer sharing:
 +
 
 +
* Add the following parameter to the <code>[global]</code> section of your <code>smb.conf</code> file:
 +
 
 +
load printers = no
 +
 
 +
* Reload Samba:
 +
 
 +
# smbcontrol all reload-config
 +
 
 +
 
 +
 
 +
== Manual Sharing of Printers ==
 +
 
 +
To manually share a printer:
 +
 
 +
* Verify that the automatic printer sharing is disabled. See [[#Disabling_the_Automatic_Printer_Sharing|Disabling the Automatic Printer Sharing]].
 +
 
 +
* Add the share for the printer to your <code>smb.conf</code> file:
 +
 
 +
[''Samba_printer_name'']
 +
        path = /var/spool/samba/
 +
        printable = yes
 +
        printer name = ''printer_name_in_the_back_end''
 +
 
 +
: Set the <code>printer name</code> parameter to the name of the printer used in the local print server back end.
 +
 
 +
* Reload Samba:
 +
 
 +
# smbcontrol all reload-config
 +
 
 +
 
 +
 
 +
 
 +
 
 +
= Setting up Automatic Printer Driver Download for Windows Clients =
 +
 
 +
See [[Setting_up_Automatic_Printer_Driver_Downloads_for_Windows_Clients|Setting up Automatic Printer Driver Downloads for Windows Clients]].
 +
 
 +
 
  
===Using a printer connected to a Windows server===
 
You also can use CUPS for it. CUPS has the special backend smb://<server>/<printer>. This in turn calls the smbspool program which is part of the samba suite. So if you set up a printer connected to a Windows server, you set up a normal printer with a special PrinterURI.
 
  
Note: the full form of that URI is: smb://[''<username>''[%''<password>'']@]//''<server>''/''<printer>''
 
  
 
----
 
----
--[[User:Rcsu|rcsu]] 15:34, 15 April 2006 (CDT)
+
[[Category:Active Directory]]
[[Category:Category Configuration]]
+
[[Category:Domain Members]]
 +
[[Category:NT4 Domains]]
 +
[[Category:Printing]]
 +
[[Category:Standalone Server]]

Latest revision as of 12:03, 18 October 2017

Introduction

If you set up Samba as a print server, clients in your network are able to send print jobs to the Samba host using the server message block (SMB) protocol. The examples shown in this documentation use a raw printer in the back end. This configuration requires that the print job is formatted by a driver on the client and thus can be processed by the printer without further processing or filtering.



Supported Print Server Back Ends

Samba supports the multiple print server back ends, such as CUPS and LPRng. For a complete list, see the printing parameter in the smb.conf(5) man page.

For details how to set up the back end, see the print server's documentation.


Samba CUPS or IPRINT Back End Support

When using the CUPS or IPRINT print server back end, Samba must have been built with CUPS support enabled. To verify, enter:

# smbd -b | grep "HAVE_CUPS"
   HAVE_CUPS

If no output is displayed:



Adding a printer to the Print Server Back End

CUPS

To add a raw printer to an CUPS print server:

  • Open the CUPS admin web interface in your browser. For example, https://servername:631/admin
  • Select the Administration tab and click Add Printer.
  • Select the connection type and enter the corresponding URL to the printer's queue or to the remote print server queue. For example:
  • LPD-based printers: lpd://printer_name/queue
  • IPP (Internet Printing Protocol)-based printers: ipp://printer_name/ipp/port
  • SMB (Server Message Block)-based printers: smb://username:password@domain/windows_print_server_host_name/printer_name
Note that forwarding a job to a print server running Windows Vista or newer, or Windows Server 2008 or newer requires authentication.
  • Enter a name for the printer. This name is used in the smb.conf when sharing the printer using Samba.
  • Select the Raw printer vendor and model.
  • Save the settings.


LPRng

To add a raw printer to a LPRng print server:

  • Add the following line to the /etc/printcap file:
printer_name:sd=/var/spool/lpd/printer_name/:sh:mx=0:mc=0:rm=Printer_DNS_name_or_IP_address
The printer name is used in the smb.conf when sharing the printer using Samba.
For further details about the options used, see the printcap(5) man page.
  • To create the spool directory, enter:
# checkpc -f
  • Restart the LPRng service.



Enabling the spoolssd Service

The Samba spoolssd is a service that is integrated into the smbd service. If you configured Samba as a print server, you can additionally enable spoolssd to:

  • Support package-aware Windows drivers.
  • Increase performance on print servers with a high number of jobs or printers.
Without spoolssd, Samba forks the smbd process or each print job and initializes the printcap cache. In case of a large number of printers, the smbd service can become unresponsive for multiple seconds when initializing the cache. The spoolssd service enables you to start pre-forked smbd processes that are processing print jobs without any delay. The main spoolssd smbd process uses a low amount of memory, and forks and terminates child processes

To enable the spoolssd service:

  • Edit the [global] section in your smb.conf file:
  • Add the following parameters:
rpc_server:spoolss = external
rpc_daemon:spoolssd = fork
  • Optionally, you can set the following parameters:
Parameter Default Description
spoolssd:prefork_min_children 5 Minimum number of child processes
spoolssd:prefork_max_children 25 Maximum number of child processes
spoolssd:prefork_spawn_rate 5 Samba forks this number of new child processes, up to the value set in spoolssd:prefork_max_children, if a new connection is established
spoolssd:prefork_max_allowed_clients 100 Number of clients, a child process serves
spoolssd:prefork_child_min_life 60 Minimum lifetime of a child process in seconds. 60 seconds is the minimum.
  • Restart Samba.

After the restart, Samba automatically starts smbd sub-processes:

# ps axf
...
30903 smbd
30912  \_ smbd
30913      \_ smbd
30914      \_ smbd
30915      \_ smbd
...



Enabling the Print Server Support in Samba

To enable the print server support:

  • Set the printing back end in the printing parameter of the [global] section in your smb.conf file. For example:
printing = CUPS
  • Add the following section to your smb.conf:
[printers]
       path = /var/spool/samba/
       printable = yes
  • Create the spool directory set in the path parameter:
# mkdir -p /var/spool/samba/
# chmod 1777 /var/spool/samba/
  • Reload Samba:
# smbcontrol all reload-config



Sharing a Printer

Automatic Sharing of All Printers Configured in the Print Server Back End

Using the default setting, all printers configured in the print server back end are automatically shared.


Disabling the Automatic Printer Sharing

To disable the automatic printer sharing:

  • Add the following parameter to the [global] section of your smb.conf file:
load printers = no
  • Reload Samba:
# smbcontrol all reload-config


Manual Sharing of Printers

To manually share a printer:

  • Add the share for the printer to your smb.conf file:
[Samba_printer_name]
       path = /var/spool/samba/
       printable = yes
       printer name = printer_name_in_the_back_end
Set the printer name parameter to the name of the printer used in the local print server back end.
  • Reload Samba:
# smbcontrol all reload-config



Setting up Automatic Printer Driver Download for Windows Clients

See Setting up Automatic Printer Driver Downloads for Windows Clients.