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

Legend:
Removed from v.1.20  
changed lines
  Added in v.1.39

  ViewVC Help
Powered by ViewVC 1.1.20