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

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

  ViewVC Help
Powered by ViewVC 1.1.20