- Timestamp:
- Nov 27, 2012, 4:43:17 PM (13 years ago)
- Location:
- trunk/server
- Files:
-
- 2 edited
-
. (modified) (1 prop)
-
docs/htmldocs/Samba3-HOWTO/classicalprinting.html (modified) (85 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/server
- Property svn:mergeinfo changed
/vendor/current merged: 581,587,591,594,597,600,615,618,740
- Property svn:mergeinfo changed
-
trunk/server/docs/htmldocs/Samba3-HOWTO/classicalprinting.html
r599 r745 1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 21. Classical Printing Support</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="msdfs.html" title="Chapter 20. Hosting a Microsoft Distributed File System Tree"><link rel="next" href="CUPS-printing.html" title="Chapter 22. CUPS Printing Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 21. Classical Printing Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="msdfs.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="CUPS-printing.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 21. Classical Printing Support"><div class="titlepage"><div><div><h2 class="title"><a name="classicalprinting"></a>Chapter 21. Classical Printing Support</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname">Danka Deutschland GmbH<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate">May 31, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="classicalprinting.html#id389000">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id389202">Technical Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id389339">Client to Samba Print Job Processing</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id389393">Printing-Related Configuration Parameters</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id389487">Simple Print Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id389756">Verifying Configuration with <code class="literal">testparm</code></a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id38993 8">Rapid Configuration Validation</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id390291">Extended Printing Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id390731">Detailed Explanation Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id393257">Point'n'Print Client Drivers on Samba Servers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id393411">The Obsoleted [printer$] Section</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id393521">Creating the [print$] Share</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id393729">[print$] Stanza Parameters</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id394022">The [print$] Share Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id394150">Installing Drivers into [print$]</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id394235">Add Printer Wizard Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#inst-rpc">Installing Print Drivers Using <code class="literal">rpcclient</code></a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id395945">Client Driver Installation Procedure</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id395960">First Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id396470">Additional Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id396581">Always Make First Client Connection as root or <span class="quote">“<span class="quote">printer admin</span>”</span></a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id396739">Other Gotchas</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id396756">Setting Default Print Options for Client Drivers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id397092">Supporting Large Numbers of Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id397328">Adding New Printers with the Windows NT APW</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id397565">Error Message: <span class="quote">“<span class="quote">Cannot connect under a different Name</span>”</span></a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id397664">Take Care When Assembling Driver Files</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id397864">Samba and Printer Ports</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id397963">Avoiding Common Client Driver Misconfiguration</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id397996">The Imprints Toolset</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id398034">What Is Imprints?</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id398063">Creating Printer Driver Packages</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id398076">The Imprints Server</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id398090">The Installation Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id398206">Adding Network Printers without User Interaction</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id398448">The <code class="literal">addprinter</code> Command</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id398481">Migration of Classical Printing to Samba</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id398612">Publishing Printer Information in Active Directory or LDAP</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id398639">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id398644">I Give My Root Password but I Do Not Get Access</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id398682">My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</a></span></dt></dl></dd></dl></div><div class="sect1" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id389000"></a>Features and Benefits</h2></div></div></div><p>2 <a class="indexterm" name="id38900 7"></a>1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 21. Classical Printing Support</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="msdfs.html" title="Chapter 20. Hosting a Microsoft Distributed File System Tree"><link rel="next" href="CUPS-printing.html" title="Chapter 22. CUPS Printing Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 21. Classical Printing Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="msdfs.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="CUPS-printing.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 21. Classical Printing Support"><div class="titlepage"><div><div><h2 class="title"><a name="classicalprinting"></a>Chapter 21. Classical Printing Support</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname">Danka Deutschland GmbH<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate">May 31, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="classicalprinting.html#id389000">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id389202">Technical Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id389339">Client to Samba Print Job Processing</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id389393">Printing-Related Configuration Parameters</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id389487">Simple Print Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id389756">Verifying Configuration with <code class="literal">testparm</code></a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id389939">Rapid Configuration Validation</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id390291">Extended Printing Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id390731">Detailed Explanation Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id393254">Point'n'Print Client Drivers on Samba Servers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id393408">The Obsoleted [printer$] Section</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id393519">Creating the [print$] Share</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id393726">[print$] Stanza Parameters</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id394019">The [print$] Share Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id394148">Installing Drivers into [print$]</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id394232">Add Printer Wizard Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#inst-rpc">Installing Print Drivers Using <code class="literal">rpcclient</code></a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id395921">Client Driver Installation Procedure</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id395936">First Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id396442">Additional Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id396553">Always Make First Client Connection as root or <span class="quote">“<span class="quote">printer admin</span>”</span></a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id396711">Other Gotchas</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id396728">Setting Default Print Options for Client Drivers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id397064">Supporting Large Numbers of Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id397300">Adding New Printers with the Windows NT APW</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id397538">Error Message: <span class="quote">“<span class="quote">Cannot connect under a different Name</span>”</span></a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id397636">Take Care When Assembling Driver Files</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id397860">Samba and Printer Ports</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id397959">Avoiding Common Client Driver Misconfiguration</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id397992">The Imprints Toolset</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id398030">What Is Imprints?</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id398060">Creating Printer Driver Packages</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id398072">The Imprints Server</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id398086">The Installation Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id398202">Adding Network Printers without User Interaction</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id398444">The <code class="literal">addprinter</code> Command</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id398477">Migration of Classical Printing to Samba</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id398608">Publishing Printer Information in Active Directory or LDAP</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id398635">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id398641">I Give My Root Password but I Do Not Get Access</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id398678">My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</a></span></dt></dl></dd></dl></div><div class="sect1" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id389000"></a>Features and Benefits</h2></div></div></div><p> 2 <a class="indexterm" name="id389008"></a> 3 3 Printing is often a mission-critical service for the users. Samba can provide this service reliably and 4 4 seamlessly for a client network consisting of Windows workstations. … … 7 7 <a class="indexterm" name="id389026"></a> 8 8 <a class="indexterm" name="id389033"></a> 9 <a class="indexterm" name="id3890 39"></a>9 <a class="indexterm" name="id389040"></a> 10 10 <a class="indexterm" name="id389046"></a> 11 11 <a class="indexterm" name="id389053"></a> 12 12 <a class="indexterm" name="id389060"></a> 13 13 <a class="indexterm" name="id389067"></a> 14 <a class="indexterm" name="id38907 3"></a>14 <a class="indexterm" name="id389074"></a> 15 15 <a class="indexterm" name="id389080"></a> 16 16 <a class="indexterm" name="id389087"></a> 17 17 <a class="indexterm" name="id389094"></a> 18 18 <a class="indexterm" name="id389101"></a> 19 <a class="indexterm" name="id38910 7"></a>19 <a class="indexterm" name="id389108"></a> 20 20 A Samba print service may be run on a standalone or domain member server, side by side with file serving 21 21 functions, or on a dedicated print server. It can be made as tightly or as loosely secured as needs dictate. … … 90 90 <a class="indexterm" name="id389401"></a> 91 91 <a class="indexterm" name="id389408"></a> 92 <a class="indexterm" name="id38941 4"></a>92 <a class="indexterm" name="id389415"></a> 93 93 There are a number of configuration parameters to control Samba's printing behavior. Please refer to the man 94 94 page for <code class="filename">smb.conf</code> for an overview of these. As with other parameters, there are global-level (tagged with a … … 137 137 <a class="indexterm" name="id389775"></a> 138 138 <a class="indexterm" name="id389782"></a> 139 <a class="indexterm" name="id38978 8"></a>139 <a class="indexterm" name="id389789"></a> 140 140 <a class="indexterm" name="id389795"></a> 141 141 <a class="indexterm" name="id389802"></a> 142 142 <a class="indexterm" name="id389809"></a> 143 143 <a class="indexterm" name="id389816"></a> 144 <a class="indexterm" name="id38982 2"></a>144 <a class="indexterm" name="id389823"></a> 145 145 <a class="indexterm" name="id389829"></a> 146 146 <a class="indexterm" name="id389836"></a> … … 195 195 <span class="quote">“<span class="quote">-v</span>”</span> switch, it only shows you the settings actually written into! To see the complete 196 196 configuration used, add the <span class="quote">“<span class="quote">-v</span>”</span> parameter to testparm. 197 </p></div></div><div class="sect2" title="Rapid Configuration Validation"><div class="titlepage"><div><div><h3 class="title"><a name="id38993 8"></a>Rapid Configuration Validation</h3></div></div></div><p>197 </p></div></div><div class="sect2" title="Rapid Configuration Validation"><div class="titlepage"><div><div><h3 class="title"><a name="id389939"></a>Rapid Configuration Validation</h3></div></div></div><p> 198 198 <a class="indexterm" name="id389947"></a> 199 199 <a class="indexterm" name="id389954"></a> … … 296 296 <a class="indexterm" name="id390299"></a> 297 297 <a class="indexterm" name="id390306"></a> 298 <a class="indexterm" name="id39031 2"></a>298 <a class="indexterm" name="id390313"></a> 299 299 <a class="indexterm" name="id390319"></a> 300 300 <a class="link" href="classicalprinting.html#extbsdpr" title="Example 21.2. Extended BSD Printing Configuration">Extended BSD Printing Configuration</a> shows a more verbose configuration for … … 305 305 are set by default. You could use a much leaner <code class="filename">smb.conf</code> file, or you can use <code class="literal">testparm</code> or 306 306 <code class="literal">SWAT</code> to optimize the <code class="filename">smb.conf</code> file to remove all parameters that are set at default. 307 </p><div class="example"><a name="extbsdpr"></a><p class="title"><b>Example 21.2. Extended BSD Printing Configuration</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id390388"></a><em class="parameter"><code>printing = bsd</code></em></td></tr><tr><td><a class="indexterm" name="id390399"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td><a class="indexterm" name="id39041 0"></a><em class="parameter"><code>show add printer wizard = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390422"></a><em class="parameter"><code>printcap name = /etc/printcap</code></em></td></tr><tr><td><a class="indexterm" name="id390434"></a><em class="parameter"><code>printer admin = @ntadmin, root</code></em></td></tr><tr><td><a class="indexterm" name="id390445"></a><em class="parameter"><code>max print jobs = 100</code></em></td></tr><tr><td><a class="indexterm" name="id390457"></a><em class="parameter"><code>lpq cache time = 20</code></em></td></tr><tr><td><a class="indexterm" name="id390468"></a><em class="parameter"><code>use client driver = no</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id390489"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id390500"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390512"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id390523"></a><em class="parameter"><code>browseable = no</code></em></td></tr><tr><td><a class="indexterm" name="id390534"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390546"></a><em class="parameter"><code>public = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390557"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390569"></a><em class="parameter"><code>writable = no </code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[my_printer_name]</code></em></td></tr><tr><td><a class="indexterm" name="id390589"></a><em class="parameter"><code>comment = Printer with Restricted Access</code></em></td></tr><tr><td><a class="indexterm" name="id390601"></a><em class="parameter"><code>path = /var/spool/samba_my_printer</code></em></td></tr><tr><td><a class="indexterm" name="id390613"></a><em class="parameter"><code>printer admin = kurt</code></em></td></tr><tr><td><a class="indexterm" name="id390624"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390636"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390647"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id390658"></a><em class="parameter"><code>hosts allow = 0.0.0.0</code></em></td></tr><tr><td><a class="indexterm" name="id390670"></a><em class="parameter"><code>hosts deny = turbo_xp, 10.160.50.23, 10.160.51.60</code></em></td></tr><tr><td><a class="indexterm" name="id390682"></a><em class="parameter"><code>guest ok = no</code></em></td></tr></table></div></div><br class="example-break"><p>307 </p><div class="example"><a name="extbsdpr"></a><p class="title"><b>Example 21.2. Extended BSD Printing Configuration</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id390388"></a><em class="parameter"><code>printing = bsd</code></em></td></tr><tr><td><a class="indexterm" name="id390399"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390411"></a><em class="parameter"><code>show add printer wizard = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390422"></a><em class="parameter"><code>printcap name = /etc/printcap</code></em></td></tr><tr><td><a class="indexterm" name="id390434"></a><em class="parameter"><code>printer admin = @ntadmin, root</code></em></td></tr><tr><td><a class="indexterm" name="id390445"></a><em class="parameter"><code>max print jobs = 100</code></em></td></tr><tr><td><a class="indexterm" name="id390457"></a><em class="parameter"><code>lpq cache time = 20</code></em></td></tr><tr><td><a class="indexterm" name="id390468"></a><em class="parameter"><code>use client driver = no</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id390489"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id390500"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390512"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id390523"></a><em class="parameter"><code>browseable = no</code></em></td></tr><tr><td><a class="indexterm" name="id390535"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390546"></a><em class="parameter"><code>public = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390558"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390569"></a><em class="parameter"><code>writable = no </code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[my_printer_name]</code></em></td></tr><tr><td><a class="indexterm" name="id390589"></a><em class="parameter"><code>comment = Printer with Restricted Access</code></em></td></tr><tr><td><a class="indexterm" name="id390601"></a><em class="parameter"><code>path = /var/spool/samba_my_printer</code></em></td></tr><tr><td><a class="indexterm" name="id390613"></a><em class="parameter"><code>printer admin = kurt</code></em></td></tr><tr><td><a class="indexterm" name="id390624"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390636"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id390647"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id390659"></a><em class="parameter"><code>hosts allow = 0.0.0.0</code></em></td></tr><tr><td><a class="indexterm" name="id390670"></a><em class="parameter"><code>hosts deny = turbo_xp, 10.160.50.23, 10.160.51.60</code></em></td></tr><tr><td><a class="indexterm" name="id390682"></a><em class="parameter"><code>guest ok = no</code></em></td></tr></table></div></div><br class="example-break"><p> 308 308 <a class="indexterm" name="id390695"></a> 309 309 <a class="indexterm" name="id390701"></a> … … 315 315 </p><div class="sect2" title="Detailed Explanation Settings"><div class="titlepage"><div><div><h3 class="title"><a name="id390731"></a>Detailed Explanation Settings</h3></div></div></div><p> 316 316 The following is a discussion of the settings from <a class="link" href="classicalprinting.html#extbsdpr" title="Example 21.2. Extended BSD Printing Configuration">Extended BSD Printing 317 Configuration</a> <a class="link" href="classicalprinting.html#extbsdpr" title="Example 21.2. Extended BSD Printing Configuration">Extended BSD Printing Configuration</a>. 318 </p><div class="sect3" title="The [global] Section"><div class="titlepage"><div><div><h4 class="title"><a name="id390754"></a>The [global] Section</h4></div></div></div><p> 317 Configuration</a>. 318 </p><div class="sect3" title="The [global] Section"><div class="titlepage"><div><div><h4 class="title"><a name="id390748"></a>The [global] Section</h4></div></div></div><p> 319 <a class="indexterm" name="id390755"></a> 319 320 <a class="indexterm" name="id390762"></a> 320 321 <a class="indexterm" name="id390769"></a> 321 <a class="indexterm" name="id390775"></a> 322 <a class="indexterm" name="id390782"></a> 322 <a class="indexterm" name="id390776"></a> 323 323 The <em class="parameter"><code>[global]</code></em> section is one of four special sections (along with <em class="parameter"><code>[homes]</code></em>, <em class="parameter"><code>[printers]</code></em>, and <em class="parameter"><code>[print$]</code></em>). The 324 324 <em class="parameter"><code>[global]</code></em> contains all parameters that apply to the server as a whole. It is the place … … 328 328 globally set share settings and specify other values). 329 329 </p><div class="variablelist"><dl><dt><span class="term"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = bsd </a></span></dt><dd><p> 330 <a class="indexterm" name="id39084 3"></a>331 <a class="indexterm" name="id3908 50"></a>332 <a class="indexterm" name="id39085 7"></a>333 <a class="indexterm" name="id39086 4"></a>334 <a class="indexterm" name="id3908 70"></a>335 <a class="indexterm" name="id39087 7"></a>336 <a class="indexterm" name="id39088 4"></a>337 <a class="indexterm" name="id3908 91"></a>338 <a class="indexterm" name="id39089 8"></a>339 <a class="indexterm" name="id39090 4"></a>340 <a class="indexterm" name="id3909 11"></a>341 <a class="indexterm" name="id39091 8"></a>330 <a class="indexterm" name="id390841"></a> 331 <a class="indexterm" name="id390847"></a> 332 <a class="indexterm" name="id390854"></a> 333 <a class="indexterm" name="id390861"></a> 334 <a class="indexterm" name="id390868"></a> 335 <a class="indexterm" name="id390874"></a> 336 <a class="indexterm" name="id390881"></a> 337 <a class="indexterm" name="id390888"></a> 338 <a class="indexterm" name="id390895"></a> 339 <a class="indexterm" name="id390901"></a> 340 <a class="indexterm" name="id390908"></a> 341 <a class="indexterm" name="id390915"></a> 342 342 Causes Samba to use default print commands applicable for the BSD (also known as RFC 1179 style or LPR/LPD) 343 343 printing system. In general, the <em class="parameter"><code>printing</code></em> parameter informs Samba about the print … … 345 345 systems defaults to a different <a class="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command</a> (and other queue control commands). 346 346 </p><div class="caution" title="Caution" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Caution</h3><p> 347 <a class="indexterm" name="id3909 50"></a>348 <a class="indexterm" name="id39095 7"></a>347 <a class="indexterm" name="id390947"></a> 348 <a class="indexterm" name="id390954"></a> 349 349 The <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing</a> parameter is normally a service-level parameter. Since it is included 350 350 here in the <em class="parameter"><code>[global]</code></em> section, it will take effect for all printer shares that are not 351 351 defined differently. Samba-3 no longer supports the SOFTQ printing system. 352 352 </p></div></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#LOADPRINTERS" target="_top">load printers = yes </a></span></dt><dd><p> 353 <a class="indexterm" name="id39 1000"></a>354 <a class="indexterm" name="id39100 6"></a>355 <a class="indexterm" name="id39101 3"></a>356 <a class="indexterm" name="id3910 20"></a>353 <a class="indexterm" name="id390997"></a> 354 <a class="indexterm" name="id391004"></a> 355 <a class="indexterm" name="id391010"></a> 356 <a class="indexterm" name="id391017"></a> 357 357 Tells Samba to create automatically all available printer shares. Available printer shares are discovered by 358 358 scanning the printcap file. All created printer shares are also loaded for browsing. If you use this … … 362 362 share separately, leaving out some you do not want to be publicly visible and available). 363 363 </p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#SHOWADDPRINTERWIZARD" target="_top">show add printer wizard = yes </a></span></dt><dd><p> 364 <a class="indexterm" name="id39106 3"></a>365 <a class="indexterm" name="id39106 9"></a>366 <a class="indexterm" name="id39107 6"></a>367 <a class="indexterm" name="id39108 3"></a>368 <a class="indexterm" name="id3910 90"></a>364 <a class="indexterm" name="id391060"></a> 365 <a class="indexterm" name="id391066"></a> 366 <a class="indexterm" name="id391073"></a> 367 <a class="indexterm" name="id391080"></a> 368 <a class="indexterm" name="id391087"></a> 369 369 Setting is normally enabled by default (even if the parameter is not specified in <code class="filename">smb.conf</code>). It causes the 370 370 <span class="guiicon">Add Printer Wizard</span> icon to appear in the <span class="guiicon">Printers</span> folder of the Samba … … 375 375 before the action), or exchange a printer's driver for any other previously uploaded driver. 376 376 </p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#MAXPRINTJOBS" target="_top">max print jobs = 100 </a></span></dt><dd><p> 377 <a class="indexterm" name="id39116 5"></a>377 <a class="indexterm" name="id391162"></a> 378 378 Sets the upper limit to 100 print jobs being active on the Samba server at any one time. Should a client 379 379 submit a job that exceeds this number, a "no more space available on server" type of error message will be … … 381 381 at all. 382 382 </p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#PRINTCAPNAME" target="_top">printcap name = /etc/printcap </a></span></dt><dd><p> 383 <a class="indexterm" name="id39119 7"></a>384 <a class="indexterm" name="id39120 4"></a>385 <a class="indexterm" name="id3912 10"></a>383 <a class="indexterm" name="id391194"></a> 384 <a class="indexterm" name="id391201"></a> 385 <a class="indexterm" name="id391208"></a> 386 386 Tells Samba where to look for a list of available printer names. Where CUPS is used, make sure that a printcap 387 387 file is written. This is controlled by the <code class="constant">Printcap</code> directive in the 388 388 <code class="filename">cupsd.conf</code> file. 389 389 </p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#PRINTERADMIN" target="_top">printer admin = @ntadmin </a></span></dt><dd><p> 390 <a class="indexterm" name="id39124 6"></a>391 <a class="indexterm" name="id3912 52"></a>392 <a class="indexterm" name="id39125 9"></a>393 <a class="indexterm" name="id39126 6"></a>390 <a class="indexterm" name="id391243"></a> 391 <a class="indexterm" name="id391249"></a> 392 <a class="indexterm" name="id391256"></a> 393 <a class="indexterm" name="id391263"></a> 394 394 Members of the ntadmin group should be able to add drivers and set printer properties 395 395 (<code class="constant">ntadmin</code> is only an example name; it needs to be a valid UNIX group name); root is … … 400 400 per-share parameter. This permits different groups to administer each printer share. 401 401 </p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#LPQCACHETIME" target="_top">lpq cache time = 20 </a></span></dt><dd><p> 402 <a class="indexterm" name="id39133 8"></a>403 <a class="indexterm" name="id39134 5"></a>402 <a class="indexterm" name="id391336"></a> 403 <a class="indexterm" name="id391342"></a> 404 404 Controls the cache time for the results of the lpq command. It prevents the lpq command being called too often 405 405 and reduces the load on a heavily used print server. 406 406 </p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#USECLIENTDRIVER" target="_top">use client driver = no </a></span></dt><dd><p> 407 <a class="indexterm" name="id3913 72"></a>407 <a class="indexterm" name="id391369"></a> 408 408 If set to <code class="constant">yes</code>, only takes effect for Windows NT/200x/XP clients (and not for Win 409 409 95/98/ME). Its default value is <code class="constant">No</code> (or <code class="constant">False</code>). It must … … 412 412 explanations, see the <code class="filename">smb.conf</code> man page. 413 413 </p></dd></dl></div></div><div class="sect3" title="The [printers] Section"><div class="titlepage"><div><div><h4 class="title"><a name="ptrsect"></a>The [printers] Section</h4></div></div></div><p> 414 <a class="indexterm" name="id3914 22"></a>415 <a class="indexterm" name="id39142 9"></a>414 <a class="indexterm" name="id391419"></a> 415 <a class="indexterm" name="id391426"></a> 416 416 The printers section is the second special section. If a section with this name appears in the <code class="filename">smb.conf</code>, 417 417 users are able to connect to any printer specified in the Samba host's printcap file, because Samba on startup … … 469 469 </p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#WRITABLE" target="_top">writable = no </a></span></dt><dd><p> 470 470 Is a synonym for <a class="link" href="smb.conf.5.html#READONLY" target="_top">read only = yes</a>. 471 </p></dd></dl></div></div><div class="sect3" title="Any [my_printer_name] Section"><div class="titlepage"><div><div><h4 class="title"><a name="id3917 82"></a>Any [my_printer_name] Section</h4></div></div></div><p>472 <a class="indexterm" name="id3917 90"></a>473 <a class="indexterm" name="id39179 6"></a>471 </p></dd></dl></div></div><div class="sect3" title="Any [my_printer_name] Section"><div class="titlepage"><div><div><h4 class="title"><a name="id391779"></a>Any [my_printer_name] Section</h4></div></div></div><p> 472 <a class="indexterm" name="id391787"></a> 473 <a class="indexterm" name="id391794"></a> 474 474 If a <em class="parameter"><code>[my_printer_name]</code></em> section appears in the <code class="filename">smb.conf</code> file, which includes the 475 475 parameter <a class="link" href="smb.conf.5.html#PRINTABLE" target="_top">printable = yes</a> Samba will configure it as a printer share. … … 503 503 </p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#GUESTOK" target="_top">guest ok = no </a></span></dt><dd><p> 504 504 This printer is not open for the guest account. 505 </p></dd></dl></div></div><div class="sect3" title="Print Commands"><div class="titlepage"><div><div><h4 class="title"><a name="id39205 5"></a>Print Commands</h4></div></div></div><p>506 <a class="indexterm" name="id3920 62"></a>507 <a class="indexterm" name="id39206 9"></a>508 <a class="indexterm" name="id39207 6"></a>509 <a class="indexterm" name="id39208 2"></a>505 </p></dd></dl></div></div><div class="sect3" title="Print Commands"><div class="titlepage"><div><div><h4 class="title"><a name="id392052"></a>Print Commands</h4></div></div></div><p> 506 <a class="indexterm" name="id392059"></a> 507 <a class="indexterm" name="id392066"></a> 508 <a class="indexterm" name="id392073"></a> 509 <a class="indexterm" name="id392080"></a> 510 510 In each section defining a printer (or in the <em class="parameter"><code>[printers]</code></em> section), 511 511 a <em class="parameter"><code>print command</code></em> parameter may be defined. It sets a command to process the files … … 519 519 make sure you pay attention to the need to remove the files from the Samba spool directory. Otherwise, 520 520 your hard disk may soon suffer from shortage of free space. 521 </p></div><div class="sect3" title="Default UNIX System Printing Commands"><div class="titlepage"><div><div><h4 class="title"><a name="id3921 22"></a>Default UNIX System Printing Commands</h4></div></div></div><p>522 <a class="indexterm" name="id3921 30"></a>521 </p></div><div class="sect3" title="Default UNIX System Printing Commands"><div class="titlepage"><div><div><h4 class="title"><a name="id392119"></a>Default UNIX System Printing Commands</h4></div></div></div><p> 522 <a class="indexterm" name="id392127"></a> 523 523 You learned earlier that Samba, in most cases, uses its built-in settings for many parameters if it cannot 524 524 find an explicitly stated one in its configuration file. The same is true for the <a class="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command</a>. The default print command varies depending on the <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing</a> parameter … … 529 529 of key printing options but excludes the special case of CUPS, is discussed in <a class="link" href="CUPS-printing.html" title="Chapter 22. CUPS Printing Support">CUPS Printing Support</a>. 530 530 </p><div class="table"><a name="printOptions"></a><p class="title"><b>Table 21.1. Default Printing Settings</b></p><div class="table-contents"><table summary="Default Printing Settings" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th align="left">Setting</th><th align="left">Default Printing Commands</th></tr></thead><tbody><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = bsd|aix|lprng|plp</a></td><td align="left">print command is <code class="literal">lpr -r -P%p %s</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = sysv|hpux</a></td><td align="left">print command is <code class="literal">lp -c -P%p %s; rm %s</code></td></tr><tr><td align="left"> <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = qnx</a></td><td align="left">print command is <code class="literal">lp -r -P%p -s %s</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = bsd|aix|lprng|plp</a></td><td align="left">lpq command is <code class="literal">lpq -P%p</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = sysv|hpux</a></td><td align="left">lpq command is <code class="literal">lpstat -o%p</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = qnx</a></td><td align="left">lpq command is <code class="literal">lpq -P%p</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = bsd|aix|lprng|plp</a></td><td align="left">lprm command is <code class="literal">lprm -P%p %j</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = sysv|hpux</a></td><td align="left">lprm command is <code class="literal">cancel %p-%j</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = qnx</a></td><td align="left">lprm command is <code class="literal">cancel %p-%j</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = bsd|aix|lprng|plp</a></td><td align="left">lppause command is <code class="literal">lp -i %p-%j -H hold</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = sysv|hpux</a></td><td align="left">lppause command (...is empty)</td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = qnx</a></td><td align="left">lppause command (...is empty)</td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = bsd|aix|lprng|plp</a></td><td align="left">lpresume command is <code class="literal">lp -i %p-%j -H resume</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = sysv|hpux</a></td><td align="left">lpresume command (...is empty)</td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = qnx</a></td><td align="left">lpresume command (...is empty)</td></tr></tbody></table></div></div><br class="table-break"><p> 531 <a class="indexterm" name="id3925 70"></a>532 <a class="indexterm" name="id39257 7"></a>533 <a class="indexterm" name="id39258 3"></a>534 <a class="indexterm" name="id3925 90"></a>531 <a class="indexterm" name="id392567"></a> 532 <a class="indexterm" name="id392574"></a> 533 <a class="indexterm" name="id392581"></a> 534 <a class="indexterm" name="id392587"></a> 535 535 For <em class="parameter"><code>printing = CUPS</code></em>, if Samba is compiled against libcups, it uses the CUPS API to 536 536 submit jobs. (It is a good idea also to set <a class="link" href="smb.conf.5.html#PRINTCAP" target="_top">printcap = cups</a> in case your … … 539 539 <code class="literal">lp -c -d%p -oraw; rm %s</code>. With <em class="parameter"><code>printing = cups</code></em>, and if Samba is 540 540 compiled against libcups, any manually set print command will be ignored! 541 </p></div><div class="sect3" title="Custom Print Commands"><div class="titlepage"><div><div><h4 class="title"><a name="id39263 8"></a>Custom Print Commands</h4></div></div></div><p>542 <a class="indexterm" name="id39264 6"></a>543 <a class="indexterm" name="id39265 3"></a>541 </p></div><div class="sect3" title="Custom Print Commands"><div class="titlepage"><div><div><h4 class="title"><a name="id392635"></a>Custom Print Commands</h4></div></div></div><p> 542 <a class="indexterm" name="id392643"></a> 543 <a class="indexterm" name="id392650"></a> 544 544 After a print job has finished spooling to a service, the <a class="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command</a> will be used 545 545 by Samba via a system() call to process the spool file. Usually the command specified will submit the spool … … 548 548 that the spool file is deleted after it has been processed. 549 549 </p><p> 550 <a class="indexterm" name="id39267 7"></a>551 <a class="indexterm" name="id39268 4"></a>552 <a class="indexterm" name="id3926 91"></a>553 <a class="indexterm" name="id39269 8"></a>550 <a class="indexterm" name="id392675"></a> 551 <a class="indexterm" name="id392681"></a> 552 <a class="indexterm" name="id392688"></a> 553 <a class="indexterm" name="id392695"></a> 554 554 There is no difficulty with using your own customized print commands with the traditional printing systems. 555 555 However, if you do not wish to roll your own, you should be well informed about the default built-in commands … … 561 561 printing, the following ones do have special relevance: 562 562 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><em class="parameter"><code>%s, %f</code></em> the path to the spool file name.</p></li><li class="listitem"><p><em class="parameter"><code>%p</code></em> the appropriate printer name.</p></li><li class="listitem"><p><em class="parameter"><code>%J</code></em> the job name as transmitted by the client.</p></li><li class="listitem"><p><em class="parameter"><code>%c</code></em> the number of printed pages of the spooled job (if known).</p></li><li class="listitem"><p><em class="parameter"><code>%z</code></em> the size of the spooled print job (in bytes).</p></li></ul></div><p> 563 <a class="indexterm" name="id3927 90"></a>563 <a class="indexterm" name="id392787"></a> 564 564 The print command must contain at least one occurrence of <em class="parameter"><code>%s</code></em> or 565 565 <em class="parameter"><code>%f</code></em>. The <em class="parameter"><code>%p</code></em> is optional. If no printer name is supplied, … … 567 567 sent to the default printer. 568 568 </p><p> 569 <a class="indexterm" name="id39282 3"></a>570 <a class="indexterm" name="id3928 30"></a>569 <a class="indexterm" name="id392820"></a> 570 <a class="indexterm" name="id392827"></a> 571 571 If specified in the <em class="parameter"><code>[global]</code></em> section, the print command given will be 572 572 used for any printable service that does not have its own print command specified. If there is neither a … … 574 574 but not processed! Most importantly, print files will not be removed, so they will consume disk space. 575 575 </p><p> 576 <a class="indexterm" name="id39284 9"></a>577 <a class="indexterm" name="id39285 6"></a>576 <a class="indexterm" name="id392846"></a> 577 <a class="indexterm" name="id392853"></a> 578 578 Printing may fail on some UNIX systems when using the <span class="emphasis"><em>nobody</em></span> account. If this happens, create an 579 579 alternative guest account and give it the privilege to print. Set up this guest account in the 580 580 <em class="parameter"><code>[global]</code></em> section with the <em class="parameter"><code>guest account</code></em> parameter. 581 581 </p><p> 582 <a class="indexterm" name="id39288 3"></a>583 <a class="indexterm" name="id3928 90"></a>584 <a class="indexterm" name="id39289 7"></a>582 <a class="indexterm" name="id392880"></a> 583 <a class="indexterm" name="id392887"></a> 584 <a class="indexterm" name="id392894"></a> 585 585 You can form quite complex print commands. You need to realize that print commands are just 586 586 passed to a UNIX shell. The shell is able to expand the included environment variables as … … 588 588 in the Samba print command is <em class="parameter"><code>%$variable</code></em>.) To give you a working 589 589 <a class="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command</a> example, the following will log a print job 590 to <code class="filename">/tmp/print.log</code>, print the file, then remove it. The semicolon (<span class="quote">“<span class="quote">;</span>”</span> 590 to <code class="filename">/tmp/print.log</code>, print the file, then remove it. The semicolon (<span class="quote">“<span class="quote">;</span>”</span>) 591 591 is the usual separator for commands in shell scripts: 592 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id39294 7"></a><em class="parameter"><code>print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s</code></em></td></tr></table><p>592 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id392944"></a><em class="parameter"><code>print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s</code></em></td></tr></table><p> 593 593 You may have to vary your own command considerably from this example depending on how you normally print 594 594 files on your system. The default for the <a class="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command</a> 595 595 parameter varies depending on the setting of the <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing</a> 596 596 parameter. Another example is: 597 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id39299 3"></a><em class="parameter"><code>print command = /usr/local/samba/bin/myprintscript %p %s</code></em></td></tr></table></div></div></div><div class="sect1" title="Printing Developments Since Samba-2.2"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cups-msrpc"></a>Printing Developments Since Samba-2.2</h2></div></div></div><p>598 <a class="indexterm" name="id3930 20"></a>599 <a class="indexterm" name="id39302 6"></a>600 <a class="indexterm" name="id39303 3"></a>597 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id392990"></a><em class="parameter"><code>print command = /usr/local/samba/bin/myprintscript %p %s</code></em></td></tr></table></div></div></div><div class="sect1" title="Printing Developments Since Samba-2.2"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cups-msrpc"></a>Printing Developments Since Samba-2.2</h2></div></div></div><p> 598 <a class="indexterm" name="id393017"></a> 599 <a class="indexterm" name="id393023"></a> 600 <a class="indexterm" name="id393030"></a> 601 601 Prior to Samba-2.2.x, print server support for Windows clients was limited to <span class="emphasis"><em>LanMan</em></span> 602 602 printing calls. This is the same protocol level as Windows 9x/Me PCs offer when they share printers. … … 607 607 The additional functionality provided by the new SPOOLSS support includes: 608 608 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> 609 <a class="indexterm" name="id39306 3"></a>609 <a class="indexterm" name="id393061"></a> 610 610 Support for downloading printer driver files to Windows 95/98/NT/2000 clients upon 611 611 demand (<span class="emphasis"><em>Point'n'Print</em></span>). 612 612 </p></li><li class="listitem"><p> 613 <a class="indexterm" name="id39307 9"></a>613 <a class="indexterm" name="id393076"></a> 614 614 Uploading of printer drivers via the Windows NT <span class="emphasis"><em>Add Printer Wizard</em></span> (APW) 615 615 or the <a class="ulink" href="http://imprints.sourceforge.net/" target="_top">Imprints</a> tool set. 616 616 </p></li><li class="listitem"><p> 617 <a class="indexterm" name="id393 101"></a>618 <a class="indexterm" name="id39310 8"></a>619 <a class="indexterm" name="id39311 5"></a>620 <a class="indexterm" name="id3931 21"></a>621 <a class="indexterm" name="id39312 8"></a>617 <a class="indexterm" name="id393098"></a> 618 <a class="indexterm" name="id393105"></a> 619 <a class="indexterm" name="id393112"></a> 620 <a class="indexterm" name="id393119"></a> 621 <a class="indexterm" name="id393126"></a> 622 622 Support for the native MS-RPC printing calls such as StartDocPrinter, EnumJobs(), and so on. (See the 623 623 <a class="ulink" href="http://msdn.microsoft.com/" target="_top">MSDN documentation</a> for more information on the 624 624 Win32 printing API). 625 625 </p></li><li class="listitem"><p> 626 <a class="indexterm" name="id39314 7"></a>627 <a class="indexterm" name="id39315 3"></a>626 <a class="indexterm" name="id393144"></a> 627 <a class="indexterm" name="id393151"></a> 628 628 Support for NT Access Control Lists (ACL) on printer objects. 629 629 </p></li><li class="listitem"><p> 630 <a class="indexterm" name="id39316 5"></a>630 <a class="indexterm" name="id393162"></a> 631 631 Improved support for printer queue manipulation through the use of internal databases for spooled 632 632 job information (implemented by various <code class="filename">*.tdb</code> files). 633 633 </p></li></ul></div><p> 634 <a class="indexterm" name="id39318 3"></a>635 <a class="indexterm" name="id3931 90"></a>634 <a class="indexterm" name="id393181"></a> 635 <a class="indexterm" name="id393187"></a> 636 636 A benefit of updating is that Samba-3 is able to publish its printers to Active Directory (or LDAP). 637 637 </p><p> 638 <a class="indexterm" name="id393 201"></a>638 <a class="indexterm" name="id393198"></a> 639 639 A fundamental difference exists between MS Windows NT print servers and Samba operation. Windows NT 640 640 permits the installation of local printers that are not shared. This is an artifact of the fact that … … 642 642 printers that are made available, either by default or by specific declaration via printer-specific shares. 643 643 </p><p> 644 <a class="indexterm" name="id39321 4"></a>645 <a class="indexterm" name="id3932 21"></a>646 <a class="indexterm" name="id39322 8"></a>647 <a class="indexterm" name="id39323 5"></a>648 <a class="indexterm" name="id3932 41"></a>644 <a class="indexterm" name="id393212"></a> 645 <a class="indexterm" name="id393218"></a> 646 <a class="indexterm" name="id393225"></a> 647 <a class="indexterm" name="id393232"></a> 648 <a class="indexterm" name="id393239"></a> 649 649 Windows NT/200x/XP Professional clients do not have to use the standard SMB printer share; they can 650 650 print directly to any printer on another Windows NT host using MS-RPC. This, of course, assumes that … … 653 653 <span class="emphasis"><em>Everyone</em></span> group. (The older clients of type Windows 9x/Me can only print to shared 654 654 printers.) 655 </p><div class="sect2" title="Point'n'Print Client Drivers on Samba Servers"><div class="titlepage"><div><div><h3 class="title"><a name="id39325 7"></a>Point'n'Print Client Drivers on Samba Servers</h3></div></div></div><p>656 <a class="indexterm" name="id39326 5"></a>655 </p><div class="sect2" title="Point'n'Print Client Drivers on Samba Servers"><div class="titlepage"><div><div><h3 class="title"><a name="id393254"></a>Point'n'Print Client Drivers on Samba Servers</h3></div></div></div><p> 656 <a class="indexterm" name="id393262"></a> 657 657 There is much confusion about what all this means. The question is often asked, <span class="quote">“<span class="quote">Is it or is 658 658 it not necessary for printer drivers to be installed on a Samba host in order to support printing from 659 659 Windows clients?</span>”</span> The answer to this is no, it is not necessary. 660 660 </p><p> 661 <a class="indexterm" name="id3932 81"></a>662 <a class="indexterm" name="id39328 8"></a>661 <a class="indexterm" name="id393278"></a> 662 <a class="indexterm" name="id393285"></a> 663 663 Windows NT/2000 clients can, of course, also run their APW to install drivers <span class="emphasis"><em>locally</em></span> 664 664 (which then connect to a Samba-served print queue). This is the same method used by Windows 9x/Me … … 666 666 require that the Samba server possess a valid driver for the printer. This was fixed in Samba 2.2.1). 667 667 </p><p> 668 <a class="indexterm" name="id39330 4"></a>669 <a class="indexterm" name="id3933 11"></a>668 <a class="indexterm" name="id393302"></a> 669 <a class="indexterm" name="id393309"></a> 670 670 But it is a new capability to install the printer drivers into the <em class="parameter"><code>[print$]</code></em> 671 671 share of the Samba server, and a big convenience, too. Then <span class="emphasis"><em>all</em></span> clients … … 683 683 Using <span class="emphasis"><em>cupsaddsmb</em></span> (only works for the CUPS printing system, not for LPR/LPD, LPRng, and so on). 684 684 </p></li></ul></div><p> 685 <a class="indexterm" name="id39338 8"></a>686 <a class="indexterm" name="id39339 5"></a>685 <a class="indexterm" name="id393385"></a> 686 <a class="indexterm" name="id393392"></a> 687 687 Samba does not use these uploaded drivers in any way to process spooled files. These drivers are utilized 688 688 entirely by the clients who download and install them via the <span class="quote">“<span class="quote">Point'n'Print</span>”</span> mechanism … … 690 690 (or the UNIX print system) requires. Print files received by Samba are handed over to the UNIX printing 691 691 system, which is responsible for all further processing, as needed. 692 </p></div><div class="sect2" title="The Obsoleted [printer$] Section"><div class="titlepage"><div><div><h3 class="title"><a name="id3934 11"></a>The Obsoleted [printer$] Section</h3></div></div></div><p>693 <a class="indexterm" name="id39341 9"></a>694 <a class="indexterm" name="id39342 6"></a>692 </p></div><div class="sect2" title="The Obsoleted [printer$] Section"><div class="titlepage"><div><div><h3 class="title"><a name="id393408"></a>The Obsoleted [printer$] Section</h3></div></div></div><p> 693 <a class="indexterm" name="id393416"></a> 694 <a class="indexterm" name="id393423"></a> 695 695 Versions of Samba prior to 2.2 made it possible to use a share named <em class="parameter"><code>[printer$]</code></em>. This 696 696 name was taken from the same named service created by Windows 9x/Me clients when a printer was shared by them. … … 702 702 be sent to the client. 703 703 </p><p> 704 <a class="indexterm" name="id39346 5"></a>705 <a class="indexterm" name="id3934 71"></a>706 <a class="indexterm" name="id39347 8"></a>704 <a class="indexterm" name="id393462"></a> 705 <a class="indexterm" name="id393469"></a> 706 <a class="indexterm" name="id393476"></a> 707 707 These parameters, including the <em class="parameter"><code>printer driver file</code></em> parameter, 708 708 are now removed and cannot be used in installations of Samba-3. The share name … … 714 714 9x/Me clients are now thrown aside. They can use Samba's <em class="parameter"><code>[print$]</code></em> 715 715 share support just fine. 716 </p></div><div class="sect2" title="Creating the [print$] Share"><div class="titlepage"><div><div><h3 class="title"><a name="id3935 21"></a>Creating the [print$] Share</h3></div></div></div><p>717 <a class="indexterm" name="id39352 9"></a>716 </p></div><div class="sect2" title="Creating the [print$] Share"><div class="titlepage"><div><div><h3 class="title"><a name="id393519"></a>Creating the [print$] Share</h3></div></div></div><p> 717 <a class="indexterm" name="id393526"></a> 718 718 In order to support the uploading and downloading of printer driver files, you must first configure a 719 719 file share named <em class="parameter"><code>[print$]</code></em>. The public name of this share is hard coded … … 725 725 as <a class="link" href="smb.conf.5.html#PATH" target="_top">path</a>, are arbitrary and should be replaced with appropriate values for your 726 726 site). See <a class="link" href="classicalprinting.html#prtdollar" title="Example 21.3. [print$] Example">[print\$] Example</a>. 727 </p><div class="example"><a name="prtdollar"></a><p class="title"><b>Example 21.3. [print$] Example</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td># members of the ntadmin group should be able to add drivers and set</td></tr><tr><td># printer properties. root is implicitly always a 'printer admin'.</td></tr><tr><td><a class="indexterm" name="id39360 6"></a><em class="parameter"><code>printer admin = @ntadmin</code></em></td></tr><tr><td># ...</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td># ...</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id393642"></a><em class="parameter"><code>comment = Printer Driver Download Area</code></em></td></tr><tr><td><a class="indexterm" name="id393654"></a><em class="parameter"><code>path = /etc/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id393665"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id393677"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id393688"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id393700"></a><em class="parameter"><code>write list = @ntadmin, root</code></em></td></tr></table></div></div><br class="example-break"><p>727 </p><div class="example"><a name="prtdollar"></a><p class="title"><b>Example 21.3. [print$] Example</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td># members of the ntadmin group should be able to add drivers and set</td></tr><tr><td># printer properties. root is implicitly always a 'printer admin'.</td></tr><tr><td><a class="indexterm" name="id393603"></a><em class="parameter"><code>printer admin = @ntadmin</code></em></td></tr><tr><td># ...</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td># ...</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id393639"></a><em class="parameter"><code>comment = Printer Driver Download Area</code></em></td></tr><tr><td><a class="indexterm" name="id393651"></a><em class="parameter"><code>path = /etc/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id393663"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id393674"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id393686"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id393697"></a><em class="parameter"><code>write list = @ntadmin, root</code></em></td></tr></table></div></div><br class="example-break"><p> 728 728 Of course, you also need to ensure that the directory named by the 729 729 <a class="link" href="smb.conf.5.html#PATH" target="_top">path</a> parameter exists on the UNIX file system. 730 </p></div><div class="sect2" title="[print$] Stanza Parameters"><div class="titlepage"><div><div><h3 class="title"><a name="id39372 9"></a>[print$] Stanza Parameters</h3></div></div></div><p>731 <a class="indexterm" name="id39373 7"></a>732 <a class="indexterm" name="id39374 3"></a>733 <a class="indexterm" name="id3937 50"></a>734 <a class="indexterm" name="id39375 7"></a>735 <a class="indexterm" name="id39376 4"></a>730 </p></div><div class="sect2" title="[print$] Stanza Parameters"><div class="titlepage"><div><div><h3 class="title"><a name="id393726"></a>[print$] Stanza Parameters</h3></div></div></div><p> 731 <a class="indexterm" name="id393734"></a> 732 <a class="indexterm" name="id393741"></a> 733 <a class="indexterm" name="id393748"></a> 734 <a class="indexterm" name="id393754"></a> 735 <a class="indexterm" name="id393761"></a> 736 736 The <em class="parameter"><code>[print$]</code></em> is a special section in <code class="filename">smb.conf</code>. It contains settings relevant to 737 737 potential printer driver download and is used by Windows clients for local print driver installation. … … 750 750 </pre><p> 751 751 you can still mount it from any client. This can also be done from the 752 <span class="guimenu">Connect network drive menu></span>from Windows Explorer.752 <span class="guimenu">Connect network drive</span> menu from Windows Explorer. 753 753 </p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#GUESTOK" target="_top">guest ok = yes </a></span></dt><dd><p> 754 754 Gives read-only access to this share for all guest users. Access may be granted to … … 778 778 be mentioned in the global <a class="link" href="smb.conf.5.html#PRINTERADMIN" target="_top">printer admin</a> 779 779 parameter. See the <code class="filename">smb.conf</code> man page for more information on configuring file shares. 780 </p></dd></dl></div></div><div class="sect2" title="The [print$] Share Directory"><div class="titlepage"><div><div><h3 class="title"><a name="id3940 22"></a>The [print$] Share Directory</h3></div></div></div><p>780 </p></dd></dl></div></div><div class="sect2" title="The [print$] Share Directory"><div class="titlepage"><div><div><h3 class="title"><a name="id394019"></a>The [print$] Share Directory</h3></div></div></div><p> 781 781 In order for a Windows NT print server to support the downloading of driver files by multiple client 782 782 architectures, you must create several subdirectories within the <em class="parameter"><code>[print$]</code></em> … … 813 813 have located the server, navigate to its <span class="guiicon">Printers and Faxes</span> folder. You should see 814 814 an initial listing of printers that matches the printer shares defined on your Samba host. 815 </p></div></div><div class="sect1" title="Installing Drivers into [print$]"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3941 50"></a>Installing Drivers into [print$]</h2></div></div></div><p>815 </p></div></div><div class="sect1" title="Installing Drivers into [print$]"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id394148"></a>Installing Drivers into [print$]</h2></div></div></div><p> 816 816 Have you successfully created the <em class="parameter"><code>[print$]</code></em> share in <code class="filename">smb.conf</code>, and have you forced 817 817 Samba to reread its <code class="filename">smb.conf</code> file? Good. But you are not yet ready to use the new facility. The client … … 829 829 </p></li></ul></div><p> 830 830 The latter option is probably the easier one (even if the process may seem a little bit weird at first). 831 </p><div class="sect2" title="Add Printer Wizard Driver Installation"><div class="titlepage"><div><div><h3 class="title"><a name="id39423 5"></a>Add Printer Wizard Driver Installation</h3></div></div></div><p>831 </p><div class="sect2" title="Add Printer Wizard Driver Installation"><div class="titlepage"><div><div><h3 class="title"><a name="id394232"></a>Add Printer Wizard Driver Installation</h3></div></div></div><p> 832 832 The printers initially listed in the Samba host's <span class="guiicon">Printers</span> folder accessed from a 833 833 client's Explorer will have no real printer driver assigned to them. By default this driver name is set … … 880 880 </p></li></ol></div><p> 881 881 We provide detailed hints for each of these steps in the paragraphs that follow. 882 </p><div class="sect3" title="Identifying Driver Files"><div class="titlepage"><div><div><h4 class="title"><a name="id39448 7"></a>Identifying Driver Files</h4></div></div></div><p>883 <a class="indexterm" name="id39449 4"></a>884 <a class="indexterm" name="id394 501"></a>885 <a class="indexterm" name="id39450 8"></a>882 </p><div class="sect3" title="Identifying Driver Files"><div class="titlepage"><div><div><h4 class="title"><a name="id394484"></a>Identifying Driver Files</h4></div></div></div><p> 883 <a class="indexterm" name="id394492"></a> 884 <a class="indexterm" name="id394498"></a> 885 <a class="indexterm" name="id394505"></a> 886 886 To find out about the driver files, you have two options. You can check the contents of the driver 887 887 CDROM that came with your printer. Study the <code class="filename">*.inf</code> files located on the CD-ROM. This … … 891 891 extremely difficult to identify the driver files required. 892 892 </p><p> 893 <a class="indexterm" name="id39453 7"></a>893 <a class="indexterm" name="id394532"></a> 894 894 Then you have the second option. Install the driver locally on a Windows client and 895 895 investigate which filenames and paths it uses after they are installed. (You need to repeat … … 898 898 clients.) 899 899 </p><p> 900 <a class="indexterm" name="id39455 6"></a>900 <a class="indexterm" name="id394550"></a> 901 901 A good method to recognize the driver files is to print the test page from the driver's 902 902 <span class="guilabel">Properties</span> dialog (<span class="guilabel">General</span> tab). Then look at the list of … … 906 906 (this may vary slightly for Windows NT). You need to note all filenames for the next steps. 907 907 </p><p> 908 <a class="indexterm" name="id3946 10"></a>909 <a class="indexterm" name="id39461 6"></a>910 <a class="indexterm" name="id3946 23"></a>908 <a class="indexterm" name="id394604"></a> 909 <a class="indexterm" name="id394611"></a> 910 <a class="indexterm" name="id394618"></a> 911 911 Another method to quickly test the driver filenames and related paths is provided by the 912 912 <code class="literal">rpcclient</code> utility. Run it with <code class="literal">enumdrivers</code> or with the … … 949 949 Defaultdatatype: [] 950 950 </pre><p> 951 <a class="indexterm" name="id3947 31"></a>952 <a class="indexterm" name="id39473 8"></a>953 <a class="indexterm" name="id3947 45"></a>954 <a class="indexterm" name="id3947 52"></a>951 <a class="indexterm" name="id394726"></a> 952 <a class="indexterm" name="id394732"></a> 953 <a class="indexterm" name="id394739"></a> 954 <a class="indexterm" name="id394746"></a> 955 955 You may notice that this driver has quite a large number of <span class="guilabel">Dependent files</span> 956 956 (there are worse cases, however). Also, strangely, the … … 962 962 Windows PC. This PC can also host the Windows 9x/Me drivers, even if it runs on Windows NT, 2000, or XP. 963 963 </p><p> 964 <a class="indexterm" name="id394796"></a> 965 <a class="indexterm" name="id394802"></a> 966 <a class="indexterm" name="id394809"></a> 964 <a class="indexterm" name="id394790"></a> 965 <a class="indexterm" name="id394797"></a> 967 966 Since the <em class="parameter"><code>[print$]</code></em> share is usually accessible through the <span class="guiicon">Network 968 967 Neighborhood</span>, you can also use the UNC notation from Windows Explorer to poke at it. The Windows … … 975 974 the Admin), its native mode for printer drivers is user mode execution. This requires drivers designed 976 975 for this purpose. These types of drivers install into the <span class="quote">“<span class="quote">3</span>”</span> subdirectory. 977 </p></div></div><div class="sect3" title="Obtaining Driver Files from Windows Client [print$] Shares"><div class="titlepage"><div><div><h4 class="title"><a name="id3948 66"></a>Obtaining Driver Files from Windows Client [print$] Shares</h4></div></div></div><p>976 </p></div></div><div class="sect3" title="Obtaining Driver Files from Windows Client [print$] Shares"><div class="titlepage"><div><div><h4 class="title"><a name="id394855"></a>Obtaining Driver Files from Windows Client [print$] Shares</h4></div></div></div><p> 978 977 Now we need to collect all the driver files we identified in our previous step. Where do we get them 979 978 from? Well, why not retrieve them from the very PC and the same <em class="parameter"><code>[print$]</code></em> … … 1000 999 <code class="literal">smbclient</code> exits again. 1001 1000 </p><p> 1002 <a class="indexterm" name="id3949 64"></a>1001 <a class="indexterm" name="id394953"></a> 1003 1002 Remember to repeat the procedure for the <span class="application">WIN40</span> architecture should you need to 1004 1003 support Windows 9x/Me/XP clients. Remember too, the files for these architectures are in the 1005 1004 <code class="filename">WIN40/0/</code> subdirectory. Once this is complete, we can run <code class="literal">smbclient. . 1006 1005 .put</code> to store the collected files on the Samba server's <em class="parameter"><code>[print$]</code></em> share. 1007 </p></div><div class="sect3" title="Installing Driver Files into [print$]"><div class="titlepage"><div><div><h4 class="title"><a name="id3949 99"></a>Installing Driver Files into [print$]</h4></div></div></div><p>1006 </p></div><div class="sect3" title="Installing Driver Files into [print$]"><div class="titlepage"><div><div><h4 class="title"><a name="id394988"></a>Installing Driver Files into [print$]</h4></div></div></div><p> 1008 1007 We are now going to locate the driver files into the <em class="parameter"><code>[print$]</code></em> share. Remember, the 1009 1008 UNIX path to this share has been defined previously in your <code class="filename">smb.conf</code> file. You also have created … … 1018 1017 (yet) into the <code class="filename">0</code> subdirectory. 1019 1018 </p></li></ul></div><p> 1020 <a class="indexterm" name="id3950 73"></a>1021 <a class="indexterm" name="id3950 80"></a>1019 <a class="indexterm" name="id395062"></a> 1020 <a class="indexterm" name="id395069"></a> 1022 1021 We again use smbclient to transfer the driver files across the network. We specify the same files 1023 1022 and paths as were leaked to us by running <code class="literal">getdriver</code> against the original … … 1056 1055 putting file HDNIS01_de.NTF as \W32X86\HDNIS01_de.NTF 1057 1056 </pre><p> 1058 <a class="indexterm" name="id3951 46"></a>1059 <a class="indexterm" name="id3951 53"></a>1060 <a class="indexterm" name="id3951 60"></a>1057 <a class="indexterm" name="id395126"></a> 1058 <a class="indexterm" name="id395133"></a> 1059 <a class="indexterm" name="id395140"></a> 1061 1060 Whew that was a lot of typing! Most drivers are a lot smaller many have only three generic 1062 1061 PostScript driver files plus one PPD. While we did retrieve the files from the <code class="filename">2</code> … … 1065 1064 <code class="literal">adddriver</code> command, which we will run shortly (and do not forget to also put the files 1066 1065 for the Windows 9x/Me architecture into the <code class="filename">WIN40/</code> subdirectory should you need them). 1067 </p></div><div class="sect3" title="smbclient to Confirm Driver Installation"><div class="titlepage"><div><div><h4 class="title"><a name="id395 202"></a><code class="literal">smbclient</code> to Confirm Driver Installation</h4></div></div></div><p>1068 <a class="indexterm" name="id395 214"></a>1069 <a class="indexterm" name="id3952 21"></a>1066 </p></div><div class="sect3" title="smbclient to Confirm Driver Installation"><div class="titlepage"><div><div><h4 class="title"><a name="id395182"></a><code class="literal">smbclient</code> to Confirm Driver Installation</h4></div></div></div><p> 1067 <a class="indexterm" name="id395194"></a> 1068 <a class="indexterm" name="id395201"></a> 1070 1069 For now we verify that our files are there. This can be done with <code class="literal">smbclient</code>, too 1071 1070 (but, of course, you can log in via SSH also and do this through a standard UNIX shell access): … … 1108 1107 40976 blocks of size 262144. 709 blocks available 1109 1108 </pre><p> 1110 <a class="indexterm" name="id3952 75"></a>1111 <a class="indexterm" name="id3952 82"></a>1112 <a class="indexterm" name="id3952 88"></a>1109 <a class="indexterm" name="id395255"></a> 1110 <a class="indexterm" name="id395261"></a> 1111 <a class="indexterm" name="id395268"></a> 1113 1112 Notice that there are already driver files present in the <code class="filename">2</code> subdirectory (probably from a 1114 1113 previous installation). Once the files for the new driver are there too, you are still a few steps away from … … 1118 1117 special, namely <span class="emphasis"><em>printer driver files</em></span>, and it does not know to which print queue(s) these 1119 1118 driver files belong. 1120 </p></div><div class="sect3" title="Running rpcclient with adddriver"><div class="titlepage"><div><div><h4 class="title"><a name="id395 312"></a>Running <code class="literal">rpcclient</code> with <code class="literal">adddriver</code></h4></div></div></div><p>1121 <a class="indexterm" name="id3953 30"></a>1122 <a class="indexterm" name="id3953 37"></a>1123 <a class="indexterm" name="id3953 44"></a>1119 </p></div><div class="sect3" title="Running rpcclient with adddriver"><div class="titlepage"><div><div><h4 class="title"><a name="id395292"></a>Running <code class="literal">rpcclient</code> with <code class="literal">adddriver</code></h4></div></div></div><p> 1120 <a class="indexterm" name="id395310"></a> 1121 <a class="indexterm" name="id395317"></a> 1122 <a class="indexterm" name="id395324"></a> 1124 1123 Next, you must tell Samba about the special category of the files you just uploaded into the 1125 1124 <em class="parameter"><code>[print$]</code></em> share. This is done by the <code class="literal">adddriver</code> … … 1145 1144 Printer Driver dm9110 successfully installed. 1146 1145 </pre><p> 1147 <a class="indexterm" name="id3953 90"></a>1148 <a class="indexterm" name="id3953 96"></a>1149 <a class="indexterm" name="id395 403"></a>1146 <a class="indexterm" name="id395369"></a> 1147 <a class="indexterm" name="id395376"></a> 1148 <a class="indexterm" name="id395383"></a> 1150 1149 After this step, the driver should be recognized by Samba on the print server. You need to be very 1151 1150 careful when typing the command. Don't exchange the order of the fields. Some changes would lead to … … 1154 1153 Hints about the syntax of the adddriver command are in the man page. 1155 1154 provides a more detailed description, should you need it. 1156 </p></div><div class="sect3" title="Checking adddriver Completion"><div class="titlepage"><div><div><h4 class="title"><a name="id3954 22"></a>Checking <code class="literal">adddriver</code> Completion</h4></div></div></div><p>1155 </p></div><div class="sect3" title="Checking adddriver Completion"><div class="titlepage"><div><div><h4 class="title"><a name="id395402"></a>Checking <code class="literal">adddriver</code> Completion</h4></div></div></div><p> 1157 1156 One indication for Samba's recognition of the files as driver files is the <code class="computeroutput">successfully 1158 1157 installed</code> message. Another one is the fact that our files have been moved by the … … 1199 1198 Another verification is that the timestamp of the printing TDB files is now updated 1200 1199 (and possibly their file size has increased). 1201 </p></div><div class="sect3" title="Check Samba for Driver Recognition"><div class="titlepage"><div><div><h4 class="title"><a name="id395 502"></a>Check Samba for Driver Recognition</h4></div></div></div><p>1202 <a class="indexterm" name="id395 510"></a>1200 </p></div><div class="sect3" title="Check Samba for Driver Recognition"><div class="titlepage"><div><div><h4 class="title"><a name="id395482"></a>Check Samba for Driver Recognition</h4></div></div></div><p> 1201 <a class="indexterm" name="id395490"></a> 1203 1202 Now the driver should be registered with Samba. We can easily verify this and will do so in a 1204 1203 moment. However, this driver is not yet associated with a particular printer. We may check the driver 1205 1204 status of the files by at least three methods: 1206 1205 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> 1207 <a class="indexterm" name="id395525"></a> 1206 <a class="indexterm" name="id395505"></a> 1207 <a class="indexterm" name="id395512"></a> 1208 <a class="indexterm" name="id395519"></a> 1209 <a class="indexterm" name="id395526"></a> 1208 1210 <a class="indexterm" name="id395532"></a> 1209 <a class="indexterm" name="id395539"></a>1210 <a class="indexterm" name="id395546"></a>1211 <a class="indexterm" name="id395553"></a>1212 1211 From any Windows client browse Network Neighborhood, find the Samba host, and open the Samba 1213 1212 <span class="guiicon">Printers and Faxes</span> folder. Select any printer icon, right-click and select … … 1219 1218 the list will differ if you look at it from Windows95/98/ME or Windows NT/2000/XP.) 1220 1219 </p></li><li class="listitem"><p> 1221 <a class="indexterm" name="id3955 91"></a>1220 <a class="indexterm" name="id395566"></a> 1222 1221 From a Windows 200x/XP client (not Windows NT) browse <span class="guiicon">Network Neighborhood</span>, 1223 1222 search for the Samba server, open the server's <span class="guiicon">Printers</span> folder, … … 1248 1247 95, 98, and Me</span>, you'll have to repeat the whole procedure with the WIN40 architecture 1249 1248 and subdirectory. 1250 </p></li></ul></div></div><div class="sect3" title="Specific Driver Name Flexibility"><div class="titlepage"><div><div><h4 class="title"><a name="id395 712"></a>Specific Driver Name Flexibility</h4></div></div></div><p>1251 <a class="indexterm" name="id395 720"></a>1249 </p></li></ul></div></div><div class="sect3" title="Specific Driver Name Flexibility"><div class="titlepage"><div><div><h4 class="title"><a name="id395688"></a>Specific Driver Name Flexibility</h4></div></div></div><p> 1250 <a class="indexterm" name="id395696"></a> 1252 1251 You can name the driver as you like. If you repeat the <code class="literal">adddriver</code> step with the same 1253 1252 files as before but with a different driver name, it will work the same: … … 1272 1271 Printer Driver mydrivername successfully installed. 1273 1272 </pre><p> 1274 <a class="indexterm" name="id3957 59"></a>1275 <a class="indexterm" name="id3957 66"></a>1276 <a class="indexterm" name="id3957 72"></a>1273 <a class="indexterm" name="id395735"></a> 1274 <a class="indexterm" name="id395742"></a> 1275 <a class="indexterm" name="id395748"></a> 1277 1276 You will be able to bind that driver to any print queue (however, you are responsible that 1278 1277 you associate drivers to queues that make sense with respect to target printers). You cannot run the … … 1281 1280 respective subdirectories, so you must execute an <code class="literal">smbclient ... put</code> command before 1282 1281 each <code class="literal">rpcclient ... adddriver</code> command. 1283 </p></div><div class="sect3" title="Running rpcclient with setdriver"><div class="titlepage"><div><div><h4 class="title"><a name="id395 814"></a>Running <code class="literal">rpcclient</code> with <code class="literal">setdriver</code></h4></div></div></div><p>1284 <a class="indexterm" name="id3958 32"></a>1285 <a class="indexterm" name="id3958 39"></a>1282 </p></div><div class="sect3" title="Running rpcclient with setdriver"><div class="titlepage"><div><div><h4 class="title"><a name="id395790"></a>Running <code class="literal">rpcclient</code> with <code class="literal">setdriver</code></h4></div></div></div><p> 1283 <a class="indexterm" name="id395808"></a> 1284 <a class="indexterm" name="id395815"></a> 1286 1285 Samba needs to know which printer owns which driver. Create a mapping of the driver to a printer, and 1287 1286 store this information in Samba's memory, the TDB files. The <code class="literal">rpcclient setdriver</code> command … … 1310 1309 or at least send an HUP signal to all running smbd processes to work around this: <strong class="userinput"><code>kill -HUP 1311 1310 `pidof smbd`</code></strong>. 1312 </p></div></div></div></div><div class="sect1" title="Client Driver Installation Procedure"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3959 45"></a>Client Driver Installation Procedure</h2></div></div></div><p>1311 </p></div></div></div></div><div class="sect1" title="Client Driver Installation Procedure"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id395921"></a>Client Driver Installation Procedure</h2></div></div></div><p> 1313 1312 As Don Quixote said, <span class="quote">“<span class="quote">The proof of the pudding is in the eating.</span>”</span> The proof 1314 1313 for our setup lies in the printing. So let's install the printer driver onto the client PCs. This is 1315 1314 not as straightforward as it may seem. Read on. 1316 </p><div class="sect2" title="First Client Driver Installation"><div class="titlepage"><div><div><h3 class="title"><a name="id3959 60"></a>First Client Driver Installation</h3></div></div></div><p>1315 </p><div class="sect2" title="First Client Driver Installation"><div class="titlepage"><div><div><h3 class="title"><a name="id395936"></a>First Client Driver Installation</h3></div></div></div><p> 1317 1316 Especially important is the installation onto the first client PC (for each architectural platform 1318 1317 separately). Once this is done correctly, all further clients are easy to set up and shouldn't need further … … 1348 1347 and Faxes</span>). 1349 1348 </p><p> 1350 <a class="indexterm" name="id396 120"></a>1349 <a class="indexterm" name="id396093"></a> 1351 1350 Most likely you are tempted to try to print a test page. After all, you now can open the printer 1352 1351 properties, and on the <span class="guimenu">General</span> tab there is a button offering to do just that. But … … 1360 1359 For a printer to be truly usable by a Windows NT/200x/XP client, it must possess: 1361 1360 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> 1362 <a class="indexterm" name="id3961 76"></a>1361 <a class="indexterm" name="id396148"></a> 1363 1362 A valid <span class="emphasis"><em>device mode</em></span> generated by the driver for the printer (defining things 1364 1363 like paper size, orientation and duplex settings). 1365 1364 </p></li><li class="listitem"><p> 1366 <a class="indexterm" name="id3961 92"></a>1365 <a class="indexterm" name="id396164"></a> 1367 1366 A complete set of <span class="emphasis"><em>printer driver data</em></span> generated by the driver. 1368 1367 </p></li></ul></div><p> 1369 <a class="indexterm" name="id396 207"></a>1370 <a class="indexterm" name="id396 214"></a>1371 <a class="indexterm" name="id396 220"></a>1372 <a class="indexterm" name="id396 227"></a>1373 <a class="indexterm" name="id3962 34"></a>1368 <a class="indexterm" name="id396179"></a> 1369 <a class="indexterm" name="id396186"></a> 1370 <a class="indexterm" name="id396193"></a> 1371 <a class="indexterm" name="id396199"></a> 1372 <a class="indexterm" name="id396206"></a> 1374 1373 If either of these is incomplete, the clients can produce less than optimal output at best. In the 1375 1374 worst cases, unreadable garbage or nothing at all comes from the printer, or it produces a harvest of … … 1397 1396 effect to happen and feeds back the new device mode to our Samba server. You can use the native Windows 1398 1397 NT/200x/XP printer properties page from a Window client for this: 1399 </p><div class="procedure" title="Procedure 21.1. Procedure to Initialize the Printer Driver Settings"><a name="id396 308"></a><p class="title"><b>Procedure 21.1. Procedure to Initialize the Printer Driver Settings</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p>1398 </p><div class="procedure" title="Procedure 21.1. Procedure to Initialize the Printer Driver Settings"><a name="id396280"></a><p class="title"><b>Procedure 21.1. Procedure to Initialize the Printer Driver Settings</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> 1400 1399 Browse the <span class="guiicon">Network Neighborhood</span>. 1401 1400 </p></li><li class="step" title="Step 2"><p> … … 1427 1426 folder, too, if you are a Samba printer admin user. From now on, printing should work as expected. 1428 1427 </p><p> 1429 <a class="indexterm" name="id3964 52"></a>1428 <a class="indexterm" name="id396424"></a> 1430 1429 Samba includes a service-level parameter name <em class="parameter"><code>default devmode</code></em> for generating a default 1431 1430 device mode for a printer. Some drivers function well with Samba's default set of properties. Others 1432 1431 may crash the client's spooler service. So use this parameter with caution. It is always better to have 1433 1432 the client generate a valid device mode for the printer and store it on the server for you. 1434 </p></div><div class="sect2" title="Additional Client Driver Installation"><div class="titlepage"><div><div><h3 class="title"><a name="id3964 70"></a>Additional Client Driver Installation</h3></div></div></div><p>1435 <a class="indexterm" name="id3964 78"></a>1433 </p></div><div class="sect2" title="Additional Client Driver Installation"><div class="titlepage"><div><div><h3 class="title"><a name="id396442"></a>Additional Client Driver Installation</h3></div></div></div><p> 1434 <a class="indexterm" name="id396450"></a> 1436 1435 Every additional driver may be installed in the same way as just described. Browse <code class="literal">Network 1437 1436 Neighborhood</code>, open the <span class="guiicon">Printers</span> folder on Samba server, right-click on … … 1446 1445 </pre><p> 1447 1446 or this command on Windows NT 4.0 workstations: 1448 <a class="indexterm" name="id3965 39"></a>1447 <a class="indexterm" name="id396511"></a> 1449 1448 </p><pre class="screen"> 1450 1449 <strong class="userinput"><code>rundll32 shell32.dll,Control_RunDLL MAIN.CPL @2</code></strong> … … 1453 1452 You can enter the commands either inside a <span class="guilabel">DOS box</span> window or in the <span class="guimenuitem">Run 1454 1453 command...</span> field from the <span class="guimenu">Start</span> menu. 1455 </p></div><div class="sect2" title="Always Make First Client Connection as root or “printer admin”"><div class="titlepage"><div><div><h3 class="title"><a name="id3965 81"></a>Always Make First Client Connection as root or <span class="quote">“<span class="quote">printer admin</span>”</span></h3></div></div></div><p>1454 </p></div><div class="sect2" title="Always Make First Client Connection as root or “printer admin”"><div class="titlepage"><div><div><h3 class="title"><a name="id396553"></a>Always Make First Client Connection as root or <span class="quote">“<span class="quote">printer admin</span>”</span></h3></div></div></div><p> 1456 1455 After you installed the driver on the Samba server (in its <em class="parameter"><code>[print$]</code></em> share), you 1457 1456 should always make sure that your first client installation completes correctly. Make it a habit for yourself … … 1468 1467 printer for <span class="guiicon">duplex</span> as the default, and so on). 1469 1468 </p><p> 1470 <a class="indexterm" name="id3966 69"></a>1469 <a class="indexterm" name="id396641"></a> 1471 1470 To connect as root to a Samba printer, try this command from a Windows 200x/XP DOS box command prompt: 1472 1471 </p><pre class="screen"> … … 1482 1481 <code class="literal">Point'n'Print</code>) will have the same defaults set for them. If you miss this step, you'll get a 1483 1482 lot of help desk calls from your users, but maybe you like to talk to people. 1484 </p></div></div><div class="sect1" title="Other Gotchas"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3967 39"></a>Other Gotchas</h2></div></div></div><p>1483 </p></div></div><div class="sect1" title="Other Gotchas"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id396711"></a>Other Gotchas</h2></div></div></div><p> 1485 1484 Your driver is installed. It is now ready for Point'n'Print installation by the clients. You may have tried to 1486 1485 download and use it on your first client machine, but wait. Let's make sure you are acquainted first with a … … 1488 1487 advised in the preceding paragraphs. Your users complain about various issues (such as, <span class="quote">“<span class="quote">We need to set 1489 1488 the paper size for each job from Letter to A4 and it will not store it</span>”</span>). 1490 </p><div class="sect2" title="Setting Default Print Options for Client Drivers"><div class="titlepage"><div><div><h3 class="title"><a name="id3967 56"></a>Setting Default Print Options for Client Drivers</h3></div></div></div><p>1489 </p><div class="sect2" title="Setting Default Print Options for Client Drivers"><div class="titlepage"><div><div><h3 class="title"><a name="id396728"></a>Setting Default Print Options for Client Drivers</h3></div></div></div><p> 1491 1490 The last sentence might be viewed with mixed feelings by some users and Admins. They have struggled for hours 1492 1491 and could not arrive at a point where their settings seemed to be saved. It is not their fault. The confusing … … 1537 1536 defaults for all users. 1538 1537 </p><div class="tip" title="Tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>Try (on Windows 200x/XP) to run this command (as a user with the right privileges): 1539 <a class="indexterm" name="id39 7022"></a>1538 <a class="indexterm" name="id396994"></a> 1540 1539 </p><p><strong class="userinput"><code> 1541 1540 rundll32 printui.dll,PrintUIEntry /p /t3 /n\\<em class="replaceable"><code>SAMBA-SERVER</code></em>\<em class="replaceable"><code>printersharename</code></em> … … 1548 1547 button (the one that does not set systemwide defaults), you can 1549 1548 start the commands from inside a DOS box or from <span class="guimenu">Start</span> -> <span class="guimenuitem">Run</span>. 1550 </p></div></div><div class="sect2" title="Supporting Large Numbers of Printers"><div class="titlepage"><div><div><h3 class="title"><a name="id3970 92"></a>Supporting Large Numbers of Printers</h3></div></div></div><p>1549 </p></div></div><div class="sect2" title="Supporting Large Numbers of Printers"><div class="titlepage"><div><div><h3 class="title"><a name="id397064"></a>Supporting Large Numbers of Printers</h3></div></div></div><p> 1551 1550 One issue that has arisen during the recent development phase of Samba is the need to support driver 1552 1551 downloads for hundreds of printers. Using Windows NT APW for this task is somewhat awkward (to say the least). If … … 1631 1630 the two commas in the description field). After the <code class="literal">setdriver</code> command 1632 1631 succeeds, all is well. 1633 </p></div><div class="sect2" title="Adding New Printers with the Windows NT APW"><div class="titlepage"><div><div><h3 class="title"><a name="id3973 28"></a>Adding New Printers with the Windows NT APW</h3></div></div></div><p>1632 </p></div><div class="sect2" title="Adding New Printers with the Windows NT APW"><div class="titlepage"><div><div><h3 class="title"><a name="id397300"></a>Adding New Printers with the Windows NT APW</h3></div></div></div><p> 1634 1633 By default, Samba exhibits all printer shares defined in <code class="filename">smb.conf</code> in the <span class="guiicon">Printers</span> 1635 1634 folder. Also located in this folder is the Windows NT Add Printer Wizard icon. The APW will be shown only if: … … 1671 1670 you unwittingly under the wrong privilege. You should check it by using the <code class="literal">smbstatus</code> 1672 1671 command. 1673 </p></div><div class="sect2" title="Error Message: “Cannot connect under a different Name”"><div class="titlepage"><div><div><h3 class="title"><a name="id3975 65"></a>Error Message: <span class="quote">“<span class="quote">Cannot connect under a different Name</span>”</span></h3></div></div></div><p>1672 </p></div><div class="sect2" title="Error Message: “Cannot connect under a different Name”"><div class="titlepage"><div><div><h3 class="title"><a name="id397538"></a>Error Message: <span class="quote">“<span class="quote">Cannot connect under a different Name</span>”</span></h3></div></div></div><p> 1674 1673 Once you are connected with the wrong credentials, there is no means to reverse the situation other than 1675 1674 to close all Explorer windows, and perhaps reboot. 1676 1675 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> 1677 <a class="indexterm" name="id3975 84"></a>1676 <a class="indexterm" name="id397556"></a> 1678 1677 The <code class="literal">net use \\SAMBA-SERVER\sharename /user:root</code> gives you an error message: 1679 1678 <span class="quote">“<span class="quote">Multiple connections to a server or a shared resource by the same user utilizing … … 1701 1700 </pre><p> 1702 1701 This will also disconnect all mapped drives and will allow you create fresh connection as required. 1703 </p></div><div class="sect2" title="Take Care When Assembling Driver Files"><div class="titlepage"><div><div><h3 class="title"><a name="id3976 64"></a>Take Care When Assembling Driver Files</h3></div></div></div><p>1702 </p></div><div class="sect2" title="Take Care When Assembling Driver Files"><div class="titlepage"><div><div><h3 class="title"><a name="id397636"></a>Take Care When Assembling Driver Files</h3></div></div></div><p> 1704 1703 You need to be extremely careful when you take notes about the files belonging to a particular 1705 1704 driver. Don't confuse the files for driver version <span class="quote">“<span class="quote">0</span>”</span> (for Windows 9x/Me, going into … … 1832 1831 correct driver files for each driver version. Don't rely on the names alone, and don't interchange files 1833 1832 belonging to different driver versions. 1834 </p></div><div class="sect2" title="Samba and Printer Ports"><div class="titlepage"><div><div><h3 class="title"><a name="id39786 4"></a>Samba and Printer Ports</h3></div></div></div><p>1835 <a class="indexterm" name="id3978 71"></a>1836 <a class="indexterm" name="id39787 8"></a>1837 <a class="indexterm" name="id39788 5"></a>1838 <a class="indexterm" name="id3978 92"></a>1833 </p></div><div class="sect2" title="Samba and Printer Ports"><div class="titlepage"><div><div><h3 class="title"><a name="id397860"></a>Samba and Printer Ports</h3></div></div></div><p> 1834 <a class="indexterm" name="id397868"></a> 1835 <a class="indexterm" name="id397874"></a> 1836 <a class="indexterm" name="id397881"></a> 1837 <a class="indexterm" name="id397888"></a> 1839 1838 Windows NT/2000 print servers associate a port with each printer. These normally take the form of 1840 1839 <code class="filename">LPT1:</code>, <code class="filename">COM1:</code>, <code class="filename">FILE:</code>, and so on. Samba must also … … 1845 1844 information to keep the Windows clients happy. 1846 1845 </p><p> 1847 <a class="indexterm" name="id3979 31"></a>1846 <a class="indexterm" name="id397927"></a> 1848 1847 Samba does not support the concept of <code class="constant">Printer Pooling</code> internally either. Printer 1849 1848 pooling assigns a logical printer to multiple ports as a form of load balancing or failover. … … 1852 1851 that they are working with Samba), configure the <a class="link" href="smb.conf.5.html#ENUMPORTSCOMMAND" target="_top">enumports command</a>, 1853 1852 which can be used to define an external program that generates a listing of ports on a system. 1854 </p></div><div class="sect2" title="Avoiding Common Client Driver Misconfiguration"><div class="titlepage"><div><div><h3 class="title"><a name="id3979 63"></a>Avoiding Common Client Driver Misconfiguration</h3></div></div></div><p>1853 </p></div><div class="sect2" title="Avoiding Common Client Driver Misconfiguration"><div class="titlepage"><div><div><h3 class="title"><a name="id397959"></a>Avoiding Common Client Driver Misconfiguration</h3></div></div></div><p> 1855 1854 So now the printing works, but there are still problems. Most jobs print well, some do not print at 1856 1855 all. Some jobs have problems with fonts, which do not look good. Some jobs print fast and some … … 1859 1858 Chapter</a>, <a class="link" href="CUPS-printing.html#cups-avoidps1" title="Avoiding Critical PostScript Driver Settings on the Client">Avoiding Critical PostScript Driver Settings on the 1860 1859 Client</a>. 1861 </p></div></div><div class="sect1" title="The Imprints Toolset"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id39799 6"></a>The Imprints Toolset</h2></div></div></div><p>1862 <a class="indexterm" name="id39 8003"></a>1860 </p></div></div><div class="sect1" title="The Imprints Toolset"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id397992"></a>The Imprints Toolset</h2></div></div></div><p> 1861 <a class="indexterm" name="id397999"></a> 1863 1862 The Imprints tool set provides a UNIX equivalent of the Windows NT APW. For complete information, please 1864 1863 refer to the <a class="ulink" href="http://imprints.sourceforge.net/" target="_top">Imprints</a> Web site as well as the … … 1872 1871 there are prepared packages to use. Packages for more up-to-date print devices are needed if Imprints 1873 1872 should have a future. Information regarding the Imprints toolset can be obtained from the <a class="ulink" href="http://imprints.sourceforge.net/" target="_top">Imprints</a> home page. 1874 </p><div class="sect2" title="What Is Imprints?"><div class="titlepage"><div><div><h3 class="title"><a name="id39803 4"></a>What Is Imprints?</h3></div></div></div><p>1873 </p><div class="sect2" title="What Is Imprints?"><div class="titlepage"><div><div><h3 class="title"><a name="id398030"></a>What Is Imprints?</h3></div></div></div><p> 1875 1874 Imprints is a collection of tools for supporting these goals: 1876 1875 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> … … 1881 1880 Providing an installation client that will obtain printer drivers from a central Internet (or intranet) Imprints Server 1882 1881 repository and install them on remote Samba and Windows NT4 print servers. 1883 </p></li></ul></div></div><div class="sect2" title="Creating Printer Driver Packages"><div class="titlepage"><div><div><h3 class="title"><a name="id39806 3"></a>Creating Printer Driver Packages</h3></div></div></div><p>1882 </p></li></ul></div></div><div class="sect2" title="Creating Printer Driver Packages"><div class="titlepage"><div><div><h3 class="title"><a name="id398060"></a>Creating Printer Driver Packages</h3></div></div></div><p> 1884 1883 The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt, 1885 1884 included with the Samba distribution for more information). In short, an Imprints driver package 1886 1885 is a gzipped tarball containing the driver files, related INF files, and a control file needed by the 1887 1886 installation client. 1888 </p></div><div class="sect2" title="The Imprints Server"><div class="titlepage"><div><div><h3 class="title"><a name="id39807 6"></a>The Imprints Server</h3></div></div></div><p>1887 </p></div><div class="sect2" title="The Imprints Server"><div class="titlepage"><div><div><h3 class="title"><a name="id398072"></a>The Imprints Server</h3></div></div></div><p> 1889 1888 The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each 1890 1889 printer entry in the database has an associated URL for the actual downloading of the package. Each … … 1893 1892 the one referred in the Imprints database. It is strongly recommended that this security check 1894 1893 not be disabled. 1895 </p></div><div class="sect2" title="The Installation Client"><div class="titlepage"><div><div><h3 class="title"><a name="id3980 90"></a>The Installation Client</h3></div></div></div><p>1894 </p></div><div class="sect2" title="The Installation Client"><div class="titlepage"><div><div><h3 class="title"><a name="id398086"></a>The Installation Client</h3></div></div></div><p> 1896 1895 More information regarding the Imprints installation client is available from the documentation file 1897 1896 <code class="filename">Imprints-Client-HOWTO.ps</code> that is included with the Imprints source package. The Imprints … … 1923 1922 The way of sidestepping this limitation is to require that all Imprints printer driver packages include both the Intel Windows NT and 1924 1923 95/98 printer drivers and that the NT driver is installed first. 1925 </p></div></div><div class="sect1" title="Adding Network Printers without User Interaction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id39820 6"></a>Adding Network Printers without User Interaction</h2></div></div></div><p>1924 </p></div></div><div class="sect1" title="Adding Network Printers without User Interaction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id398202"></a>Adding Network Printers without User Interaction</h2></div></div></div><p> 1926 1925 The following MS Knowledge Base article may be of some help if you need to handle Windows 2000 clients: 1927 1926 <span class="emphasis"><em>How to Add Printers with No User Interaction in Windows 2000,</em></span> (<a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;189105" target="_top">Microsoft KB 189105</a>). It also … … 1982 1981 added, changed, and deleted at will on the server with no user intervention required from the clients 1983 1982 (you just need to keep the logon scripts up to date). 1984 </p></div><div class="sect1" title="The addprinter Command"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id39844 8"></a>The <code class="literal">addprinter</code> Command</h2></div></div></div><p>1983 </p></div><div class="sect1" title="The addprinter Command"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id398444"></a>The <code class="literal">addprinter</code> Command</h2></div></div></div><p> 1985 1984 The <code class="literal">addprinter</code> command can be configured to be a shell script or program executed by 1986 1985 Samba. It is triggered by running the APW from a client against the Samba print server. The APW asks … … 1990 1989 by executing the <code class="literal">lpadmin</code> command on more modern systems) and create the associated share, 1991 1990 then the APW will in effect really create a new printer on Samba and the UNIX print subsystem! 1992 </p></div><div class="sect1" title="Migration of Classical Printing to Samba"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3984 81"></a>Migration of Classical Printing to Samba</h2></div></div></div><p>1991 </p></div><div class="sect1" title="Migration of Classical Printing to Samba"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id398477"></a>Migration of Classical Printing to Samba</h2></div></div></div><p> 1993 1992 The basic NT-style printer driver management has not changed considerably in 3.0 over the 2.2.x releases 1994 1993 (apart from many small improvements). Here migration should be quite easy, especially if you followed … … 2020 2019 using smbclient and rpcclient. See the Imprints installation client on the <a class="ulink" href="http://imprints.sourceforge.net/" target="_top">Imprints</a> web site for example. See also the discussion of 2021 2020 rpcclient usage in <a class="link" href="CUPS-printing.html" title="Chapter 22. CUPS Printing Support">CUPS Printing</a>. 2022 </p></li></ul></div></div><div class="sect1" title="Publishing Printer Information in Active Directory or LDAP"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3986 12"></a>Publishing Printer Information in Active Directory or LDAP</h2></div></div></div><p>2021 </p></li></ul></div></div><div class="sect1" title="Publishing Printer Information in Active Directory or LDAP"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id398608"></a>Publishing Printer Information in Active Directory or LDAP</h2></div></div></div><p> 2023 2022 This topic has also been addressed in <a class="link" href="NetCommand.html" title="Chapter 13. Remote and Local Management: The Net Command">Remote and Local Management The 2024 2023 Net Command</a>. If you wish to volunteer your services to help document this further, please contact 2025 2024 <a class="ulink" href="mail://jht@samba.org" target="_top">John H. Terpstra</a>. 2026 </p></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id39863 9"></a>Common Errors</h2></div></div></div><div class="sect2" title="I Give My Root Password but I Do Not Get Access"><div class="titlepage"><div><div><h3 class="title"><a name="id398644"></a>I Give My Root Password but I Do Not Get Access</h3></div></div></div><p>2025 </p></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id398635"></a>Common Errors</h2></div></div></div><div class="sect2" title="I Give My Root Password but I Do Not Get Access"><div class="titlepage"><div><div><h3 class="title"><a name="id398641"></a>I Give My Root Password but I Do Not Get Access</h3></div></div></div><p> 2027 2026 Do not confuse the root password, which is valid for the UNIX system (and in most cases stored in the 2028 2027 form of a one-way hash in a file named <code class="filename">/etc/shadow</code>), with the password used to … … 2035 2034 Retype new SMB password: secret 2036 2035 </pre><p> 2037 </p></div><div class="sect2" title="My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost"><div class="titlepage"><div><div><h3 class="title"><a name="id3986 82"></a>My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</h3></div></div></div><p>2036 </p></div><div class="sect2" title="My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost"><div class="titlepage"><div><div><h3 class="title"><a name="id398678"></a>My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</h3></div></div></div><p> 2038 2037 Do not use the existing UNIX print system spool directory for the Samba spool directory. It may seem 2039 2038 convenient and a savings of space, but it only leads to problems. The two must be separate. The UNIX/Linux
Note:
See TracChangeset
for help on using the changeset viewer.
