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

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

  ViewVC Help
Powered by ViewVC 1.1.20