/[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.14 Revision 1.28
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.14 2004/12/21 18:09:59 neysx Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.28 2007/06/06 22:42:25 nightmorph Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4<guide link="quick-samba-howto.xml"> 4<guide link="/doc/en/quick-samba-howto.xml">
5<title>Gentoo Samba3/CUPS/Clam AV HOWTO</title> 5<title>Gentoo Samba3/CUPS/ClamAV HOWTO</title>
6<author title="Author"> 6<author title="Author">
7 <mail link="daff at dword dot org">Andreas "daff" Ntaflos</mail> 7 <mail link="daff at dword dot org">Andreas "daff" Ntaflos</mail>
8</author> 8</author>
9<author title="Author"> 9<author title="Author">
10 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail> 10 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail>
18 18
19<!-- The content of this document is licensed under the CC-BY-SA license --> 19<!-- The content of this document is licensed under the CC-BY-SA license -->
20<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 20<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
21<license/> 21<license/>
22 22
23<version>1.10</version> 23<version>1.17</version>
24<date>2004-12-21</date> 24<date>2007-06-06</date>
25 25
26<chapter> 26<chapter>
27<title>Introduction to this HOWTO</title> 27<title>Introduction to this HOWTO</title>
28<section> 28<section>
29<title>Purpose</title> 29<title>Purpose</title>
107</p> 107</p>
108 108
109<ul> 109<ul>
110 <li>On the Samba server: 110 <li>On the Samba server:
111 <ul> 111 <ul>
112 <li>Install and configure CLAM-AV</li> 112 <li>Install and configure ClamAV</li>
113 <li>Install and configure Samba</li> 113 <li>Install and configure Samba</li>
114 <li>Install and configure CUPS</li> 114 <li>Install and configure CUPS</li>
115 <li>Adding the printer to CUPS</li> 115 <li>Adding the printer to CUPS</li>
116 <li>Adding the PS drivers for the Windows clients</li> 116 <li>Adding the PS drivers for the Windows clients</li>
117 </ul> 117 </ul>
144<ul> 144<ul>
145 <li>net-fs/samba</li> 145 <li>net-fs/samba</li>
146 <li>app-antivirus/clamav</li> 146 <li>app-antivirus/clamav</li>
147 <li>net-print/cups</li> 147 <li>net-print/cups</li>
148 <li>net-print/foomatic</li> 148 <li>net-print/foomatic</li>
149 <li>net-print/hpijs (if you have an HP printer)</li> 149 <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> 150 <li>A kernel of sorts (2.6)</li>
151 <li>A printer (PS or non-PS, maybe not TOO new or fancy)</li> 151 <li>A printer (PS or non-PS, maybe not TOO new or fancy)</li>
152 <li> 152 <li>
153 A working network (home/office/etc) consisting of more than one machine) 153 A working network (home/office/etc) consisting of more than one machine)
154 </li> 154 </li>
155</ul> 155</ul>
157<p> 157<p>
158The main package we use here is net-fs/samba, however, you will need 158The main package we use here is net-fs/samba, however, you will need
159a kernel with smbfs support enabled in order to mount a samba or windows 159a kernel with smbfs support enabled in order to mount a samba or windows
160share from another computer. CUPS will be emerged if it is not already. 160share from another computer. CUPS will be emerged if it is not already.
161app-antivirus/clamav will be used also, but others should be easily adapted 161app-antivirus/clamav will be used also, but others should be easily adapted
162to work with Samba. 162to work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning
163technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ...
163</p> 164</p>
164 165
165</body> 166</body>
166</section> 167</section>
167</chapter> 168</chapter>
171<section> 172<section>
172<title>The USE Flags</title> 173<title>The USE Flags</title>
173<body> 174<body>
174 175
175<p> 176<p>
176Before emerging anything, take a look at the various USE flags 177Before emerging anything, take a look at some of the various USE flags available
177available to Samba. 178to Samba.
178</p> 179</p>
179 180
180<pre caption="Samba uses the following USE Variables:"> 181<pre caption="Samba uses the following USE Variables:">
181kerberos mysql xml acl cups ldap pam readline python oav 182kerberos acl cups ldap pam readline python oav
182</pre> 183</pre>
183 184
184<p> 185<p>
185Depending on the network topology and the specific requirements of 186Depending on the network topology and the specific requirements of
186the server, the USE flags outlined below will define what to include or 187the server, the USE flags outlined below will define what to include or
196 <th><b>kerberos</b></th> 197 <th><b>kerberos</b></th>
197 <ti> 198 <ti>
198 Include support for Kerberos. The server will need this if it is 199 Include support for Kerberos. The server will need this if it is
199 intended to join an existing domain or Active Directory. See the note 200 intended to join an existing domain or Active Directory. See the note
200 below for more information. 201 below for more information.
201 </ti>
202</tr>
203<tr>
204 <th><b>mysql</b></th>
205 <ti>
206 This will allow Samba to use MySQL in order to do password authentication.
207 It will store ACLs, usernames, passwords, etc in a database versus a
208 flat file. If Samba is needed to do password authentication, such as
209 acting as a password validation server or a Primary Domain Controller
210 (PDC).
211 </ti>
212</tr>
213<tr>
214 <th><b>xml</b></th>
215 <ti>
216 The xml USE option for Samba provides a password database backend allowing
217 Samba to store account details in XML files, for the same reasons listed in
218 the mysql USE flag description.
219 </ti> 202 </ti>
220</tr> 203</tr>
221<tr> 204<tr>
222 <th><b>acl</b></th> 205 <th><b>acl</b></th>
223 <ti> 206 <ti>
292 <li> 275 <li>
293 While Active Directory, ACL, and PDC functions are out of the intended 276 While Active Directory, ACL, and PDC functions are out of the intended
294 scope of this HOWTO, you may find these links as helpful to your cause: 277 scope of this HOWTO, you may find these links as helpful to your cause:
295 <ul> 278 <ul>
296 <li><uri>http://www.bluelightning.org/linux/samba_acl_howto/</uri></li> 279 <li><uri>http://www.bluelightning.org/linux/samba_acl_howto/</uri></li>
297 <li><uri>http://open-projects.linuxcare.com/research-papers/winbind-08162000.html</uri></li>
298 <li><uri>http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory</uri></li> 280 <li><uri>http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory</uri></li>
299 </ul> 281 </ul>
300 </li> 282 </li>
301</ul> 283</ul>
302 284
335To optimize performance, size and the time of the build, the 317To optimize performance, size and the time of the build, the
336USE flags are specifically included or excluded. 318USE flags are specifically included or excluded.
337</p> 319</p>
338 320
339<pre caption="Emerge Samba"> 321<pre caption="Emerge Samba">
340<comment>(Note the USE flags!)</comment> 322# <i>echo "net-fs/samba oav readline cups pam" &gt;&gt; /etc/portage/package.use</i>
341# <i>USE=&quot;oav readline cups pam -python -ldap -kerberos -xml -acl -mysql&quot; emerge net-fs/samba</i> 323# <i>emerge net-fs/samba</i>
342</pre> 324</pre>
343 325
344<note> 326<note>
345The following archs will need to add <e>~</e> to their <e>KEYWORDS</e>: x86, 327The following archs will need to add <e>~</e> to their <e>KEYWORDS</e>: x86,
346ppc, sparc, hppa, ia64 and alpha 328ppc, sparc, hppa, ia64 and alpha
351</p> 333</p>
352 334
353</body> 335</body>
354</section> 336</section>
355<section> 337<section>
356<title>Emerging Clam AV</title> 338<title>Emerging ClamAV</title>
357<body> 339<body>
358 340
359<p> 341<p>
360Because the <e>oav</e> USE flag only provides an interface to allow on access 342Because the <e>oav</e> USE flag only provides an interface to allow on access
361virus scanning, the actual virus scanner must be emerged. The scanner 343virus scanning, the actual virus scanner must be emerged. The scanner
362used in this HOWTO is Clam AV. 344used in this HOWTO is ClamAV.
363</p> 345</p>
364 346
365<pre caption="Emerge clam-av"> 347<pre caption="Emerge Clamav">
366# <i>emerge app-antivirus/clamav</i> 348# <i>emerge app-antivirus/clamav</i>
367</pre> 349</pre>
368 350
369</body> 351</body>
370</section> 352</section>
377</pre> 359</pre>
378 360
379</body> 361</body>
380</section> 362</section>
381<section> 363<section>
382<title>Emerging net-print/hpijs</title> 364<title>Emerging net-print/hplip</title>
383<body> 365<body>
384 366
385<p> 367<p>
386You only need to emerge this if you use an HP printer. 368You only need to emerge this if you use an HP printer.
387</p> 369</p>
388 370
389<pre caption="Emerge hpijs"> 371<pre caption="Emerge hplip">
390# <i>emerge net-print/hpijs</i> 372# <i>emerge net-print/hplip</i>
391</pre> 373</pre>
392 374
393</body> 375</body>
394</section> 376</section>
395</chapter> 377</chapter>
413<pre caption="A Sample /etc/samba/smb.conf"> 395<pre caption="A Sample /etc/samba/smb.conf">
414[global] 396[global]
415<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment> 397<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment>
416workgroup = <comment>MYWORKGROUPNAME</comment> 398workgroup = <comment>MYWORKGROUPNAME</comment>
417<comment># Of course this has no REAL purpose other than letting 399<comment># Of course this has no REAL purpose other than letting
418# everyone know its not Windows! 400# everyone knows it's not Windows!
419# %v prints the version of Samba we are using.</comment> 401# %v prints the version of Samba we are using.</comment>
420server string = Samba Server %v 402server string = Samba Server %v
421<comment># We are going to use cups, so we are going to put it in here ;-)</comment> 403<comment># We are going to use cups, so we are going to put it in here ;-)</comment>
422printcap name = cups 404printcap name = cups
423printing = cups 405printing = cups
446<comment># We now will implement the on access virus scanner. 428<comment># We now will implement the on access virus scanner.
447# NOTE: By putting this in our [Global] section, we enable 429# NOTE: By putting this in our [Global] section, we enable
448# scanning of ALL shares, you could optionally move 430# scanning of ALL shares, you could optionally move
449# these to a specific share and only scan it.</comment> 431# these to a specific share and only scan it.</comment>
450 432
451<comment># For Samba 3.x</comment> 433<comment># For Samba 3.x. This enables ClamAV on access scanning.</comment>
452vfs object = vscan-clamav 434vfs object = vscan-clamav
453vscan-clamav: config-file = /etc/samba/vscan-clamav.conf 435vscan-clamav: config-file = /etc/samba/vscan-clamav.conf
454
455<comment># For Samba 2.2.x</comment>
456vfs object = /usr/lib/samba/vfs/vscan-clamav.so
457vfs options = config-file = /etc/samba/vscan-clamav.conf
458 436
459<comment># Now we setup our print drivers information!</comment> 437<comment># Now we setup our print drivers information!</comment>
460[print$] 438[print$]
461comment = Printer Drivers 439comment = Printer Drivers
462path = /etc/samba/printer <comment># this path holds the driver structure</comment> 440path = /etc/samba/printer <comment># this path holds the driver structure</comment>
515printer user, like <c>printeruser</c> or <c>printer</c> or 493printer user, like <c>printeruser</c> or <c>printer</c> or
516<c>printme</c> or whatever. It doesn't hurt and it will certainly 494<c>printme</c> or whatever. It doesn't hurt and it will certainly
517protect you from a lot of problems. 495protect you from a lot of problems.
518</warn> 496</warn>
519 497
498<warn>
499Turning on ClamAV on access scanning in the <c>[global]</c> section will slow
500down the performance of your Samba server dramatically.
501</warn>
502
520<p> 503<p>
521Now create the directories required for the minimum configuration of 504Now create the directories required for the minimum configuration of
522Samba to share the installed printer throughout the network. 505Samba to share the installed printer throughout the network.
523</p> 506</p>
524 507
558</pre> 541</pre>
559 542
560</body> 543</body>
561</section> 544</section>
562<section> 545<section>
563<title>Configuring Clam AV</title> 546<title>Configuring ClamAV</title>
564<body> 547<body>
565 548
566<p> 549<p>
567The configuration file specified to be used in <path>smb.conf</path> is 550The configuration file specified to be used in <path>smb.conf</path> is
568<path>/etc/samba/vscan-clamav.conf</path>. While these options are set 551<path>/etc/samba/vscan-clamav.conf</path>. While these options are set
624<comment>; an entry is invalidated after lru file entry lifetime (in seconds). 607<comment>; an entry is invalidated after lru file entry lifetime (in seconds).
625; (Default: 5)</comment> 608; (Default: 5)</comment>
626lru file entry lifetime = 5 609lru file entry lifetime = 5
627 610
628<comment>; socket name of clamd (default: /var/run/clamd)</comment> 611<comment>; socket name of clamd (default: /var/run/clamd)</comment>
629clamd socket name = /var/run/clamd 612clamd socket name = /tmp/clamd
613
614<comment>; port number the ScannerDaemon listens on</comment>
615oav port = 8127
630</pre> 616</pre>
631 617
632<p> 618<p>
633It is generally a good idea to start the virus scanner immediately. Add 619It is generally a good idea to start the virus scanner immediately. Add
634it to the <e>default</e> runlevel and then start the <c>clamd</c> service immediately. 620it to the <e>default</e> runlevel and then start the <c>clamd</c> service
621immediately. The service has two processes: freshclam keeps the virus definition
622database up to date while clamd is the actual anti-virus daemon. First you may
623want to set the paths of the logfiles so that it fits your needs.
624</p>
625
626<pre caption="Checking the location of the logfiles">
627# <i>vim /etc/clamd.conf</i>
628<comment>(Check the line "LogFile /var/log/clamd.log")</comment>
629# <i>vim /etc/freshclam.conf</i>
630<comment>(Check the line "UpdateLogFile /var/log/freshclam.log")</comment>
631# <i>vim /etc/conf.d/clamd</i>
632<comment>(Set "START_CLAMD=yes" and "START_FRESHCLAM=yes")</comment>
633</pre>
634
635<p>
636Now fire up the virus scanner.
635</p> 637</p>
636 638
637<pre caption="Add clamd to bootup and start it"> 639<pre caption="Add clamd to bootup and start it">
638# <i>rc-update add clamd default</i> 640# <i>rc-update add clamd default</i>
639# <i>/etc/init.d/clamd start</i> 641# <i>/etc/init.d/clamd start</i>
652in the example are the directives that need to be changed: 654in the example are the directives that need to be changed:
653</p> 655</p>
654 656
655<pre caption="/etc/cups/cupsd.conf"> 657<pre caption="/etc/cups/cupsd.conf">
656ServerName <i>PrintServer</i> <comment># your printserver name</comment> 658ServerName <i>PrintServer</i> <comment># your printserver name</comment>
657ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, eg you</comment> 659ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment>
658 660
659AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment> 661AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment>
660ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment> 662ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment>
661 663
662LogLevel debug <comment># only while isntalling and testing, should later be 664LogLevel debug <comment># only while isntalling and testing, should later be
663 # changed to 'info'</comment> 665 # changed to 'info'</comment>
664 666
665MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back, 667MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back,
666 # there seemed to be a bug in CUPS' controlling of the web interface, 668 # there seemed to be a bug in CUPS' controlling of the web interface,
667 # making CUPS think a denial of service attack was in progress when 669 # making CUPS think a denial of service attack was in progress when
668 # I tried to configure a printer with the web interface. weird.</comment> 670 # I tried to configure a printer with the web interface. weird.</comment>
671 673
672&lt;Location /&gt; 674&lt;Location /&gt;
673Order Deny,Allow 675Order Deny,Allow
674Deny From All 676Deny From All
675Allow From <i>192.168.1.*</i> <comment># the addresses of your internel network 677Allow From <i>192.168.1.*</i> <comment># the addresses of your internel network
676 # eg 192.168.1.* will allow connections from any host on 678 # e.g. 192.168.1.* will allow connections from any host on
677 # the 192.168.1.0 network. change to whatever suits you</comment> 679 # the 192.168.1.0 network. change to whatever suits you</comment>
678&lt;/Location&gt; 680&lt;/Location&gt;
679 681
680&lt;Location /admin&gt; 682&lt;Location /admin&gt;
681AuthType Basic 683AuthType Basic
727 729
728<p> 730<p>
729First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to 731First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to
730find and download the correct PPD file for your printer and CUPS. To do so, 732find and download the correct PPD file for your printer and CUPS. To do so,
731click the link Printer Listings to the left. Select your printers manufacturer 733click the link Printer Listings to the left. Select your printers manufacturer
732and the model in the pulldown menu, eg HP and DeskJet 930C. Click "Show". On 734and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On
733the page coming up click the "recommended driver" link after reading the 735the page coming up click the "recommended driver" link after reading the
734various notes and information. Then fetch the PPD file from the next page, 736various notes and information. Then fetch the PPD file from the next page,
735again after reading the notes and introductions there. You may have to select 737again after reading the notes and introductions there. You may have to select
736your printers manufacturer and model again. Reading the <uri 738your printers manufacturer and model again. Reading the <uri
737link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> 739link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri>
746interface is found at <path>http://PrintServer:631</path> once CUPS is running. 748interface is found at <path>http://PrintServer:631</path> once CUPS is running.
747</p> 749</p>
748 750
749<pre caption="Install the printer via command line"> 751<pre caption="Install the printer via command line">
750# <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i> 752# <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i>
753# <i>/etc/init.d/cupsd restart</i>
751</pre> 754</pre>
752 755
753<p> 756<p>
754Remember to adjust to what you have. Be sure to have the name 757Remember to adjust to what you have. Be sure to have the name
755(<c>-p</c> argument) right (the name you set above during the Samba 758(<c>-p</c> argument) right (the name you set above during the Samba
777drivers automagically to the connecting client, avoiding the hassle of 780drivers automagically to the connecting client, avoiding the hassle of
778manually installing printer drivers locally. 781manually installing printer drivers locally.
779</p> 782</p>
780 783
781<p> 784<p>
782There are two sets of printer drivers for this. First, the Adobe PS 785There are two sets of printer drivers for this. First, the Adobe PS drivers
783drivers which can be obtained from <uri 786which can be obtained from <uri
784link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> 787link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript
785(PostScript printer drivers). Second, there are the CUPS PS drivers, 788printer drivers). Second, there are the CUPS PS drivers, to be obtained <uri
786to be obtained from <uri link="http://www.cups.org/software.php">the 789link="http://dev.gentoo.org/~nightmorph/misc/cups-samba-5.0rc2.tar.gz">here</uri>.
787CUPS homepage</uri> and selecting "CUPS Driver for Windows" from the 790There doesn't seem to be a difference between the functionality of the two, but
788pull down menu. There doesn't seem to be a difference between the 791the Adobe PS drivers need to be extracted on a Windows System since it's a
789functionality of the two, but the Adobe PS drivers need to be extracted 792Windows binary. Also the whole procedure of finding and copying the correct
790on a Windows System since it's a Windows binary. Also the whole procedure 793files is a bit more hassle. The CUPS drivers seem to support some options the
791of finding and copying the correct files is a bit more hassle. The CUPS 794Adobe drivers don't.
792drivers seem to support some options the Adobe drivers don't.
793</p> 795</p>
796<!--
797used to be available at www.cups.org/articles.php?L142+p4, but only 6.0 is
798available. at some point, we should update this for 6.0.
799-->
794 800
795<p> 801<p>
796This HOWTO uses the CUPS drivers for Windows. The downloaded file is 802This HOWTO uses the CUPS drivers for Windows. The downloaded file is
797called <path>cups-samba-5.0rc2.tar.gz</path>. Extract the files 803called <path>cups-samba-5.0rc2.tar.gz</path>. Extract the files
798contained into a directory. 804contained into a directory.
810<path>cups5.hlp</path>, <path>cupsdrvr5.dll</path> and 816<path>cups5.hlp</path>, <path>cupsdrvr5.dll</path> and
811<path>cupsui5.dll</path>. These are the actual driver files. 817<path>cupsui5.dll</path>. These are the actual driver files.
812</p> 818</p>
813 819
814<warn> 820<warn>
815The script <c>cups-samba.install</c> may not work for all *nixes (ie FreeBSD) 821The script <c>cups-samba.install</c> may not work for all *nixes (i.e. FreeBSD)
816because almost everything which is not part of the base system is 822because almost everything which is not part of the base system is
817installed somewhere under the prefix <path>/usr/local/</path>. This 823installed somewhere under the prefix <path>/usr/local/</path>. This
818seems not to be the case for most things you install under GNU/Linux. 824seems not to be the case for most things you install under GNU/Linux.
819However, if your CUPS installation is somewhere other than 825However, if your CUPS installation is somewhere other than
820<path>/usr/share/cups/</path> see the example below. 826<path>/usr/share/cups/</path> see the example below.
831# <i>tar -xf cups-samba.ss</i> 837# <i>tar -xf cups-samba.ss</i>
832<comment>(This extracts the files to usr/share/cups/drivers under the CURRENT WORKING DIRECTORY)</comment> 838<comment>(This extracts the files to usr/share/cups/drivers under the CURRENT WORKING DIRECTORY)</comment>
833# <i>cd usr/share/cups/drivers</i> 839# <i>cd usr/share/cups/drivers</i>
834<comment>(no leading / !)</comment> 840<comment>(no leading / !)</comment>
835# <i>cp cups* /usr/local/share/cups/drivers</i> 841# <i>cp cups* /usr/local/share/cups/drivers</i>
842# <i>/etc/init.d/cupsd restart</i>
836</pre> 843</pre>
837 844
838<p> 845<p>
839Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS 846Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution.
840distribution. It's man page is an interesting read. 847Its man page is an interesting read.
841</p> 848</p>
842 849
843<pre caption="Run cupsaddsmb"> 850<pre caption="Run cupsaddsmb">
844# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i> 851# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i>
845<comment>(Instead of HPDeskJet930C you could also specify "-a", which will 852<comment>(Instead of HPDeskJet930C you could also specify "-a", which will
846"export all known printers".)</comment> 853"export all known printers".)</comment>
847# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -a</i> 854# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -a</i>
848</pre> 855</pre>
849 856
850<warn> 857<warn>
851The execution of this command often causes the most trouble. 858The execution of this command often causes the most trouble. Read through the
852Reading through the <uri
853link="http://forums.gentoo.org/viewtopic.php?t=110931">posts in this 859<uri link="http://forums.gentoo.org/viewtopic.php?t=110931">posts in this
854thread</uri>. 860thread</uri> for some troubleshooting tips.
855</warn> 861</warn>
856 862
857<p> 863<p>
858Here are common errors that may happen: 864Here are common errors that may happen:
859</p> 865</p>
1117troubleshooting your installation: 1123troubleshooting your installation:
1118</p> 1124</p>
1119 1125
1120<ul> 1126<ul>
1121 <li><uri link="http://www.cups.org/">CUPS Homepage</uri></li> 1127 <li><uri link="http://www.cups.org/">CUPS Homepage</uri></li>
1128 <li>
1122 <li><uri link="http://www.samba.org/">Samba Homepage</uri></li> 1129 <uri link="http://www.samba.org/">Samba Homepage</uri>, especially the <uri
1130 link="http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/CUPS-printing.html">chapter
1131 on Samba/CUPS configuration</uri>
1132 </li>
1123 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li> 1133 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li>
1124 <li> 1134 <li>
1125 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt 1135 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt
1126 Pfeifle's Samba Print HOWTO</uri> ( 1136 Pfeifle's Samba Print HOWTO</uri> (
1127 This HOWTO really covers <e>ANYTHING</e> and <e>EVERYTHING</e> 1137 This HOWTO really covers <e>ANYTHING</e> and <e>EVERYTHING</e>

Legend:
Removed from v.1.14  
changed lines
  Added in v.1.28

  ViewVC Help
Powered by ViewVC 1.1.20