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

Legend:
Removed from v.1.26  
changed lines
  Added in v.1.43

  ViewVC Help
Powered by ViewVC 1.1.20