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

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.37

  ViewVC Help
Powered by ViewVC 1.1.20