/[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.2 Revision 1.29
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.29 2007/06/06 23:23:35 nightmorph Exp $ -->
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<guide link="quick-samba-howto.xml"> 4<guide link="/doc/en/quick-samba-howto.xml">
4<title>Gentoo Samba3/CUPS/clamav HOWTO</title> 5<title>Gentoo Samba3/CUPS/ClamAV HOWTO</title>
5<author title="Author"> 6<author title="Author">
6 <mail link="daff at dword dot org">Andreas "daff" Ntaflos</mail> 7 <mail link="daff at dword dot org">Andreas "daff" Ntaflos</mail>
7</author> 8</author>
8<author title="Author"> 9<author title="Author">
9 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail> 10 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail>
10</author> 11</author>
11 12
12<abstract> 13<abstract>
13Setup, install and configure a Samba Server under Gentoo that shares 14Setup, install and configure a Samba Server under Gentoo that shares files,
14files, printers without the need to install drivers and provides 15printers without the need to install drivers and provides automatic virus
15automatic virus scanning. 16scanning.
16</abstract> 17</abstract>
17 18
18<!-- The content of this document is licensed under the CC-BY-SA license --> 19<!-- The content of this document is licensed under the CC-BY-SA license -->
19<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 20<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
20<license/> 21<license/>
21 22
22<version>1.2</version> 23<version>1.17</version>
23<date>May 13, 2004</date> 24<date>2007-06-06</date>
24 25
25<chapter> 26<chapter>
26<title>Introduction to this HOWTO</title> 27<title>Introduction to this HOWTO</title>
27<section> 28<section>
28<title>Purpose</title> 29<title>Purpose</title>
29<body> 30<body>
30 31
31<p> 32<p>
32This HOWTO is designed to help you move a network from many different 33This HOWTO is designed to help you move a network from many different clients
33clients speaking different languages, to many different manchines that 34speaking different languages, to many different machines that speak a common
34speak a common language. The ultimate goal is to help differing 35language. The ultimate goal is to help differing architectures and technologies,
35architechures and technologies, come together in a productive, 36come together in a productive, happily coexisting environment.
36happily coexistant environment.
37</p>
38
39<p> 37</p>
38
39<p>
40Following the directions outlined in this HOWTO should give you an 40Following the directions outlined in this HOWTO should give you an excellent
41excellent step towards a peaceful cohabitation between Windows, and 41step towards a peaceful cohabitation between Windows, and virtually all known
42virtually all known variations of *nix. 42variations of *nix.
43</p>
44
45<p> 43</p>
44
45<p>
46This HOWTO originally started not as a HOWTO, but as a FAQ. It was 46This HOWTO originally started not as a HOWTO, but as a FAQ. It was intended to
47intended to explore the functionality and power of the Gentoo system, 47explore the functionality and power of the Gentoo system, portage and the
48portage and the flexibility of USE flags. Like so many other projects, 48flexibility of USE flags. Like so many other projects, it was quickly discovered
49it was quickly discovered what was missing in the Gentoo realm: there 49what was missing in the Gentoo realm: there weren't any Samba HOWTO's catered
50weren't any Samba HOWTO's catered for Gentoo users. These users are 50for Gentoo users. These users are more demanding than most; they require
51more demanding than most; they require performance, flexibility and 51performance, flexibility and customization. This does not however imply that
52customization. This does not however imply that this HOWTO was not
53intended for other distributions; rather that it was designed to work 52this HOWTO was not intended for other distributions; rather that it was designed
54with a highly customized version of Samba. 53to work with a highly customized version of Samba.
55</p>
56
57<p> 54</p>
55
56<p>
58This HOWTO will describe how to share files and printers between Windows 57This HOWTO will describe how to share files and printers between Windows PCs and
59PCs and *nix PCs. It will also demonstrate the use of the VFS (Virtual 58*nix PCs. It will also demonstrate the use of the VFS (Virtual File System)
60File System) feature of Samba to incorporate automatic virus protection. 59feature of Samba to incorporate automatic virus protection. As a finale, it will
61As a finale, it will show you how to mount and manipulate shares. 60show you how to mount and manipulate shares.
62</p>
63
64<p> 61</p>
62
63<p>
65There are a few topics that will be mentioned, but are out of the 64There are a few topics that will be mentioned, but are out of the scope of this
66scope of this HOWTO. These will be noted as they are presented. 65HOWTO. These will be noted as they are presented.
67</p>
68
69<p> 66</p>
67
68<p>
70This HOWTO is based on a compilation and merge of an excellent HOWTO 69This HOWTO is based on a compilation and merge of an excellent HOWTO provided in
71provided in the <uri link="http://forums.gentoo.org">Gentoo forums</uri> 70the <uri link="http://forums.gentoo.org">Gentoo forums</uri> by Andreas "daff"
72by Andreas "daff" Ntaflos and the collected knowledge of Joshua Preston. 71Ntaflos and the collected knowledge of Joshua Preston. The link to this
73The link to this discussion is provided below for your reference: 72discussion is provided below for your reference:
74</p> 73</p>
75 74
76<ul> 75<ul>
77 <li> 76 <li>
78 <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO 77 <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO
85<section> 84<section>
86<title>Before you use this guide</title> 85<title>Before you use this guide</title>
87<body> 86<body>
88 87
89<p> 88<p>
90There are a several other guides for setting up CUPS and/or Samba, 89There are a several other guides for setting up CUPS and/or Samba, please read
91please read them as well, as they may tell you things left out of this 90them as well, as they may tell you things left out of this HOWTO (intentional or
92HOWTO (intentional or otherwise). One such document is the very useful 91otherwise). One such document is the very useful and well written <uri
93and well written <uri link="http://www.gentoo.org/doc/en/printing-howto.xml">Gentoo 92link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration
94Printing Guide</uri>, as configuration issues and specific printer setup 93issues and specific printer setup is not discussed here.
95is not discussed here.
96</p> 94</p>
97 95
98</body> 96</body>
99</section> 97</section>
100<section> 98<section>
101<title>Brief Overview</title> 99<title>Brief Overview</title>
102<body> 100<body>
103 101
104<p> 102<p>
105After presenting the various USE flags, the following list will outline 103After presenting the various USE flags, the following list will outline all of
106all of the topics covered as they are presented: 104the topics covered as they are presented:
107</p> 105</p>
108 106
109<ul> 107<ul>
110 <li>On the Samba server: 108 <li>On the Samba server:
111 <ul> 109 <ul>
112 <li>Install and configure CLAM-AV</li> 110 <li>Install and configure ClamAV</li>
113 <li>Install and configure Samba</li> 111 <li>Install and configure Samba</li>
114 <li>Install and configure CUPS</li> 112 <li>Install and configure CUPS</li>
115 <li>Adding the printer to CUPS</li> 113 <li>Adding the printer to CUPS</li>
116 <li>Adding the PS drivers for the Windows clients</li> 114 <li>Adding the PS drivers for the Windows clients</li>
117 </ul> 115 </ul>
141We will need the following: 139We will need the following:
142</p> 140</p>
143 141
144<ul> 142<ul>
145 <li>net-fs/samba</li> 143 <li>net-fs/samba</li>
146 <li>net-mail/clamav</li> 144 <li>app-antivirus/clamav</li>
147 <li>net-print/cups</li> 145 <li>net-print/cups</li>
148 <li>net-print/foomatic</li> 146 <li>net-print/foomatic</li>
149 <li>net-print/hpijs (if you have an HP printer)</li> 147 <li>net-print/hplip (if you have an HP printer)</li>
150 <li>A kernel of sorts (preferably 2.4.24+ or 2.6.x)</li> 148 <li>A kernel of sorts (2.6)</li>
151 <li>A printer (PS or non-PS, maybe not TOO new or fancy)</li> 149 <li>A printer (PS or non-PS, maybe not TOO new or fancy)</li>
152 <li> 150 <li>
153 A working network (home/office/etc) consisting of more than one machine) 151 A working network (home/office/etc) consisting of more than one machine)
154 </li> 152 </li>
155</ul> 153</ul>
156 154
157<p> 155<p>
158The main package we use here is net-fs/samba, however, you will need 156The 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 157with smbfs 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. 158another computer. CUPS will be emerged if it is not already.
161net-mail/clamav will be used also, but others should be easily adapted 159app-antivirus/clamav will be used also, but others should be easily adapted to
162to work with Samba. 160work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning
161technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ...
163</p> 162</p>
164 163
165</body> 164</body>
166</section> 165</section>
167</chapter> 166</chapter>
167
168<chapter> 168<chapter>
169<title>Getting acquainted with Samba</title> 169<title>Getting acquainted with Samba</title>
170<section> 170<section>
171<title>The USE Flags</title> 171<title>The USE Flags</title>
172<body> 172<body>
173 173
174<p> 174<p>
175Before emerging anything, take a look at the various USE flags 175Before emerging anything, take a look at some of the various USE flags available
176available to Samba. 176to Samba.
177</p> 177</p>
178 178
179<pre caption="Samba uses the following USE Variables:"> 179<pre caption="Samba uses the following USE Variables:">
180kerberos mysql xml acl cups ldap pam readline python oav 180kerberos acl cups ldap pam readline python oav
181</pre> 181</pre>
182 182
183<p> 183<p>
184Depending on the network topology and the specific requirements of 184Depending on the network topology and the specific requirements of the server,
185the server, the USE flags outlined below will define what to include or 185the USE flags outlined below will define what to include or exclude from the
186exclude from the emerging of Samba. 186emerging of Samba.
187</p> 187</p>
188 188
189<table> 189<table>
190<tr> 190<tr>
191 <th><b>USE flag</b></th> 191 <th><b>USE flag</b></th>
198 intended to join an existing domain or Active Directory. See the note 198 intended to join an existing domain or Active Directory. See the note
199 below for more information. 199 below for more information.
200 </ti> 200 </ti>
201</tr> 201</tr>
202<tr> 202<tr>
203 <th><b>mysql</b></th>
204 <ti>
205 This will allow Samba to use MySQL in order to do password authentication.
206 It will store ACLs, usernames, passwords, etc in a database versus a
207 flat file. If Samba is needed to do password authentication, such as
208 acting as a password validation server or a Primary Domain Controller
209 (PDC).
210 </ti>
211</tr>
212<tr>
213 <th><b>xml</b></th>
214 <ti>
215 The xml USE option for Samba provides a password database backend allowing
216 Samba to store account details in XML files, for the same reasons listed in
217 the mysql USE flag description.
218 </ti>
219</tr>
220<tr>
221 <th><b>acl</b></th> 203 <th><b>acl</b></th>
222 <ti> 204 <ti>
223 Enables Access Control Lists. The ACL support in Samba uses a patched 205 Enables Access Control Lists. The ACL support in Samba uses a patched
224 ext2/ext3, or SGI's XFS in order to function properly as it extends more 206 ext2/ext3, or SGI's XFS in order to function properly as it extends more
225 detailed access to files or directories; much more so than typical *nix 207 detailed access to files or directories; much more so than typical *nix
227 </ti> 209 </ti>
228</tr> 210</tr>
229<tr> 211<tr>
230 <th><b>cups</b></th> 212 <th><b>cups</b></th>
231 <ti> 213 <ti>
232 This enables support for the Common Unix Printing System. This 214 This enables support for the Common Unix Printing System. This provides an
233 provides an interface allowing local CUPS printers to be shared to 215 interface allowing local CUPS printers to be shared to other systems in the
234 other systems in the network. 216 network.
235 </ti> 217 </ti>
236</tr> 218</tr>
237<tr> 219<tr>
238 <th><b>ldap</b></th> 220 <th><b>ldap</b></th>
239 <ti> 221 <ti>
240 Enables the Lightweight Directory Access Protocol (LDAP). If Samba is 222 Enables the Lightweight Directory Access Protocol (LDAP). If Samba is
241 expected to use Active Directory, this option must be used. This would 223 expected to use Active Directory, this option must be used. This would be
242 be used in the event Samba needs to login to or provide login to 224 used in the event Samba needs to login to or provide login to a
243 a Domain/Active Directory Server. The kerberos USE flag is needed for 225 Domain/Active Directory Server. The kerberos USE flag is needed for proper
244 proper functioning of this option. 226 functioning of this option.
245 </ti> 227 </ti>
246</tr> 228</tr>
247<tr> 229<tr>
248 <th><b>pam</b></th> 230 <th><b>pam</b></th>
249 <ti> 231 <ti>
250 Include support for pluggable authentication modules (PAM). This 232 Include support for pluggable authentication modules (PAM). This provides
251 provides the ability to authenticate users on the Samba Server, which is 233 the ability to authenticate users on the Samba Server, which is required if
252 required if users have to login to your server. The kerberos USE flag 234 users have to login to your server. The kerberos USE flag is recommended
253 is recommended along with this option. 235 along with this option.
254 </ti> 236 </ti>
255</tr> 237</tr>
256<tr> 238<tr>
257 <th><b>readline</b></th> 239 <th><b>readline</b></th>
258 <ti> 240 <ti>
259 Link Samba again libreadline. This is highly recommended and should 241 Link Samba against libreadline. This is highly recommended and should
260 probably not be disabled 242 probably not be disabled.
261 </ti> 243 </ti>
262</tr> 244</tr>
263<tr> 245<tr>
264 <th><b>python</b></th> 246 <th><b>python</b></th>
265 <ti> 247 <ti>
266 Python bindings API. Provides an API that will allow Python to 248 Python bindings API. Provides an API that will allow Python to interface
267 interface with Samba. 249 with Samba.
268 </ti> 250 </ti>
269</tr> 251</tr>
270<tr> 252<tr>
271 <th><b>oav</b></th> 253 <th><b>oav</b></th>
272 <ti> 254 <ti>
273 Provides on-access scanning of Samba shares with FRISK F-Prot 255 Provides on-access scanning of Samba shares with FRISK F-Prot Daemon,
274 Daemon, Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep 256 Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep (SAVI),
275 (SAVI), Symantec CarrierScan, and Trend Micro (VSAPI). 257 Symantec CarrierScan, and Trend Micro (VSAPI).
276 </ti> 258 </ti>
277</tr> 259</tr>
278</table> 260</table>
279 261
280<p> 262<p>
291 <li> 273 <li>
292 While Active Directory, ACL, and PDC functions are out of the intended 274 While Active Directory, ACL, and PDC functions are out of the intended
293 scope of this HOWTO, you may find these links as helpful to your cause: 275 scope of this HOWTO, you may find these links as helpful to your cause:
294 <ul> 276 <ul>
295 <li><uri>http://www.bluelightning.org/linux/samba_acl_howto/</uri></li> 277 <li><uri>http://www.bluelightning.org/linux/samba_acl_howto/</uri></li>
296 <li><uri>http://open-projects.linuxcare.com/research-papers/winbind-08162000.html</uri></li>
297 <li><uri>http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory</uri></li> 278 <li><uri>http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory</uri></li>
298 </ul> 279 </ul>
299 </li> 280 </li>
300</ul> 281</ul>
301 282
302</body> 283</body>
303</section> 284</section>
304</chapter> 285</chapter>
286
305<chapter> 287<chapter>
306<title>Server Software Installation</title> 288<title>Server Software Installation</title>
307<section> 289<section>
308<title>Emerging Samba</title> 290<title>Emerging Samba</title>
309<body> 291<body>
310 292
311<p> 293<p>
312First of all: be sure that all your hostnames resolve correctly. 294First of all: be sure that all your hostnames resolve correctly. Either have a
313Either have a working domain name system running on your network 295working domain name system running on your network or appropriate entries in
314or appropriate entries in your /etc/hosts file. cupsaddsmb often 296your <path>/etc/hosts</path> file. <c>cupsaddsmb</c> often borks if hostnames
315borks if hostnames don't point to the correct machines. 297don't point to the correct machines.
316</p>
317
318<p> 298</p>
299
300<p>
319Hopefully now you can make an assessment of what you'll actually need in 301Hopefully now you can make an assessment of what you'll actually need in order
320order to use Samba with your particular setup. The setup used for this 302to use Samba with your particular setup. The setup used for this HOWTO is:
321HOWTO is:
322</p> 303</p>
323 304
324<ul> 305<ul>
325 <li>oav</li> 306 <li>oav</li>
326 <li>cups</li> 307 <li>cups</li>
327 <li>readline</li> 308 <li>readline</li>
328 <li>pam</li> 309 <li>pam</li>
329</ul> 310</ul>
330 311
331<p> 312<p>
332To optimize performance, size and the time of the build, the 313To optimize performance, size and the time of the build, the USE flags are
333USE flags are specifically included or excluded. 314specifically included or excluded.
334</p> 315</p>
335 316
336<pre caption="Emerge Samba"> 317<pre caption="Emerge Samba">
337<comment>(Note the USE flags!)</comment> 318# <i>echo "net-fs/samba oav readline cups pam" &gt;&gt; /etc/portage/package.use</i>
338# <i>USE=&quot;oav readline cups pam -python -ldap -kerberos -xml -acl -mysql&quot; emerge net-fs/samba</i> 319# <i>emerge net-fs/samba</i>
339</pre> 320</pre>
340 321
341<note> 322<note>
342The following archs will need to add <e>~</e> to their <e>KEYWORDS</e>: x86, 323The following arches will need to add <e>~</e> to their <e>KEYWORDS</e>: x86,
343ppc, sparc, hppa, ia64 and alpha 324ppc, sparc, hppa, ia64 and alpha
344</note> 325</note>
345 326
346<p> 327<p>
347This will emerge Samba and CUPS (if CUPS is not already emerged). 328This will emerge Samba and CUPS (if CUPS is not already emerged).
348</p> 329</p>
349 330
350</body> 331</body>
351</section> 332</section>
352<section> 333<section>
353<title>Emerging clam-av</title> 334<title>Emerging ClamAV</title>
354<body> 335<body>
355 336
356<p> 337<p>
357Because the oav USE flag only provides an interface to allow on access 338Because the <e>oav</e> USE flag only provides an interface to allow on access
358virus scanning, the actual virus scanner must be emerged. The scanner 339virus scanning, the actual virus scanner must be emerged. The scanner used in
359used in this HOWTO is <e>net-mail/clamav</e>. 340this HOWTO is ClamAV.
360</p> 341</p>
361 342
362<pre caption="Emerge clam-av"> 343<pre caption="Emerge Clamav">
363# <i>emerge net-mail/clamav</i> 344# <i>emerge app-antivirus/clamav</i>
364</pre> 345</pre>
365 346
366</body> 347</body>
367</section> 348</section>
368<section> 349<section>
374</pre> 355</pre>
375 356
376</body> 357</body>
377</section> 358</section>
378<section> 359<section>
379<title>Emerging net-print/hpijs</title> 360<title>Emerging net-print/hplip</title>
380<body> 361<body>
381 362
382<p> 363<p>
383You only need to emerge this if you use an HP printer. 364You only need to emerge this if you use an HP printer.
384</p> 365</p>
385 366
386<pre caption="Emerge hpijs"> 367<pre caption="Emerge hplip">
387# <i>emerge net-print/hpijs</i> 368# <i>emerge net-print/hplip</i>
388</pre> 369</pre>
389 370
390</body> 371</body>
391</section> 372</section>
392</chapter> 373</chapter>
374
393<chapter> 375<chapter>
394<title>Server Configuration</title> 376<title>Server Configuration</title>
395<section> 377<section>
396<title>Configuring Samba</title> 378<title>Configuring Samba</title>
397<body> 379<body>
398 380
399<p> 381<p>
400The main Samba configuration file is <path>/etc/samba/smb.conf</path>. 382The main Samba configuration file is <path>/etc/samba/smb.conf</path>. It is
401It is divided in sections indicated by [sectionname]. Comments are either 383divided in sections indicated by [sectionname]. Comments are either
402# or ;. A sample <path>smb.conf</path> is included below with comments and 384# or ;. A sample <path>smb.conf</path> is included below with comments and
403suggestions for modifications. If more details are required, see the 385suggestions for modifications. If more details are required, see the man page
404man page for <path>smb.conf</path>, the installed smb.conf.example, the Samba 386for <path>smb.conf</path>, the installed <path>smb.conf.example</path>, the
405Web site or any of the numerous Samba books available. 387Samba Web site or any of the numerous Samba books available.
406</p> 388</p>
407 389
408<pre caption="A Sample /etc/samba/smb.conf"> 390<pre caption="A Sample /etc/samba/smb.conf">
409[global] 391[global]
410<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment> 392<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment>
411workgroup = <comment>MYWORKGROUPNAME</comment> 393workgroup = <comment>MYWORKGROUPNAME</comment>
412<comment># Of course this has no REAL purpose other than letting 394<comment># Of course this has no REAL purpose other than letting
413# everyone know its not Windows! 395# everyone knows it's not Windows!
414# %v prints the version of Samba we are using.</comment> 396# %v prints the version of Samba we are using.</comment>
415server string = Samba Server %v 397server string = Samba Server %v
416<comment># We are going to use cups, so we are going to put it in here ;-)</comment> 398<comment># We are going to use cups, so we are going to put it in here ;-)</comment>
417printcap name = cups 399printcap name = cups
418printing = cups 400printing = cups
440guest ok = yes 422guest ok = yes
441<comment># We now will implement the on access virus scanner. 423<comment># We now will implement the on access virus scanner.
442# NOTE: By putting this in our [Global] section, we enable 424# NOTE: By putting this in our [Global] section, we enable
443# scanning of ALL shares, you could optionally move 425# scanning of ALL shares, you could optionally move
444# these to a specific share and only scan it.</comment> 426# these to a specific share and only scan it.</comment>
445vfs object = /usr/lib/samba/vfs/vscan-clamav.so 427
428<comment># For Samba 3.x. This enables ClamAV on access scanning.</comment>
429vfs object = vscan-clamav
446vfs options = config-file = /etc/samba/vscan-clamav.conf 430vscan-clamav: config-file = /etc/samba/vscan-clamav.conf
447 431
448<comment># Now we setup our print drivers information!</comment> 432<comment># Now we setup our print drivers information!</comment>
449[print$] 433[print$]
450comment = Printer Drivers 434comment = Printer Drivers
451path = /etc/samba/printer <comment># this path holds the driver structure</comment> 435path = /etc/samba/printer <comment># this path holds the driver structure</comment>
452guest ok = no 436guest ok = yes
453browseable = yes 437browseable = yes
454read only = yes 438read only = yes
455<comment># Modify this to "username,root" if you don't want root to 439<comment># Modify this to "username,root" if you don't want root to
456# be the only printer admin)</comment> 440# be the only printer admin)</comment>
457write list = <i>root</i> 441write list = <i>root</i>
470 454
471<comment># Now we setup our printers share. This should be 455<comment># Now we setup our printers share. This should be
472# browseable, printable, public.</comment> 456# browseable, printable, public.</comment>
473[printers] 457[printers]
474comment = All Printers 458comment = All Printers
475browseable = yes 459browseable = no
476printable = yes 460printable = yes
461writable = no
477public = yes 462public = yes
478guest ok = yes 463guest ok = yes
479path = /var/spool/samba 464path = /var/spool/samba
480<comment># Modify this to "username,root" if you don't want root to 465<comment># Modify this to "username,root" if you don't want root to
481# be the only printer admin)</comment> 466# be the only printer admin)</comment>
491create mode = 0766 476create mode = 0766
492guest ok = yes 477guest ok = yes
493path = /home/samba/public 478path = /home/samba/public
494</pre> 479</pre>
495 480
496<p> 481<warn>
497There are several warnings that we should put here:
498</p>
499
500<ul>
501 <li>
502 If 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
503 printing from Windows clients: don't 483Windows clients: don't set <c>guest only = yes</c> in the <c>[global]</c>
504 </li>
505 <li>Don't set guest only = yes in the global section</li>
506 <li>
507 The guest account seems to cause problems when running cupsaddsmb sometimes 484section. The guest account seems to cause problems when running
508 when trying to connect from Windows machines. See below, too, when we talk 485<c>cupsaddsmb</c> sometimes when trying to connect from Windows machines. See
509 about cupsaddsmb and the problems that can arise. Use a dedicated printer 486below, too, when we talk about <c>cupsaddsmb</c> and the problems that can
510 user, like "printeruser" or "printer" or "printme" or whatever. It doesn't 487arise. Use a dedicated printer user, like <c>printeruser</c> or <c>printer</c>
511 hurt and it will certainly protect you from a lot of problems. 488or <c>printme</c> or whatever. It doesn't hurt and it will certainly protect you
512 </li> 489from a lot of problems.
513</ul> 490</warn>
514 491
492<warn>
493Turning on ClamAV on access scanning in the <c>[global]</c> section will slow
494down the performance of your Samba server dramatically.
495</warn>
496
515<p> 497<p>
516Now create the directories required for the minimum configuration of 498Now create the directories required for the minimum configuration of Samba to
517Samba to share the installed printer throughout the network. 499share the installed printer throughout the network.
518</p> 500</p>
519 501
520<pre caption="Create the directories"> 502<pre caption="Create the directories">
521# <i>mkdir /etc/samba/printer</i> 503# <i>mkdir /etc/samba/printer</i>
522# <i>mkdir /var/spool/samba</i> 504# <i>mkdir /var/spool/samba</i>
523# <i>mkdir /home/samba/public</i> 505# <i>mkdir /home/samba/public</i>
524</pre> 506</pre>
525 507
526<p> 508<p>
527At 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
528drivers 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
529exist in the system's <path>/etc/passwd</path> file. 511<path>/etc/passwd</path> file.
530</p> 512</p>
531 513
532<pre caption="Creating the users"> 514<pre caption="Creating the users">
533# <i>smbpasswd -a root</i> 515# <i>smbpasswd -a root</i>
534 516
539<p> 521<p>
540The Samba passwords need not be the same as the system passwords 522The Samba passwords need not be the same as the system passwords
541in <path>/etc/passwd</path>. 523in <path>/etc/passwd</path>.
542</p> 524</p>
543 525
526<p>
527You will also need to update <path>/etc/nsswitch.conf</path> so that Windows
528systems can be found easily using NetBIOS:
529</p>
530
531<pre caption="Editing /etc/nsswitch.conf">
532# <i>nano -w /etc/nsswitch.conf</i>
533<comment>(Edit the hosts: line)</comment>
534hosts: files dns <i>wins</i>
535</pre>
536
544</body> 537</body>
545</section>
546<section> 538</section>
539<section>
547<title>Configuring clam-av</title> 540<title>Configuring ClamAV</title>
548<body> 541<body>
549 542
550<p> 543<p>
551The 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
552<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
553to the defaults, the infected file action may need to be changed. 546defaults, the infected file action may need to be changed.
554</p> 547</p>
555 548
556<pre caption="/etc/samba/vscan-clamav.conf"> 549<pre caption="/etc/samba/vscan-clamav.conf">
557[samba-vscan] 550[samba-vscan]
558<comment>; run-time configuration for vscan-samba using 551<comment>; run-time configuration for vscan-samba using
575 568
576<comment>; if communication to clamd fails, should access to file denied? 569<comment>; if communication to clamd fails, should access to file denied?
577; (default: yes)</comment> 570; (default: yes)</comment>
578deny access on error = yes 571deny access on error = yes
579 572
580<comment>; if daemon files with a minor error (corruption, etc.), 573<comment>; if daemon fails with a minor error (corruption, etc.),
581; should access to file denied? 574; should access to file denied?
582; (default: yes)</comment> 575; (default: yes)</comment>
583deny access on minor error = yes 576deny access on minor error = yes
584 577
585<comment>; send a warning message via Windows Messenger service 578<comment>; send a warning message via Windows Messenger service
603; of period, samba-vscan use a last recently used file mechanism to avoid 596; of period, samba-vscan use a last recently used file mechanism to avoid
604; multiple scans of a file. This setting specified the maximum number of 597; multiple scans of a file. This setting specified the maximum number of
605; elements of the last recently used file list. (default: 100)</comment> 598; elements of the last recently used file list. (default: 100)</comment>
606max lru files entries = 100 599max lru files entries = 100
607 600
608<comment>; an entry is invalidad after lru file entry lifetime (in seconds). 601<comment>; an entry is invalidated after lru file entry lifetime (in seconds).
609; (Default: 5)</comment> 602; (Default: 5)</comment>
610lru file entry lifetime = 5 603lru file entry lifetime = 5
611 604
612<comment>; socket name of clamd (default: /var/run/clamd)</comment> 605<comment>; socket name of clamd (default: /var/run/clamd)</comment>
613clamd socket name = /var/run/clamd 606clamd socket name = /tmp/clamd
614</pre>
615 607
608<comment>; port number the ScannerDaemon listens on</comment>
609oav port = 8127
610</pre>
611
616<p> 612<p>
617It 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
618it to the default runlevel and then start the clamd service immediately. 614the <e>default</e> runlevel and then start the <c>clamd</c> service immediately.
615The service has two processes: freshclam keeps the virus definition database up
616to date while clamd is the actual anti-virus daemon. First you may want to set
617the paths of the logfiles so that it fits your needs.
618</p>
619
620<pre caption="Checking the location of the logfiles">
621# <i>vim /etc/clamd.conf</i>
622<comment>(Check the line "LogFile /var/log/clamd.log")</comment>
623# <i>vim /etc/freshclam.conf</i>
624<comment>(Check the line "UpdateLogFile /var/log/freshclam.log")</comment>
625# <i>vim /etc/conf.d/clamd</i>
626<comment>(Set "START_CLAMD=yes" and "START_FRESHCLAM=yes")</comment>
627</pre>
628
629<p>
630Now fire up the virus scanner.
619</p> 631</p>
620 632
621<pre caption="Add clamd to bootup and start it"> 633<pre caption="Add clamd to bootup and start it">
622# <i>rc-update add clamd default</i> 634# <i>rc-update add clamd default</i>
623# <i>/etc/init.d/clamd start</i> 635# <i>/etc/init.d/clamd start</i>
628<section> 640<section>
629<title>Configuring CUPS</title> 641<title>Configuring CUPS</title>
630<body> 642<body>
631 643
632<p> 644<p>
633This is a little more complicated). CUPS' main config file is 645This is a little more complicated. CUPS' main config file is
634<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
635<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
636in the example are the directives that need to be changed: 648example are the directives that need to be changed:
637</p> 649</p>
638 650
639<pre caption="/etc/cups/cupsd.conf"> 651<pre caption="/etc/cups/cupsd.conf">
640ServerName <i>PrintServer</i> <comment># your printserver name</comment> 652ServerName <i>PrintServer</i> <comment># your printserver name</comment>
641ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, eg you</comment> 653ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment>
642 654
643AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment> 655AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment>
644ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment> 656ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment>
645 657
646LogLevel debug <comment># only while isntalling and testing, should later be 658LogLevel debug <comment># only while isntalling and testing, should later be
647 # changed to 'info'</comment> 659 # changed to 'info'</comment>
648 660
649MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back, 661MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back,
650 # there seemed to be a bug in CUPS' controlling of the web interface, 662 # there seemed to be a bug in CUPS' controlling of the web interface,
651 # making CUPS think a denial of service attack was in progress when 663 # making CUPS think a denial of service attack was in progress when
652 # I tried to configure a printer with the web interface. weird.</comment> 664 # I tried to configure a printer with the web interface. weird.</comment>
655 667
656&lt;Location /&gt; 668&lt;Location /&gt;
657Order Deny,Allow 669Order Deny,Allow
658Deny From All 670Deny From All
659Allow From <i>192.168.1.*</i> <comment># the addresses of your internel network 671Allow From <i>192.168.1.*</i> <comment># the addresses of your internel network
660 # eg 192.168.1.* will allow connections from any host on 672 # e.g. 192.168.1.* will allow connections from any host on
661 # the 192.168.1.0 network. change to whatever suits you</comment> 673 # the 192.168.1.0 network. change to whatever suits you</comment>
662&lt;/Location&gt; 674&lt;/Location&gt;
663 675
664&lt;Location /admin&gt; 676&lt;Location /admin&gt;
665AuthType Basic 677AuthType Basic
672&lt;/Location&gt; 684&lt;/Location&gt;
673</pre> 685</pre>
674 686
675<p> 687<p>
676Edit <path>/etc/cups/mime.convs</path> to uncomment some lines. 688Edit <path>/etc/cups/mime.convs</path> to uncomment some lines.
677The changes to mime.convs and mime.types are needed to make CUPSprint Microsoft Office document files. 689The changes to <path>mime.convs</path> and <path>mime.types</path> are
690needed to make CUPS print Microsoft Office document files.
678</p> 691</p>
679 692
680<pre caption="/etc/cups/mime.convs"> 693<pre caption="/etc/cups/mime.convs">
681<comment>(The following line is found near the end of the file. Uncomment it)</comment> 694<comment>(The following line is found near the end of the file. Uncomment it)</comment>
682application/octet-stream application/vnd.cups-raw 0 695application/octet-stream application/vnd.cups-raw 0
683</pre> 696</pre>
684 697
685<p> 698<p>
686Edit <path>/etc/cups/mime.convs</path> to uncomment some lines. 699Edit <path>/etc/cups/mime.types</path> to uncomment some lines.
687</p> 700</p>
688 701
689<pre caption="/etc/cups/mime.types"> 702<pre caption="/etc/cups/mime.types">
690<comment>(The following line is found near the end of the file. Uncomment it)</comment> 703<comment>(The following line is found near the end of the file. Uncomment it)</comment>
691application/octet-stream 704application/octet-stream
696</p> 709</p>
697 710
698<pre caption="Setting up the CUPS service" > 711<pre caption="Setting up the CUPS service" >
699<comment>(To start CUPS on boot)</comment> 712<comment>(To start CUPS on boot)</comment>
700# <i>rc-update add cupsd default</i> 713# <i>rc-update add cupsd default</i>
701<comment>(To start CUPS if it isn't started)</comment> 714<comment>(To start or restart CUPS now)</comment>
702# <i>/etc/init.d/cupsd start</i>
703<comment>(If CUPS is already started we'll need to restart it!)</comment>
704# <i>/etc/init.d/cupsd restart</i> 715# <i>/etc/init.d/cupsd restart</i>
705</pre> 716</pre>
706 717
707</body> 718</body>
708</section> 719</section>
709<section> 720<section>
710<title>Installing a printer for and with CUPS</title> 721<title>Installing a printer for and with CUPS</title>
711<body> 722<body>
712 723
713<p> 724<p>
714First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> 725First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to
715to find and download the correct PPD file for your printer and CUPS. To 726find and download the correct PPD file for your printer and CUPS. To do so,
716do so, click the link Printer Listings to the left. Select your 727click the link Printer Listings to the left. Select your printers manufacturer
717printers manufacturer and the model in the pulldown menu, eg HP and 728and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On
718DeskJet 930C. Click "Show". On the page coming up click the "recommended 729the page coming up click the "recommended driver" link after reading the various
719driver" link after reading the various notes and information. Then fetch 730notes and information. Then fetch the PPD file from the next page, again after
720the PPD file from the next page, again after reading the notes and
721introductions there. You may have to select your printers manufacturer 731reading the notes and introductions there. You may have to select your printers
722and model again. Reading the <uri link="http://www.linuxprinting.org/cups-doc.html">CUPS 732manufacturer and model again. Reading the <uri
733link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> is
723quickstart guide</uri> is also very helpful when working with CUPS. 734also very helpful when working with CUPS.
724</p>
725
726<p> 735</p>
736
737<p>
727Now 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
728<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
729named HP-DeskJet_930C-hpijs.ppd. You should now install the printer. 740<path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer.
730This 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
731interface is found at http://PrintServer:631 once CUPS is running. 742interface is found at <path>http://PrintServer:631</path> once CUPS is running.
732</p> 743</p>
733 744
734<pre caption="Install the printer via command line"> 745<pre caption="Install the printer via command line">
735# <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>
747# <i>/etc/init.d/cupsd restart</i>
736</pre> 748</pre>
737 749
738<p> 750<p>
739Remember to adjust to what you have. Be sure to have the name (-p) right (the 751Remember to adjust to what you have. Be sure to have the name (<c>-p</c>
740name you set above during the Samba configuration!) and to put in the 752argument) right (the name you set above during the Samba configuration!) and to
741correct usb:/dev/usb/blah, parallel:/dev/blah or whatever device you 753put in the correct <c>usb:/dev/usb/blah</c>, <c>parallel:/dev/blah</c> or
742are using for your printer. 754whatever device you are using for your printer.
743</p>
744
745<p> 755</p>
756
757<p>
746You should now be able to access the printer from the web interface. You 758You should now be able to access the printer from the web interface and be able
747should now be able to print a test page. 759to print a test page.
748</p> 760</p>
749 761
750</body> 762</body>
751</section> 763</section>
752<section> 764<section>
753<title>Installing the Windows printer drivers</title> 765<title>Installing the Windows printer drivers</title>
754<body> 766<body>
755 767
756<p> 768<p>
757Now 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
758for the Windows clients to work. Samba 2.2 introduced this functionality. 770Windows clients to work. Samba 2.2 introduced this functionality. Browsing to
759Browsing to the print server in the Network Neighbourhood, right-clicking 771the print server in the Network Neighbourhood, right-clicking on the
760on the printershare and selecting "connect" downloads the appropriate 772printershare and selecting "connect" downloads the appropriate drivers
761drivers automagically to the connecting client, avoiding the hassle of 773automagically to the connecting client, avoiding the hassle of manually
762manually installing printer drivers locally. 774installing printer drivers locally.
763</p>
764
765<p> 775</p>
776
777<p>
766There are two sets of printer drivers for this. First, the Adobe PS 778There are two sets of printer drivers for this. First, the Adobe PS drivers
767drivers which can be obtained from <uri 779which can be obtained from <uri
768link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> 780link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript
769(PostScript printer drivers). Second, there are the CUPS PS drivers, 781printer drivers). Second, there are the CUPS PS drivers, to be obtained <uri
770to be obtained from <uri link="http://www.cups.org/software.php">the 782link="http://dev.gentoo.org/~nightmorph/misc/cups-samba-5.0rc2.tar.gz">here</uri>.
771CUPS homepage</uri> and selecting "CUPS Driver for Windows" from the 783There doesn't seem to be a difference between the functionality of the two, but
772pull down menu. There doesn't seem to be a difference between the 784the Adobe PS drivers need to be extracted on a Windows System since it's a
773functionality of the two, but the Adobe PS drivers need to be extracted 785Windows binary. Also the whole procedure of finding and copying the correct
774on a Windows System since it's a Windows binary. Also the whole procedure 786files is a bit more hassle. The CUPS drivers seem to support some options the
775of finding and copying the correct files is a bit more hassle. The CUPS 787Adobe drivers don't.
776drivers seem to support some options the Adobe drivers don't.
777</p> 788</p>
789<!--
790used to be available at www.cups.org/articles.php?L142+p4, but only 6.0 is
791available. at some point, we should update this for 6.0.
792-->
778 793
779<p> 794<p>
780This HOWTO uses the CUPS drivers for Windows. The downloaded file is 795This HOWTO uses the CUPS drivers for Windows. The downloaded file is
781called <path>cups-samba-5.0rc2.tar.gz</path>. Extract the files 796called <path>cups-samba-5.0rc2.tar.gz</path>. Extract the files
782contained into a directory. 797contained into a directory.
788<comment>(Only use this script if CUPS resides in /usr/share/cups)</comment> 803<comment>(Only use this script if CUPS resides in /usr/share/cups)</comment>
789# <i>./cups-samba.install</i> 804# <i>./cups-samba.install</i>
790</pre> 805</pre>
791 806
792<p> 807<p>
793cups-samba.ss is a TAR archive containing three files: 808<path>cups-samba.ss</path> is a TAR archive containing three files:
794cups5.hlp, cupsdrvr5.dll and cupsui5.dll. These are the actual driver 809<path>cups5.hlp</path>, <path>cupsdrvr5.dll</path> and
795files. 810<path>cupsui5.dll</path>. These are the actual driver files.
796</p> 811</p>
797 812
798<warn> 813<warn>
799The script cups-samba.install may not work for all *nixes (ie FreeBSD) 814The script <c>cups-samba.install</c> may not work for all *nixes (i.e. FreeBSD)
800because almost everything which is not part of the base system is 815because almost everything which is not part of the base system is installed
801installed somewhere under the prefix <path>/usr/local/</path>. This 816somewhere under the prefix <path>/usr/local/</path>. This seems not to be the
802seems not to be the case for most things you install under GNU/Linux. 817case for most things you install under GNU/Linux. However, if your CUPS
803However, if your CUPS installation is somewhere other than 818installation is somewhere other than <path>/usr/share/cups/</path> see the
804<path>/usr/share/cups/</path> See the example below. 819example below.
805</warn> 820</warn>
806 821
807<p> 822<p>
808Suppose your CUPS installation resides under 823Suppose your CUPS installation resides under
809<path>/usr/local/share/cups/</path>, and you want to install the drivers there. 824<path>/usr/local/share/cups/</path>, and you want to install the drivers there.
810Do the following: 825Do the following:
811</p> 826</p>
812 827
813<pre caption="Manually installing the drivers"> 828<pre caption="Manually installing the drivers">
814# <i>cd /path/you/extracted/the/CUPS-driver/tarball/into</i> 829# <i>cd /path/you/extracted/the/CUPS-driver/tarball/into</i>
815# <i>tar -xf cups-samba.ss</i> 830# <i>tar -xf cups-samba.ss</i>
816<comment>(This extracts the files to usr/share/cups/drivers under the CURRENT WORKING DIRECTORY)</comment> 831<comment>(This extracts the files to usr/share/cups/drivers under the CURRENT WORKING DIRECTORY)</comment>
817# <i>cd usr/share/cups/drivers</i> 832# <i>cd usr/share/cups/drivers</i>
818<comment>(no leading / !)</comment> 833<comment>(no leading / !)</comment>
819# <i>cp cups* /usr/local/share/cups/drivers</i> 834# <i>cp cups* /usr/local/share/cups/drivers</i>
835# <i>/etc/init.d/cupsd restart</i>
820</pre> 836</pre>
821 837
822<p> 838<p>
823Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS 839Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution.
824distribution. It's man page is an interesting read. 840Its man page is an interesting read.
825</p> 841</p>
826 842
827<pre caption="Run cupsaddsmb"> 843<pre caption="Run cupsaddsmb">
828# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i> 844# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i>
829<comment>(Instead of HPDeskJet930C you could also specify "-a", which will 845<comment>(Instead of HPDeskJet930C you could also specify "-a", which will
830"export all known printers".)</comment> 846"export all known printers".)</comment>
831# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -a</i> 847# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -a</i>
832</pre> 848</pre>
833 849
834<warn> 850<warn>
835The execution of this command often causes the most trouble. 851The execution of this command often causes the most trouble. Read through the
836Reading through the <uri
837link="http://forums.gentoo.com/viewtopic.php?t=110931">posts in this 852<uri link="http://forums.gentoo.org/viewtopic.php?t=110931">posts in this
838thread</uri>. 853thread</uri> for some troubleshooting tips.
839</warn> 854</warn>
840 855
841<p> 856<p>
842Here are common errors that may happen: 857Here are common errors that may happen:
843</p> 858</p>
844 859
845<ul> 860<ul>
846 <li> 861 <li>
847 The hostname given as a parameter for -h and -H (PrintServer) often does 862 The hostname given as a parameter for <c>-h</c> and <c>-H</c>
848 not resolve correctly and doesn't identify the print server for CUPS/Samba 863 (<c>PrintServer</c>) often does not resolve correctly and doesn't identify
849 interaction. 864 the print server for CUPS/Samba interaction. If an error like: <b>Warning:
850 If an error like: <b>Warning: No PPD file for printer "CUPS_PRINTER_NAME" - 865 No PPD file for printer "CUPS_PRINTER_NAME" - skipping!</b> occurs, the
851 skipping!</b> occurs, the first thing you should do is substitute 866 first thing you should do is substitute <c>PrintServer</c> with
852 PrintServer with localhost and try it again. 867 <c>localhost</c> and try it again.
853 </li> 868 </li>
854 <li> 869 <li>
855 The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message 870 The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message
856 is quite common, but can be triggered by many problems. It's unfortunately 871 is quite common, but can be triggered by many problems. It's unfortunately
857 not very helpful. One thing to try is to temporarily set <b>security = 872 not very helpful. One thing to try is to temporarily set <c>security =
858 user</b> in your <path>smb.conf</path>. After/if the installation completes 873 user</c> in your <path>smb.conf</path>. After/if the installation completes
859 successfully, you should set it back to share, or whatever it was set to 874 successfully, you should set it back to share, or whatever it was set to
860 before. 875 before.
861 </li> 876 </li>
862</ul> 877</ul>
863 878
864<p> 879<p>
865This should install the correct driver directory structure under 880This should install the correct driver directory structure under
866<path>/etc/samba/printer</path>. That would be 881<path>/etc/samba/printer</path>. That would be
867<path>/etc/samba/printer/W32X86/2/</path>. The files contained should 882<path>/etc/samba/printer/W32X86/2/</path>. The files contained should be the 3
868be the 3 driver files and the PPD file, renamed to YourPrinterName.ppd 883driver files and the PPD file, renamed to <path>YourPrinterName.ppd</path> (the
869(the name which you gave the printer when installing it (see above). 884name which you gave the printer when installing it (see above).
870</p>
871
872<p> 885</p>
886
887<p>
873Pending no errors or other complications, your drivers are now 888Pending no errors or other complications, your drivers are now installed.
874installed.
875</p> 889</p>
876 890
877</body> 891</body>
878</section> 892</section>
879<section> 893<section>
897<title>Testing our Samba configuration</title> 911<title>Testing our Samba configuration</title>
898<body> 912<body>
899 913
900<p> 914<p>
901We will want to test our configuration file to ensure that it is formatted 915We will want to test our configuration file to ensure that it is formatted
902properly and all of our options have at least the correct syntax. To do 916properly and all of our options have at least the correct syntax. To do this we
903this we run <c>testparm</c>. 917run <c>testparm</c>.
904</p> 918</p>
905 919
906<pre caption="Running the testparm"> 920<pre caption="Running the testparm">
907<comment>(By default, testparm checks /etc/samba/smb.conf)</comment> 921<comment>(By default, testparm checks /etc/samba/smb.conf)</comment>
908# <i>/usr/bin/testparm</i> 922# <i>/usr/bin/testparm</i>
938<section> 952<section>
939<title>Checking our services</title> 953<title>Checking our services</title>
940<body> 954<body>
941 955
942<p> 956<p>
943It would probably be prudent to check our logs at this time also. 957It would probably be prudent to check our logs at this time also. We will also
944We will also want to take a peak at our Samba shares using 958want to take a peak at our Samba shares using <c>smbclient</c>.
945<c>smbclient</c>.
946</p> 959</p>
947 960
948<pre caption="Checking the shares with smbclient"> 961<pre caption="Checking the shares with smbclient">
949# <i>smbclient -L localhost</i> 962# <i>smbclient -L localhost</i>
950Password: 963Password:
952</pre> 965</pre>
953 966
954</body> 967</body>
955</section> 968</section>
956</chapter> 969</chapter>
970
957<chapter> 971<chapter>
958<title>Configuration of the Clients</title> 972<title>Configuration of the Clients</title>
959<section> 973<section>
960<title>Printer configuration of *nix based clients</title> 974<title>Printer configuration of *nix based clients</title>
961<body> 975<body>
962 976
963<p> 977<p>
964Despite the variation or distribution, the only thing needed is CUPS. 978Despite the variation or distribution, the only thing needed is CUPS. Do the
965Do the equivalent on any other UNIX/Linux/BSD client. 979equivalent on any other UNIX/Linux/BSD client.
966</p> 980</p>
967 981
968<pre caption="Configuring a Gentoo system."> 982<pre caption="Configuring a Gentoo system">
969# <i>emerge cups</i> 983# <i>emerge cups</i>
970# <i>/etc/init.d/cupsd start</i> 984# <i>nano -w /etc/cups/client.conf</i>
971# <i>rc-update add cupsd default</i> 985ServerName <i>PrintServer</i> <comment># your printserver name</comment>
972</pre> 986</pre>
973 987
974<p>
975That should be it. Nothing else will be needed. Just point your web
976browser to http://localhost:631 (on the CLIENT) and you'll see that
977PrintServer broadcasts all available printers to all CUPS clients.
978</p> 988<p>
979 989That should be it. Nothing else will be needed.
980<p> 990</p>
981To print, use for example 991
982</p> 992<p>
993If you use only one printer, it will be your default printer. If your print
994server manages several printers, your administrator will have defined a default
995printer on the server. If you want to define a different default printer for
996yourself, use the <c>lpoptions</c> command.
997</p>
998
999<pre caption="Setting your default printer">
1000<comment>(List available printers)</comment>
1001# <i>lpstat -a</i>
1002<comment>(Sample output, yours will differ)</comment>
1003HPDeskJet930C accepting requests since Jan 01 00:00
1004laser accepting requests since Jan 01 00:00
1005<comment>(Define HPDeskJet930C as your default printer)</comment>
1006# <i>lpoptions -d HPDeskJet930C</i>
1007</pre>
983 1008
984<pre caption="Printing in *nix"> 1009<pre caption="Printing in *nix">
1010<comment>(Specify the printer to be used)</comment>
985# <i>lpr -pHPDeskJet930C anything.txt</i> 1011# <i>lp -d HPDeskJet930C anything.txt</i>
986# <i>lpr -PHPDeskJet930C foobar.whatever.ps</i> 1012<comment>(Use your default printer)</comment>
987</pre>
988
989<p>
990In order to setup a default printer, you have to edit
991<path>/etc/cups/client.conf</path> and set the directive ServerName to
992your printserver. In the case of this guide that would be the
993following example.
994</p>
995
996<pre caption="/etc/cups/client.conf">
997ServerName PrintServer
998</pre>
999
1000<p>
1001The following will print foorbar.whatever.ps directly to the print
1002server.
1003</p>
1004
1005<pre caption="Printing to the default printer">
1006$ <i>lpr foobar.whatever.ps</i> 1013# <i>lp foobar.whatever.ps</i>
1007</pre> 1014</pre>
1008 1015
1009<p>
1010Some common observations when setting a default printer in this manner
1011include the following:
1012</p> 1016<p>
1013 1017Just point your web browser to <c>http://printserver:631</c> on the client if
1014<ul> 1018you want to manage your printers and their jobs with a nice web interface.
1015 <li> 1019Replace <c>printserver</c> with the name of the <e>machine</e> that acts as your
1016 Setting the ServerName in client.conf seems to work well for only one 1020print server, not the name you gave to the cups print server if you used
1017 printer, there may be yet another way to set a client's default remote 1021different names.
1018 printer. 1022</p>
1019 </li>
1020 <li>
1021 Also, when accessing http://localhost:631 on the client now, no printers
1022 seem to be "found" by the client-CUPS. This is to be expected when setting
1023 ServerName in <path>client.conf</path>.
1024 </li>
1025</ul>
1026 1023
1027</body> 1024</body>
1028</section> 1025</section>
1029<section> 1026<section>
1030<title>Mounting a Windows or Samba share in GNU/Linux</title> 1027<title>Mounting a Windows or Samba share in GNU/Linux</title>
1031<body> 1028<body>
1032 1029
1033<p> 1030<p>
1034Now is time to configure our kernel to support it the smbfs. Since I'm 1031Now is time to configure our kernel to support smbfs. Since I'm assumming we've
1035assumming we've all compiled at least one kernel, we'll need to make 1032all compiled at least one kernel, we'll need to make sure we have all the right
1036sure we have all the right options selected in our kernel. 1033options selected in our kernel. For simplicity's sake, make it a module for ease
1037For simplicity sake, make it as a module for ease of use. It is the
1038authors opinion that kernel modules are a good thing and should be used 1034of use. It is the author's opinion that kernel modules are a good thing and
1039whenever possible. 1035should be used whenever possible.
1040</p> 1036</p>
1041 1037
1042<pre caption="Relevant kernel options" > 1038<pre caption="Relevant kernel options" >
1043CONFIG_SMB_FS=m 1039CONFIG_SMB_FS=m
1044CONFIG_SMB_UNIX=y 1040CONFIG_SMB_UNIX=y
1051<pre caption="Loading the kernel module"> 1047<pre caption="Loading the kernel module">
1052# <i>modprobe smbfs</i> 1048# <i>modprobe smbfs</i>
1053</pre> 1049</pre>
1054 1050
1055<p> 1051<p>
1056Once the modules is loaded, mounting a Windows or Samba share is 1052Once the module is loaded, mounting a Windows or Samba share is possible. Use
1057possible. Use <c>mount</c> to accomplish this, as detailed below: 1053<c>mount</c> to accomplish this, as detailed below:
1058</p> 1054</p>
1059 1055
1060<pre caption="Mounting a Windows/Samba share"> 1056<pre caption="Mounting a Windows/Samba share">
1061<comment>(The syntax for mounting a Windows/Samba share is: 1057<comment>(The syntax for mounting a Windows/Samba share is:
1062 mount -t smbfs [-o username=xxx,password=xxx] //server/share /mnt/point 1058 mount -t smbfs [-o username=xxx,password=xxx] //server/share /mnt/point
1067<comment>(If a password is needed)</comment> 1063<comment>(If a password is needed)</comment>
1068# <i>mount -t smbfs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i> 1064# <i>mount -t smbfs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i>
1069</pre> 1065</pre>
1070 1066
1071<p> 1067<p>
1072After you mount the share, you would access it as if it were a local 1068After you mount the share, you would access it as if it were a local drive.
1073drive.
1074</p> 1069</p>
1075 1070
1076</body> 1071</body>
1077</section> 1072</section>
1078<section> 1073<section>
1079<title>Printer Configuration for Windows NT/2000/XP clients</title> 1074<title>Printer Configuration for Windows NT/2000/XP clients</title>
1080<body> 1075<body>
1081 1076
1082<p> 1077<p>
1083That's just a bit of point-and-click. Browse to \\PrintServer and right 1078That's just a bit of point-and-click. Browse to <path>\\PrintServer</path> and
1084click on the printer (HPDeskJet930C) and click connect. This will 1079right click on the printer (HPDeskJet930C) and click connect. This will download
1085download the drivers to the Windows client and now every application 1080the drivers to the Windows client and now every application (such as Word or
1086(such as Word or Acrobat) will offer HPDeskJet930C as an available 1081Acrobat) will offer HPDeskJet930C as an available printer to print to. :-)
1087printer to print to. :-)
1088</p> 1082</p>
1089 1083
1090</body> 1084</body>
1091</section> 1085</section>
1092</chapter> 1086</chapter>
1087
1093<chapter> 1088<chapter>
1094<title>Final Notes</title> 1089<title>Final Notes</title>
1095<section> 1090<section>
1096<title>A Fond Farewell</title> 1091<title>A Fond Farewell</title>
1097<body> 1092<body>
1098 1093
1099<p> 1094<p>
1100Well that should be it. You should now have a successful printing enviroment 1095That should be it. You should now have a successful printing enviroment that is
1101that is friendly to both Windows and *nix as well as a fully virus-free working 1096friendly to both Windows and *nix as well as a fully virus-free working share!
1102share!
1103</p> 1097</p>
1104 1098
1105</body> 1099</body>
1106</section> 1100</section>
1107</chapter> 1101</chapter>
1102
1108<chapter> 1103<chapter>
1109<title>Links and Resources</title> 1104<title>Links and Resources</title>
1110<section> 1105<section>
1111<title>Links</title> 1106<title>Links</title>
1112<body> 1107<body>
1116troubleshooting your installation: 1111troubleshooting your installation:
1117</p> 1112</p>
1118 1113
1119<ul> 1114<ul>
1120 <li><uri link="http://www.cups.org/">CUPS Homepage</uri></li> 1115 <li><uri link="http://www.cups.org/">CUPS Homepage</uri></li>
1116 <li>
1121 <li><uri link="http://www.samba.org/">Samba Homepage</uri></li> 1117 <uri link="http://www.samba.org/">Samba Homepage</uri>, especially the <uri
1118 link="http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/CUPS-printing.html">chapter
1119 on Samba/CUPS configuration</uri>
1120 </li>
1122 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li> 1121 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li>
1123 <li> 1122 <li>
1124 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt 1123 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt
1125 Pfeifle's Samba Print HOWTO</uri> ( 1124 Pfeifle's Samba Print HOWTO</uri> ( This HOWTO really covers <e>ANYTHING</e>
1126 This HOWTO really covers <e>ANYTHING</e> and <e>EVERYTHING</e>
1127 I've written here, plus a LOT more concerning CUPS and Samba, and 1125 and <e>EVERYTHING</e> I've written here, plus a LOT more concerning CUPS and
1128 generally printing support on networks. A really interesting read, 1126 Samba, and generally printing support on networks. A really interesting
1129 with lots and lots of details) 1127 read, with lots and lots of details.)
1130 </li> 1128 </li>
1131 <li><uri link="http://www.freebsddiary.org/cups.php">FreeBSD Diary's CUPS Topic</uri></li> 1129 <li><uri link="http://www.freebsddiary.org/cups.php">FreeBSD Diary's CUPS Topic</uri></li>
1132</ul> 1130</ul>
1133 1131
1134</body> 1132</body>
1136<section> 1134<section>
1137<title>Troubleshooting</title> 1135<title>Troubleshooting</title>
1138<body> 1136<body>
1139 1137
1140<p> 1138<p>
1139See <uri
1141See <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37">this 1140link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37">this
1142page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" 1141page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" manual. Lots of
1143manual. Lots of useful tips there! Be sure to look this one up 1142useful tips there! Be sure to look this one up first, before posting questions
1144first, before posting questions and problems! Maybe the solution 1143and problems! Maybe the solution you're looking for is right there.
1145you're looking for is right there.
1146</p> 1144</p>
1147 1145
1148</body> 1146</body>
1149</section> 1147</section>
1150</chapter> 1148</chapter>

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.29

  ViewVC Help
Powered by ViewVC 1.1.20