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

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

  ViewVC Help
Powered by ViewVC 1.1.20