/[gentoo]/xml/htdocs/doc/en/quick-samba-howto.xml

Diff of /xml/htdocs/doc/en/quick-samba-howto.xml

Parent Directory | Revision Log | View Patch Patch

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

 Legend:



Removed from v.1.3
 


changed lines


 
Added in v.1.29
 Legend:



Removed from v.1.3
 


changed lines


 
Added in v.1.29
-Removed from v.1.3
+Added in v.1.29

	ViewVC Help
Powered by ViewVC 1.1.20