/[gentoo]/xml/htdocs/doc/en/quick-samba-howto.xml
Gentoo

Diff of /xml/htdocs/doc/en/quick-samba-howto.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.28 Revision 1.32
1<?xml version='1.0' encoding='UTF-8'?> 1<?xml version='1.0' encoding='UTF-8'?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.28 2007/06/06 22:42:25 nightmorph Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.32 2007/07/29 22:14:39 nightmorph Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4<guide link="/doc/en/quick-samba-howto.xml"> 4<guide link="/doc/en/quick-samba-howto.xml">
5<title>Gentoo Samba3/CUPS/ClamAV HOWTO</title> 5<title>Gentoo Samba3/CUPS/ClamAV HOWTO</title>
6<author title="Author"> 6<author title="Author">
7 <mail link="daff at dword dot org">Andreas "daff" Ntaflos</mail> 7 <mail link="daff at dword dot org">Andreas "daff" Ntaflos</mail>
8</author> 8</author>
9<author title="Author"> 9<author title="Author">
10 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail> 10 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail>
11</author> 11</author>
12<author title="Editor">
13 <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
14</author>
12 15
13<abstract> 16<abstract>
14Setup, install and configure a Samba Server under Gentoo that shares 17Setup, install and configure a Samba Server under Gentoo that shares files,
15files, printers without the need to install drivers and provides 18printers without the need to install drivers and provides automatic virus
16automatic virus scanning. 19scanning.
17</abstract> 20</abstract>
18 21
19<!-- The content of this document is licensed under the CC-BY-SA license --> 22<!-- The content of this document is licensed under the CC-BY-SA license -->
20<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 23<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
21<license/> 24<license/>
22 25
23<version>1.17</version> 26<version>1.20</version>
24<date>2007-06-06</date> 27<date>2007-07-29</date>
25 28
26<chapter> 29<chapter>
27<title>Introduction to this HOWTO</title> 30<title>Introduction to this HOWTO</title>
28<section> 31<section>
29<title>Purpose</title> 32<title>Purpose</title>
30<body> 33<body>
31 34
32<p> 35<p>
33This HOWTO is designed to help you move a network from many different 36This HOWTO is designed to help you move a network from many different clients
34clients speaking different languages, to many different machines that 37speaking different languages, to many different machines that speak a common
35speak a common language. The ultimate goal is to help differing 38language. The ultimate goal is to help differing architectures and technologies,
36architectures and technologies, come together in a productive, 39come together in a productive, happily coexisting environment.
37happily coexisting environment.
38</p>
39
40<p> 40</p>
41
42<p>
41Following the directions outlined in this HOWTO should give you an 43Following the directions outlined in this HOWTO should give you an excellent
42excellent step towards a peaceful cohabitation between Windows, and 44step towards a peaceful cohabitation between Windows, and virtually all known
43virtually all known variations of *nix. 45variations of *nix.
44</p>
45
46<p> 46</p>
47
48<p>
47This HOWTO originally started not as a HOWTO, but as a FAQ. It was 49This HOWTO originally started not as a HOWTO, but as a FAQ. It was intended to
48intended to explore the functionality and power of the Gentoo system, 50explore the functionality and power of the Gentoo system, portage and the
49portage and the flexibility of USE flags. Like so many other projects, 51flexibility of USE flags. Like so many other projects, it was quickly discovered
50it was quickly discovered what was missing in the Gentoo realm: there 52what was missing in the Gentoo realm: there weren't any Samba HOWTO's catered
51weren't any Samba HOWTO's catered for Gentoo users. These users are 53for Gentoo users. These users are more demanding than most; they require
52more demanding than most; they require performance, flexibility and 54performance, flexibility and customization. This does not however imply that
53customization. This does not however imply that this HOWTO was not
54intended for other distributions; rather that it was designed to work 55this HOWTO was not intended for other distributions; rather that it was designed
55with a highly customized version of Samba. 56to work with a highly customized version of Samba.
56</p>
57
58<p> 57</p>
58
59<p>
59This HOWTO will describe how to share files and printers between Windows 60This HOWTO will describe how to share files and printers between Windows PCs and
60PCs and *nix PCs. It will also demonstrate the use of the VFS (Virtual 61*nix PCs. It will also demonstrate the use of the VFS (Virtual File System)
61File System) feature of Samba to incorporate automatic virus protection. 62feature of Samba to incorporate automatic virus protection. As a finale, it will
62As a finale, it will show you how to mount and manipulate shares. 63show you how to mount and manipulate shares.
63</p>
64
65<p> 64</p>
65
66<p>
66There are a few topics that will be mentioned, but are out of the 67There are a few topics that will be mentioned, but are out of the scope of this
67scope of this HOWTO. These will be noted as they are presented. 68HOWTO. These will be noted as they are presented.
68</p>
69
70<p> 69</p>
70
71<p>
71This HOWTO is based on a compilation and merge of an excellent HOWTO 72This HOWTO is based on a compilation and merge of an excellent HOWTO provided in
72provided in the <uri link="http://forums.gentoo.org">Gentoo forums</uri> 73the <uri link="http://forums.gentoo.org">Gentoo forums</uri> by Andreas "daff"
73by Andreas "daff" Ntaflos and the collected knowledge of Joshua Preston. 74Ntaflos and the collected knowledge of Joshua Preston. The link to this
74The link to this discussion is provided below for your reference: 75discussion is provided below for your reference:
75</p> 76</p>
76 77
77<ul> 78<ul>
78 <li> 79 <li>
79 <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO 80 <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO
87<title>Before you use this guide</title> 88<title>Before you use this guide</title>
88<body> 89<body>
89 90
90<p> 91<p>
91There are a several other guides for setting up CUPS and/or Samba, please read 92There are a several other guides for setting up CUPS and/or Samba, please read
92them as well, as they may tell you things left out of this HOWTO (intentional 93them as well, as they may tell you things left out of this HOWTO (intentional or
93or otherwise). One such document is the very useful and well written <uri 94otherwise). One such document is the very useful and well written <uri
94link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration 95link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration
95issues and specific printer setup is not discussed here. 96issues and specific printer setup is not discussed here.
96</p> 97</p>
97 98
98</body> 99</body>
100<section> 101<section>
101<title>Brief Overview</title> 102<title>Brief Overview</title>
102<body> 103<body>
103 104
104<p> 105<p>
105After presenting the various USE flags, the following list will outline 106After presenting the various USE flags, the following list will outline all of
106all of the topics covered as they are presented: 107the topics covered as they are presented:
107</p> 108</p>
108 109
109<ul> 110<ul>
110 <li>On the Samba server: 111 <li>On the Samba server:
111 <ul> 112 <ul>
153 A working network (home/office/etc) consisting of more than one machine) 154 A working network (home/office/etc) consisting of more than one machine)
154 </li> 155 </li>
155</ul> 156</ul>
156 157
157<p> 158<p>
158The main package we use here is net-fs/samba, however, you will need 159The main package we use here is net-fs/samba, however, you will need a kernel
159a kernel with smbfs support enabled in order to mount a samba or windows 160with cifs support enabled in order to mount a samba or windows share from
160share from another computer. CUPS will be emerged if it is not already. 161another computer. CUPS will be emerged if it is not already.
161app-antivirus/clamav will be used also, but others should be easily adapted 162app-antivirus/clamav will be used also, but others should be easily adapted to
162to work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning 163work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning
163technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ... 164technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ...
164</p> 165</p>
165 166
166</body> 167</body>
167</section> 168</section>
181<pre caption="Samba uses the following USE Variables:"> 182<pre caption="Samba uses the following USE Variables:">
182kerberos acl cups ldap pam readline python oav 183kerberos acl cups ldap pam readline python oav
183</pre> 184</pre>
184 185
185<p> 186<p>
186Depending on the network topology and the specific requirements of 187Depending on the network topology and the specific requirements of the server,
187the server, the USE flags outlined below will define what to include or 188the USE flags outlined below will define what to include or exclude from the
188exclude from the emerging of Samba. 189emerging of Samba.
189</p> 190</p>
190 191
191<table> 192<table>
192<tr> 193<tr>
193 <th><b>USE flag</b></th> 194 <th><b>USE flag</b></th>
211 </ti> 212 </ti>
212</tr> 213</tr>
213<tr> 214<tr>
214 <th><b>cups</b></th> 215 <th><b>cups</b></th>
215 <ti> 216 <ti>
216 This enables support for the Common Unix Printing System. This 217 This enables support for the Common Unix Printing System. This provides an
217 provides an interface allowing local CUPS printers to be shared to 218 interface allowing local CUPS printers to be shared to other systems in the
218 other systems in the network. 219 network.
219 </ti> 220 </ti>
220</tr> 221</tr>
221<tr> 222<tr>
222 <th><b>ldap</b></th> 223 <th><b>ldap</b></th>
223 <ti> 224 <ti>
224 Enables the Lightweight Directory Access Protocol (LDAP). If Samba is 225 Enables the Lightweight Directory Access Protocol (LDAP). If Samba is
225 expected to use Active Directory, this option must be used. This would 226 expected to use Active Directory, this option must be used. This would be
226 be used in the event Samba needs to login to or provide login to 227 used in the event Samba needs to login to or provide login to a
227 a Domain/Active Directory Server. The kerberos USE flag is needed for 228 Domain/Active Directory Server. The kerberos USE flag is needed for proper
228 proper functioning of this option. 229 functioning of this option.
229 </ti> 230 </ti>
230</tr> 231</tr>
231<tr> 232<tr>
232 <th><b>pam</b></th> 233 <th><b>pam</b></th>
233 <ti> 234 <ti>
234 Include support for pluggable authentication modules (PAM). This 235 Include support for pluggable authentication modules (PAM). This provides
235 provides the ability to authenticate users on the Samba Server, which is 236 the ability to authenticate users on the Samba Server, which is required if
236 required if users have to login to your server. The kerberos USE flag 237 users have to login to your server. The kerberos USE flag is recommended
237 is recommended along with this option. 238 along with this option.
238 </ti> 239 </ti>
239</tr> 240</tr>
240<tr> 241<tr>
241 <th><b>readline</b></th> 242 <th><b>readline</b></th>
242 <ti> 243 <ti>
243 Link Samba against libreadline. This is highly recommended and should 244 Link Samba against libreadline. This is highly recommended and should
244 probably not be disabled 245 probably not be disabled.
245 </ti> 246 </ti>
246</tr> 247</tr>
247<tr> 248<tr>
248 <th><b>python</b></th> 249 <th><b>python</b></th>
249 <ti> 250 <ti>
250 Python bindings API. Provides an API that will allow Python to 251 Python bindings API. Provides an API that will allow Python to interface
251 interface with Samba. 252 with Samba.
252 </ti> 253 </ti>
253</tr> 254</tr>
254<tr> 255<tr>
255 <th><b>oav</b></th> 256 <th><b>oav</b></th>
256 <ti> 257 <ti>
257 Provides on-access scanning of Samba shares with FRISK F-Prot 258 Provides on-access scanning of Samba shares with FRISK F-Prot Daemon,
258 Daemon, Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep 259 Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep (SAVI),
259 (SAVI), Symantec CarrierScan, and Trend Micro (VSAPI). 260 Symantec CarrierScan, and Trend Micro (VSAPI).
260 </ti> 261 </ti>
261</tr> 262</tr>
262</table> 263</table>
263 264
264<p> 265<p>
291<section> 292<section>
292<title>Emerging Samba</title> 293<title>Emerging Samba</title>
293<body> 294<body>
294 295
295<p> 296<p>
296First of all: be sure that all your hostnames resolve correctly. 297First of all: be sure that all your hostnames resolve correctly. Either have a
297Either have a working domain name system running on your network 298working domain name system running on your network or appropriate entries in
298or appropriate entries in your <path>/etc/hosts</path> file. 299your <path>/etc/hosts</path> file. <c>cupsaddsmb</c> often borks if hostnames
299<c>cupsaddsmb</c> often borks if hostnames don't point to the correct 300don't point to the correct machines.
300machines.
301</p>
302
303<p> 301</p>
302
303<p>
304Hopefully now you can make an assessment of what you'll actually need in 304Hopefully now you can make an assessment of what you'll actually need in order
305order to use Samba with your particular setup. The setup used for this 305to use Samba with your particular setup. The setup used for this HOWTO is:
306HOWTO is:
307</p> 306</p>
308 307
309<ul> 308<ul>
310 <li>oav</li> 309 <li>oav</li>
311 <li>cups</li> 310 <li>cups</li>
312 <li>readline</li> 311 <li>readline</li>
313 <li>pam</li> 312 <li>pam</li>
314</ul> 313</ul>
315 314
316<p> 315<p>
317To optimize performance, size and the time of the build, the 316To optimize performance, size and the time of the build, the USE flags are
318USE flags are specifically included or excluded. 317specifically included or excluded.
319</p> 318</p>
320 319
321<pre caption="Emerge Samba"> 320<pre caption="Emerge Samba">
322# <i>echo "net-fs/samba oav readline cups pam" &gt;&gt; /etc/portage/package.use</i> 321# <i>echo "net-fs/samba oav readline cups pam" &gt;&gt; /etc/portage/package.use</i>
323# <i>emerge net-fs/samba</i> 322# <i>emerge net-fs/samba</i>
324</pre> 323</pre>
325 324
326<note> 325<note>
327The following archs will need to add <e>~</e> to their <e>KEYWORDS</e>: x86, 326The following arches will need to add <e>~</e> to their <e>KEYWORDS</e>: x86,
328ppc, sparc, hppa, ia64 and alpha 327ppc, sparc, hppa, ia64 and alpha
329</note> 328</note>
330 329
331<p> 330<p>
332This will emerge Samba and CUPS (if CUPS is not already emerged). 331This will emerge Samba and CUPS (if CUPS is not already emerged).
337<section> 336<section>
338<title>Emerging ClamAV</title> 337<title>Emerging ClamAV</title>
339<body> 338<body>
340 339
341<p> 340<p>
342Because the <e>oav</e> USE flag only provides an interface to allow on access 341Because the <e>oav</e> USE flag only provides an interface to allow on access
343virus scanning, the actual virus scanner must be emerged. The scanner 342virus scanning, the actual virus scanner must be emerged. The scanner used in
344used in this HOWTO is ClamAV. 343this HOWTO is ClamAV.
345</p> 344</p>
346 345
347<pre caption="Emerge Clamav"> 346<pre caption="Emerge Clamav">
348# <i>emerge app-antivirus/clamav</i> 347# <i>emerge app-antivirus/clamav</i>
349</pre> 348</pre>
381<section> 380<section>
382<title>Configuring Samba</title> 381<title>Configuring Samba</title>
383<body> 382<body>
384 383
385<p> 384<p>
386The main Samba configuration file is <path>/etc/samba/smb.conf</path>. 385The main Samba configuration file is <path>/etc/samba/smb.conf</path>. It is
387It is divided in sections indicated by [sectionname]. Comments are either 386divided in sections indicated by [sectionname]. Comments are either
388# or ;. A sample <path>smb.conf</path> is included below with comments and 387# or ;. A sample <path>smb.conf</path> is included below with comments and
389suggestions for modifications. If more details are required, see the 388suggestions for modifications. If more details are required, see the man page
390man page for <path>smb.conf</path>, the installed 389for <path>smb.conf</path>, the installed <path>smb.conf.example</path>, the
391<path>smb.conf.example</path>, the Samba Web site or any of the 390Samba Web site or any of the numerous Samba books available.
392numerous Samba books available.
393</p> 391</p>
394 392
395<pre caption="A Sample /etc/samba/smb.conf"> 393<pre caption="A Sample /etc/samba/smb.conf">
396[global] 394[global]
397<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment> 395<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment>
482guest ok = yes 480guest ok = yes
483path = /home/samba/public 481path = /home/samba/public
484</pre> 482</pre>
485 483
486<warn> 484<warn>
487If you like to use Samba's guest account to do anything concerning 485If you like to use Samba's guest account to do anything concerning printing from
488printing from Windows clients: don't set <c>guest only = yes</c> in 486Windows clients: don't set <c>guest only = yes</c> in the <c>[global]</c>
489the <c>[global]</c> section. The guest account seems to cause 487section. The guest account seems to cause problems when running
490problems when running <c>cupsaddsmb</c> sometimes when trying to 488<c>cupsaddsmb</c> sometimes when trying to connect from Windows machines. See
491connect from Windows machines. See below, too, when we talk about 489below, too, when we talk about <c>cupsaddsmb</c> and the problems that can
492<c>cupsaddsmb</c> and the problems that can arise. Use a dedicated
493printer user, like <c>printeruser</c> or <c>printer</c> or 490arise. Use a dedicated printer user, like <c>printeruser</c> or <c>printer</c>
494<c>printme</c> or whatever. It doesn't hurt and it will certainly 491or <c>printme</c> or whatever. It doesn't hurt and it will certainly protect you
495protect you from a lot of problems. 492from a lot of problems.
496</warn> 493</warn>
497 494
498<warn> 495<warn>
499Turning on ClamAV on access scanning in the <c>[global]</c> section will slow 496Turning on ClamAV on access scanning in the <c>[global]</c> section will slow
500down the performance of your Samba server dramatically. 497down the performance of your Samba server dramatically.
501</warn> 498</warn>
502 499
503<p> 500<p>
504Now create the directories required for the minimum configuration of 501Now create the directories required for the minimum configuration of Samba to
505Samba to share the installed printer throughout the network. 502share the installed printer throughout the network.
506</p> 503</p>
507 504
508<pre caption="Create the directories"> 505<pre caption="Create the directories">
509# <i>mkdir /etc/samba/printer</i> 506# <i>mkdir /etc/samba/printer</i>
510# <i>mkdir /var/spool/samba</i> 507# <i>mkdir /var/spool/samba</i>
511# <i>mkdir /home/samba/public</i> 508# <i>mkdir /home/samba/public</i>
512</pre> 509</pre>
513 510
514<p> 511<p>
515At least one Samba user is required in order to install the printer 512At least one Samba user is required in order to install the printer drivers and
516drivers and to allow users to connect to the printer. Users must 513to allow users to connect to the printer. Users must exist in the system's
517exist in the system's <path>/etc/passwd</path> file. 514<path>/etc/passwd</path> file.
518</p> 515</p>
519 516
520<pre caption="Creating the users"> 517<pre caption="Creating the users">
521# <i>smbpasswd -a root</i> 518# <i>smbpasswd -a root</i>
522 519
545<section> 542<section>
546<title>Configuring ClamAV</title> 543<title>Configuring ClamAV</title>
547<body> 544<body>
548 545
549<p> 546<p>
550The configuration file specified to be used in <path>smb.conf</path> is 547The configuration file specified to be used in <path>smb.conf</path> is
551<path>/etc/samba/vscan-clamav.conf</path>. While these options are set 548<path>/etc/samba/vscan-clamav.conf</path>. While these options are set to the
552to the defaults, the infected file action may need to be changed. 549defaults, the infected file action may need to be changed.
553</p> 550</p>
554 551
555<pre caption="/etc/samba/vscan-clamav.conf"> 552<pre caption="/etc/samba/vscan-clamav.conf">
556[samba-vscan] 553[samba-vscan]
557<comment>; run-time configuration for vscan-samba using 554<comment>; run-time configuration for vscan-samba using
614<comment>; port number the ScannerDaemon listens on</comment> 611<comment>; port number the ScannerDaemon listens on</comment>
615oav port = 8127 612oav port = 8127
616</pre> 613</pre>
617 614
618<p> 615<p>
619It is generally a good idea to start the virus scanner immediately. Add 616It is generally a good idea to start the virus scanner immediately. Add it to
620it to the <e>default</e> runlevel and then start the <c>clamd</c> service 617the <e>default</e> runlevel and then start the <c>clamd</c> service immediately.
621immediately. The service has two processes: freshclam keeps the virus definition 618The service has two processes: freshclam keeps the virus definition database up
622database up to date while clamd is the actual anti-virus daemon. First you may 619to date while clamd is the actual anti-virus daemon. First you may want to set
623want to set the paths of the logfiles so that it fits your needs. 620the paths of the logfiles so that it fits your needs.
624</p> 621</p>
625 622
626<pre caption="Checking the location of the logfiles"> 623<pre caption="Checking the location of the logfiles">
627# <i>vim /etc/clamd.conf</i> 624# <i>vim /etc/clamd.conf</i>
628<comment>(Check the line "LogFile /var/log/clamd.log")</comment> 625<comment>(Check the line "LogFile /var/log/clamd.log")</comment>
646<section> 643<section>
647<title>Configuring CUPS</title> 644<title>Configuring CUPS</title>
648<body> 645<body>
649 646
650<p> 647<p>
651This is a little more complicated. CUPS' main config file is 648This is a little more complicated. CUPS' main config file is
652<path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's 649<path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's
653<path>httpd.conf</path> file, so many you may find it familiar. Outlined 650<path>httpd.conf</path> file, so many you may find it familiar. Outlined in the
654in the example are the directives that need to be changed: 651example are the directives that need to be changed:
655</p> 652</p>
656 653
657<pre caption="/etc/cups/cupsd.conf"> 654<pre caption="/etc/cups/cupsd.conf">
658ServerName <i>PrintServer</i> <comment># your printserver name</comment> 655ServerName <i>PrintServer</i> <comment># your printserver name</comment>
659ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment> 656ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment>
730<p> 727<p>
731First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to 728First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to
732find and download the correct PPD file for your printer and CUPS. To do so, 729find and download the correct PPD file for your printer and CUPS. To do so,
733click the link Printer Listings to the left. Select your printers manufacturer 730click the link Printer Listings to the left. Select your printers manufacturer
734and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On 731and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On
735the page coming up click the "recommended driver" link after reading the 732the page coming up click the "recommended driver" link after reading the various
736various notes and information. Then fetch the PPD file from the next page, 733notes and information. Then fetch the PPD file from the next page, again after
737again after reading the notes and introductions there. You may have to select 734reading the notes and introductions there. You may have to select your printers
738your printers manufacturer and model again. Reading the <uri 735manufacturer and model again. Reading the <uri
739link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> 736link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> is
740is also very helpful when working with CUPS. 737also very helpful when working with CUPS.
741</p>
742
743<p> 738</p>
739
740<p>
744Now you have a PPD file for your printer to work with CUPS. Place it in 741Now you have a PPD file for your printer to work with CUPS. Place it in
745<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was 742<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was named
746named <path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer. 743<path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer.
747This can be done via the CUPS web interface or via command line. The web 744This can be done via the CUPS web interface or via command line. The web
748interface is found at <path>http://PrintServer:631</path> once CUPS is running. 745interface is found at <path>http://PrintServer:631</path> once CUPS is running.
749</p> 746</p>
750 747
751<pre caption="Install the printer via command line"> 748<pre caption="Install the printer via command line">
752# <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i> 749# <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i>
753# <i>/etc/init.d/cupsd restart</i> 750# <i>/etc/init.d/cupsd restart</i>
754</pre> 751</pre>
755 752
756<p> 753<p>
757Remember to adjust to what you have. Be sure to have the name 754Remember to adjust to what you have. Be sure to have the name (<c>-p</c>
758(<c>-p</c> argument) right (the name you set above during the Samba 755argument) right (the name you set above during the Samba configuration!) and to
759configuration!) and to put in the correct <c>usb:/dev/usb/blah</c>, 756put in the correct <c>usb:/dev/usb/blah</c>, <c>parallel:/dev/blah</c> or
760<c>parallel:/dev/blah</c> or whatever device you are using for your 757whatever device you are using for your printer.
761printer.
762</p>
763
764<p> 758</p>
759
760<p>
765You should now be able to access the printer from the web interface 761You should now be able to access the printer from the web interface and be able
766and be able to print a test page. 762to print a test page.
767</p> 763</p>
768 764
769</body> 765</body>
770</section> 766</section>
771<section> 767<section>
772<title>Installing the Windows printer drivers</title> 768<title>Installing the Windows printer drivers</title>
773<body> 769<body>
774 770
775<p> 771<p>
776Now that the printer should be working it is time to install the drivers 772Now that the printer should be working it is time to install the drivers for the
777for the Windows clients to work. Samba 2.2 introduced this functionality. 773Windows clients to work. Samba 2.2 introduced this functionality. Browsing to
778Browsing to the print server in the Network Neighbourhood, right-clicking 774the print server in the Network Neighbourhood, right-clicking on the
779on the printershare and selecting "connect" downloads the appropriate 775printershare and selecting "connect" downloads the appropriate drivers
780drivers automagically to the connecting client, avoiding the hassle of 776automagically to the connecting client, avoiding the hassle of manually
781manually installing printer drivers locally. 777installing printer drivers locally.
782</p> 778</p>
783 779
784<p> 780<p>
785There are two sets of printer drivers for this. First, the Adobe PS drivers 781There are two sets of printer drivers for this. First, the Adobe PS drivers
786which can be obtained from <uri 782which can be obtained from <uri
787link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript 783link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript
788printer drivers). Second, there are the CUPS PS drivers, to be obtained <uri 784printer drivers). Second, there are the CUPS PS drivers, to be obtained by
789link="http://dev.gentoo.org/~nightmorph/misc/cups-samba-5.0rc2.tar.gz">here</uri>. 785emerging <c>net-print/cups-windows</c>. Note that it may still be marked ~arch,
786so you may need to add it to <path>/etc/portage/package.keywords</path>. There
790There doesn't seem to be a difference between the functionality of the two, but 787doesn't seem to be a difference between the functionality of the two, but the
791the Adobe PS drivers need to be extracted on a Windows System since it's a 788Adobe PS drivers need to be extracted on a Windows System since it's a Windows
792Windows binary. Also the whole procedure of finding and copying the correct 789binary. Also the whole procedure of finding and copying the correct files is a
793files is a bit more hassle. The CUPS drivers seem to support some options the 790bit more hassle. The CUPS drivers seem to support some options the Adobe drivers
794Adobe drivers don't. 791don't.
795</p>
796<!--
797used to be available at www.cups.org/articles.php?L142+p4, but only 6.0 is
798available. at some point, we should update this for 6.0.
799-->
800
801<p> 792</p>
802This HOWTO uses the CUPS drivers for Windows. The downloaded file is 793
803called <path>cups-samba-5.0rc2.tar.gz</path>. Extract the files
804contained into a directory.
805</p> 794<p>
806 795This HOWTO uses the CUPS drivers for Windows. Install them as shown:
807<pre caption="Extract the drivers and run the install">
808# <i>tar -xzf cups-samba-5.0rc2.tar.gz</i>
809# <i>cd cups-samba-5.0rc2</i>
810<comment>(Only use this script if CUPS resides in /usr/share/cups)</comment>
811# <i>./cups-samba.install</i>
812</pre>
813
814<p> 796</p>
815<path>cups-samba.ss</path> is a TAR archive containing three files:
816<path>cups5.hlp</path>, <path>cupsdrvr5.dll</path> and
817<path>cupsui5.dll</path>. These are the actual driver files.
818</p>
819 797
820<warn> 798<pre caption="Install the drivers and restart CUPS">
821The script <c>cups-samba.install</c> may not work for all *nixes (i.e. FreeBSD) 799# <i>emerge -av cups-windows</i>
822because almost everything which is not part of the base system is
823installed somewhere under the prefix <path>/usr/local/</path>. This
824seems not to be the case for most things you install under GNU/Linux.
825However, if your CUPS installation is somewhere other than
826<path>/usr/share/cups/</path> see the example below.
827</warn>
828
829<p>
830Suppose your CUPS installation resides under
831<path>/usr/local/share/cups/</path>, and you want to install the drivers there.
832Do the following:
833</p>
834
835<pre caption="Manually installing the drivers">
836# <i>cd /path/you/extracted/the/CUPS-driver/tarball/into</i>
837# <i>tar -xf cups-samba.ss</i>
838<comment>(This extracts the files to usr/share/cups/drivers under the CURRENT WORKING DIRECTORY)</comment>
839# <i>cd usr/share/cups/drivers</i>
840<comment>(no leading / !)</comment>
841# <i>cp cups* /usr/local/share/cups/drivers</i>
842# <i>/etc/init.d/cupsd restart</i> 800# <i>/etc/init.d/cupsd restart</i>
843</pre> 801</pre>
844 802
845<p> 803<p>
846Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution. 804Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution.
865</p> 823</p>
866 824
867<ul> 825<ul>
868 <li> 826 <li>
869 The hostname given as a parameter for <c>-h</c> and <c>-H</c> 827 The hostname given as a parameter for <c>-h</c> and <c>-H</c>
870 (<c>PrintServer</c>) often does not resolve correctly and doesn't 828 (<c>PrintServer</c>) often does not resolve correctly and doesn't identify
871 identify the print server for CUPS/Samba interaction. If an error 829 the print server for CUPS/Samba interaction. If an error like: <b>Warning:
872 like: <b>Warning: No PPD file for printer "CUPS_PRINTER_NAME" - 830 No PPD file for printer "CUPS_PRINTER_NAME" - skipping!</b> occurs, the
873 skipping!</b> occurs, the first thing you should do is substitute 831 first thing you should do is substitute <c>PrintServer</c> with
874 <c>PrintServer</c> with <c>localhost</c> and try it again. 832 <c>localhost</c> and try it again.
875 </li> 833 </li>
876 <li> 834 <li>
877 The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message 835 The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message
878 is quite common, but can be triggered by many problems. It's unfortunately 836 is quite common, but can be triggered by many problems. It's unfortunately
879 not very helpful. One thing to try is to temporarily set <c>security = 837 not very helpful. One thing to try is to temporarily set <c>security =
880 user</c> in your <path>smb.conf</path>. After/if the installation completes 838 user</c> in your <path>smb.conf</path>. After/if the installation completes
881 successfully, you should set it back to share, or whatever it was set to 839 successfully, you should set it back to share, or whatever it was set to
882 before. 840 before.
883 </li> 841 </li>
884</ul> 842</ul>
885 843
886<p> 844<p>
887This should install the correct driver directory structure under 845This should install the correct driver directory structure under
888<path>/etc/samba/printer</path>. That would be 846<path>/etc/samba/printer</path>. That would be
889<path>/etc/samba/printer/W32X86/2/</path>. The files contained should 847<path>/etc/samba/printer/W32X86/2/</path>. The files contained should be the 3
890be the 3 driver files and the PPD file, renamed to YourPrinterName.ppd 848driver files and the PPD file, renamed to <path>YourPrinterName.ppd</path> (the
891(the name which you gave the printer when installing it (see above). 849name which you gave the printer when installing it (see above).
892</p>
893
894<p> 850</p>
851
852<p>
895Pending no errors or other complications, your drivers are now 853Pending no errors or other complications, your drivers are now installed.
896installed.
897</p> 854</p>
898 855
899</body> 856</body>
900</section> 857</section>
901<section> 858<section>
919<title>Testing our Samba configuration</title> 876<title>Testing our Samba configuration</title>
920<body> 877<body>
921 878
922<p> 879<p>
923We will want to test our configuration file to ensure that it is formatted 880We will want to test our configuration file to ensure that it is formatted
924properly and all of our options have at least the correct syntax. To do 881properly and all of our options have at least the correct syntax. To do this we
925this we run <c>testparm</c>. 882run <c>testparm</c>.
926</p> 883</p>
927 884
928<pre caption="Running the testparm"> 885<pre caption="Running the testparm">
929<comment>(By default, testparm checks /etc/samba/smb.conf)</comment> 886<comment>(By default, testparm checks /etc/samba/smb.conf)</comment>
930# <i>/usr/bin/testparm</i> 887# <i>/usr/bin/testparm</i>
960<section> 917<section>
961<title>Checking our services</title> 918<title>Checking our services</title>
962<body> 919<body>
963 920
964<p> 921<p>
965It would probably be prudent to check our logs at this time also. 922It would probably be prudent to check our logs at this time also. We will also
966We will also want to take a peak at our Samba shares using 923want to take a peak at our Samba shares using <c>smbclient</c>.
967<c>smbclient</c>.
968</p> 924</p>
969 925
970<pre caption="Checking the shares with smbclient"> 926<pre caption="Checking the shares with smbclient">
971# <i>smbclient -L localhost</i> 927# <i>smbclient -L localhost</i>
972Password: 928Password:
982<section> 938<section>
983<title>Printer configuration of *nix based clients</title> 939<title>Printer configuration of *nix based clients</title>
984<body> 940<body>
985 941
986<p> 942<p>
987Despite the variation or distribution, the only thing needed is CUPS. Do the 943Despite the variation or distribution, the only thing needed is CUPS. Do the
988equivalent on any other UNIX/Linux/BSD client. 944equivalent on any other UNIX/Linux/BSD client.
989</p> 945</p>
990 946
991<pre caption="Configuring a Gentoo system"> 947<pre caption="Configuring a Gentoo system">
992# <i>emerge cups</i> 948# <i>emerge cups</i>
1023</pre> 979</pre>
1024 980
1025<p> 981<p>
1026Just point your web browser to <c>http://printserver:631</c> on the client if 982Just point your web browser to <c>http://printserver:631</c> on the client if
1027you want to manage your printers and their jobs with a nice web interface. 983you want to manage your printers and their jobs with a nice web interface.
1028Replace <c>printserver</c> with the name of the <e>machine</e> that acts as 984Replace <c>printserver</c> with the name of the <e>machine</e> that acts as your
1029your print server, not the name you gave to the cups print server if you used 985print server, not the name you gave to the cups print server if you used
1030different names. 986different names.
1031</p> 987</p>
1032 988
1033</body> 989</body>
1034</section> 990</section>
1035<section> 991<section>
1036<title>Mounting a Windows or Samba share in GNU/Linux</title> 992<title>Mounting a Windows or Samba share in GNU/Linux</title>
1037<body> 993<body>
1038 994
995<note>
996Don't forget to first <c>emerge samba</c> on the client(s) that that will be
997accessing the shares.
998</note>
999
1039<p> 1000<p>
1040Now is time to configure our kernel to support smbfs. Since I'm assumming we've 1001Now is time to configure our kernel to support cifs. Since I'm assuming
1041all compiled at least one kernel, we'll need to make sure we have all the right 1002we've all compiled at least one kernel, we'll need to make sure we have all the
1042options selected in our kernel. For simplicity sake, make it a module for ease 1003right options selected in our kernel. For simplicity's sake, make it a module
1043of use. It is the author's opinion that kernel modules are a good thing and 1004for ease of use. It is the author's opinion that kernel modules are a good thing
1044should be used whenever possible. 1005and should be used whenever possible.
1045</p>
1046
1047<pre caption="Relevant kernel options" >
1048CONFIG_SMB_FS=m
1049CONFIG_SMB_UNIX=y
1050</pre>
1051
1052<p> 1006</p>
1007
1008<pre caption="Kernel support" >
1009CONFIG_CIFS=m
1010</pre>
1011
1012<p>
1053Then make the module/install it; insert them with: 1013Then make the module/install it; insert it with:
1054</p> 1014</p>
1055 1015
1056<pre caption="Loading the kernel module"> 1016<pre caption="Loading the kernel module">
1057# <i>modprobe smbfs</i> 1017# <i>modprobe cifs</i>
1058</pre> 1018</pre>
1059 1019
1060<p> 1020<p>
1061Once the modules is loaded, mounting a Windows or Samba share is 1021Once the module is loaded, mounting a Windows or Samba share is possible. Use
1062possible. Use <c>mount</c> to accomplish this, as detailed below: 1022<c>mount</c> to accomplish this, as detailed below:
1063</p> 1023</p>
1064 1024
1065<pre caption="Mounting a Windows/Samba share"> 1025<pre caption="Mounting a Windows/Samba share">
1066<comment>(The syntax for mounting a Windows/Samba share is: 1026<comment>(The syntax for mounting a Windows/Samba share is:
1067 mount -t smbfs [-o username=xxx,password=xxx] //server/share /mnt/point 1027 mount -t cifs [-o username=xxx,password=xxx] //server/share /mnt/point
1068If we are not using passwords or a password is not needed)</comment> 1028If we are not using passwords or a password is not needed)</comment>
1069 1029
1070# <i>mount -t smbfs //PrintServer/public /mnt/public</i> 1030# <i>mount -t cifs //PrintServer/public /mnt/public</i>
1071 1031
1072<comment>(If a password is needed)</comment> 1032<comment>(If a password is needed)</comment>
1073# <i>mount -t smbfs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i> 1033# <i>mount -t cifs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i>
1074</pre> 1034</pre>
1075 1035
1076<p> 1036<p>
1077After you mount the share, you would access it as if it were a local 1037After you mount the share, you would access it as if it were a local drive.
1078drive.
1079</p> 1038</p>
1080 1039
1081</body> 1040</body>
1082</section> 1041</section>
1083<section> 1042<section>
1084<title>Printer Configuration for Windows NT/2000/XP clients</title> 1043<title>Printer Configuration for Windows NT/2000/XP clients</title>
1085<body> 1044<body>
1086 1045
1087<p> 1046<p>
1088That's just a bit of point-and-click. Browse to 1047That's just a bit of point-and-click. Browse to <path>\\PrintServer</path> and
1089<path>\\PrintServer</path> and right click on the printer 1048right click on the printer (HPDeskJet930C) and click connect. This will download
1090(HPDeskJet930C) and click connect. This will download the drivers to
1091the Windows client and now every application (such as Word or Acrobat) 1049the drivers to the Windows client and now every application (such as Word or
1092will offer HPDeskJet930C as an available printer to print to. :-) 1050Acrobat) will offer HPDeskJet930C as an available printer to print to. :-)
1093</p> 1051</p>
1094 1052
1095</body> 1053</body>
1096</section> 1054</section>
1097</chapter> 1055</chapter>
1101<section> 1059<section>
1102<title>A Fond Farewell</title> 1060<title>A Fond Farewell</title>
1103<body> 1061<body>
1104 1062
1105<p> 1063<p>
1106Well that should be it. You should now have a successful printing enviroment 1064That should be it. You should now have a successful printing enviroment that is
1107that is friendly to both Windows and *nix as well as a fully virus-free working 1065friendly to both Windows and *nix as well as a fully virus-free working share!
1108share!
1109</p> 1066</p>
1110 1067
1111</body> 1068</body>
1112</section> 1069</section>
1113</chapter> 1070</chapter>
1131 on Samba/CUPS configuration</uri> 1088 on Samba/CUPS configuration</uri>
1132 </li> 1089 </li>
1133 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li> 1090 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li>
1134 <li> 1091 <li>
1135 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt 1092 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt
1136 Pfeifle's Samba Print HOWTO</uri> ( 1093 Pfeifle's Samba Print HOWTO</uri> ( This HOWTO really covers <e>ANYTHING</e>
1137 This HOWTO really covers <e>ANYTHING</e> and <e>EVERYTHING</e>
1138 I've written here, plus a LOT more concerning CUPS and Samba, and 1094 and <e>EVERYTHING</e> I've written here, plus a LOT more concerning CUPS and
1139 generally printing support on networks. A really interesting read, 1095 Samba, and generally printing support on networks. A really interesting
1140 with lots and lots of details) 1096 read, with lots and lots of details.)
1141 </li> 1097 </li>
1142 <li><uri link="http://www.freebsddiary.org/cups.php">FreeBSD Diary's CUPS Topic</uri></li> 1098 <li><uri link="http://www.freebsddiary.org/cups.php">FreeBSD Diary's CUPS Topic</uri></li>
1143</ul> 1099</ul>
1144 1100
1145</body> 1101</body>
1147<section> 1103<section>
1148<title>Troubleshooting</title> 1104<title>Troubleshooting</title>
1149<body> 1105<body>
1150 1106
1151<p> 1107<p>
1108See <uri
1152See <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37">this 1109link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37">this
1153page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" 1110page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" manual. Lots of
1154manual. Lots of useful tips there! Be sure to look this one up 1111useful tips there! Be sure to look this one up first, before posting questions
1155first, before posting questions and problems! Maybe the solution 1112and problems! Maybe the solution you're looking for is right there.
1156you're looking for is right there.
1157</p> 1113</p>
1158 1114
1159</body> 1115</body>
1160</section> 1116</section>
1161</chapter> 1117</chapter>

Legend:
Removed from v.1.28  
changed lines
  Added in v.1.32

  ViewVC Help
Powered by ViewVC 1.1.20