/[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.2 Revision 1.10
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.10 2004/08/11 14:34:34 swift 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="quick-samba-howto.xml">
4<title>Gentoo Samba3/CUPS/clamav HOWTO</title> 5<title>Gentoo Samba3/CUPS/Clam AV 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>
13Setup, install and configure a Samba Server under Gentoo that shares 14Setup, install and configure a Samba Server under Gentoo that shares
14files, printers without the need to install drivers and provides 15files, printers without the need to install drivers and provides
15automatic virus scanning. 16automatic virus 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.2</version> 23<version>1.7</version>
23<date>May 13, 2004</date> 24<date>August 11, 2004</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>
32This HOWTO is designed to help you move a network from many different 33This HOWTO is designed to help you move a network from many different
33clients speaking different languages, to many different manchines that 34clients speaking different languages, to many different machines that
34speak a common language. The ultimate goal is to help differing 35speak a common language. The ultimate goal is to help differing
35architechures and technologies, come together in a productive, 36architectures and technologies, come together in a productive,
36happily coexistant environment. 37happily coexisting environment.
37</p> 38</p>
38 39
39<p> 40<p>
40Following the directions outlined in this HOWTO should give you an 41Following the directions outlined in this HOWTO should give you an
41excellent step towards a peaceful cohabitation between Windows, and 42excellent step towards a peaceful cohabitation between Windows, and
85<section> 86<section>
86<title>Before you use this guide</title> 87<title>Before you use this guide</title>
87<body> 88<body>
88 89
89<p> 90<p>
90There are a several other guides for setting up CUPS and/or Samba, 91There are a several other guides for setting up CUPS and/or Samba, please read
91please read them as well, as they may tell you things left out of this 92them as well, as they may tell you things left out of this HOWTO (intentional
92HOWTO (intentional or otherwise). One such document is the very useful 93or otherwise). One such document is the very useful and well written <uri
93and well written <uri link="http://www.gentoo.org/doc/en/printing-howto.xml">Gentoo 94link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration
94Printing Guide</uri>, as configuration issues and specific printer setup 95issues and specific printer setup is not discussed here.
95is not discussed here.
96</p> 96</p>
97 97
98</body> 98</body>
99</section> 99</section>
100<section> 100<section>
141We will need the following: 141We will need the following:
142</p> 142</p>
143 143
144<ul> 144<ul>
145 <li>net-fs/samba</li> 145 <li>net-fs/samba</li>
146 <li>net-mail/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/hpijs (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 (preferably 2.4.24+ or 2.6.x)</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>
156 156
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.
161net-mail/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.
163</p> 163</p>
164 164
165</body> 165</body>
166</section> 166</section>
167</chapter> 167</chapter>
168
168<chapter> 169<chapter>
169<title>Getting acquainted with Samba</title> 170<title>Getting acquainted with Samba</title>
170<section> 171<section>
171<title>The USE Flags</title> 172<title>The USE Flags</title>
172<body> 173<body>
300</ul> 301</ul>
301 302
302</body> 303</body>
303</section> 304</section>
304</chapter> 305</chapter>
306
305<chapter> 307<chapter>
306<title>Server Software Installation</title> 308<title>Server Software Installation</title>
307<section> 309<section>
308<title>Emerging Samba</title> 310<title>Emerging Samba</title>
309<body> 311<body>
310 312
311<p> 313<p>
312First of all: be sure that all your hostnames resolve correctly. 314First of all: be sure that all your hostnames resolve correctly.
313Either have a working domain name system running on your network 315Either have a working domain name system running on your network
314or appropriate entries in your /etc/hosts file. cupsaddsmb often 316or appropriate entries in your <path>/etc/hosts</path> file.
315borks if hostnames don't point to the correct machines. 317<c>cupsaddsmb</c> often borks if hostnames don't point to the correct
318machines.
316</p> 319</p>
317 320
318<p> 321<p>
319Hopefully now you can make an assessment of what you'll actually need in 322Hopefully now you can make an assessment of what you'll actually need in
320order to use Samba with your particular setup. The setup used for this 323order to use Samba with your particular setup. The setup used for this
348</p> 351</p>
349 352
350</body> 353</body>
351</section> 354</section>
352<section> 355<section>
353<title>Emerging clam-av</title> 356<title>Emerging Clam AV</title>
354<body> 357<body>
355 358
356<p> 359<p>
357Because the oav USE flag only provides an interface to allow on access 360Because the <e>oav</e> USE flag only provides an interface to allow on access
358virus scanning, the actual virus scanner must be emerged. The scanner 361virus scanning, the actual virus scanner must be emerged. The scanner
359used in this HOWTO is <e>net-mail/clamav</e>. 362used in this HOWTO is Clam AV.
360</p> 363</p>
361 364
362<pre caption="Emerge clam-av"> 365<pre caption="Emerge clam-av">
363# <i>emerge net-mail/clamav</i> 366# <i>emerge app-antivirus/clamav</i>
364</pre> 367</pre>
365 368
366</body> 369</body>
367</section> 370</section>
368<section> 371<section>
388</pre> 391</pre>
389 392
390</body> 393</body>
391</section> 394</section>
392</chapter> 395</chapter>
396
393<chapter> 397<chapter>
394<title>Server Configuration</title> 398<title>Server Configuration</title>
395<section> 399<section>
396<title>Configuring Samba</title> 400<title>Configuring Samba</title>
397<body> 401<body>
399<p> 403<p>
400The main Samba configuration file is <path>/etc/samba/smb.conf</path>. 404The main Samba configuration file is <path>/etc/samba/smb.conf</path>.
401It is divided in sections indicated by [sectionname]. Comments are either 405It is divided in sections indicated by [sectionname]. Comments are either
402# or ;. A sample <path>smb.conf</path> is included below with comments and 406# or ;. A sample <path>smb.conf</path> is included below with comments and
403suggestions for modifications. If more details are required, see the 407suggestions for modifications. If more details are required, see the
404man page for <path>smb.conf</path>, the installed smb.conf.example, the Samba 408man page for <path>smb.conf</path>, the installed
405Web site or any of the numerous Samba books available. 409<path>smb.conf.example</path>, the Samba Web site or any of the
410numerous Samba books available.
406</p> 411</p>
407 412
408<pre caption="A Sample /etc/samba/smb.conf"> 413<pre caption="A Sample /etc/samba/smb.conf">
409[global] 414[global]
410<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment> 415<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment>
440guest ok = yes 445guest ok = yes
441<comment># We now will implement the on access virus scanner. 446<comment># We now will implement the on access virus scanner.
442# NOTE: By putting this in our [Global] section, we enable 447# NOTE: By putting this in our [Global] section, we enable
443# scanning of ALL shares, you could optionally move 448# scanning of ALL shares, you could optionally move
444# these to a specific share and only scan it.</comment> 449# these to a specific share and only scan it.</comment>
450
451<comment># For Samba 3.x</comment>
452vfs object = vscan-clamav
453vscan-clamav: config-file = /etc/samba/vscan-clamav.conf
454
455<comment># For Samba 2.2.x</comment>
445vfs object = /usr/lib/samba/vfs/vscan-clamav.so 456vfs object = /usr/lib/samba/vfs/vscan-clamav.so
446vfs options = config-file = /etc/samba/vscan-clamav.conf 457vfs options = config-file = /etc/samba/vscan-clamav.conf
447 458
448<comment># Now we setup our print drivers information!</comment> 459<comment># Now we setup our print drivers information!</comment>
449[print$] 460[print$]
450comment = Printer Drivers 461comment = Printer Drivers
451path = /etc/samba/printer <comment># this path holds the driver structure</comment> 462path = /etc/samba/printer <comment># this path holds the driver structure</comment>
452guest ok = no 463guest ok = yes
453browseable = yes 464browseable = yes
454read only = yes 465read only = yes
455<comment># Modify this to "username,root" if you don't want root to 466<comment># Modify this to "username,root" if you don't want root to
456# be the only printer admin)</comment> 467# be the only printer admin)</comment>
457write list = <i>root</i> 468write list = <i>root</i>
470 481
471<comment># Now we setup our printers share. This should be 482<comment># Now we setup our printers share. This should be
472# browseable, printable, public.</comment> 483# browseable, printable, public.</comment>
473[printers] 484[printers]
474comment = All Printers 485comment = All Printers
475browseable = yes 486browseable = no
476printable = yes 487printable = yes
488writable = no
477public = yes 489public = yes
478guest ok = yes 490guest ok = yes
479path = /var/spool/samba 491path = /var/spool/samba
480<comment># Modify this to "username,root" if you don't want root to 492<comment># Modify this to "username,root" if you don't want root to
481# be the only printer admin)</comment> 493# be the only printer admin)</comment>
491create mode = 0766 503create mode = 0766
492guest ok = yes 504guest ok = yes
493path = /home/samba/public 505path = /home/samba/public
494</pre> 506</pre>
495 507
496<p> 508<warn>
497There are several warnings that we should put here:
498</p>
499
500<ul>
501 <li>
502 If you like to use Samba's guest account to do anything concerning 509If you like to use Samba's guest account to do anything concerning
503 printing from Windows clients: don't 510printing from Windows clients: don't set <c>guest only = yes</c> in
504 </li> 511the <c>[global]</c> section. The guest account seems to cause
505 <li>Don't set guest only = yes in the global section</li> 512problems when running <c>cupsaddsmb</c> sometimes when trying to
506 <li>
507 The guest account seems to cause problems when running cupsaddsmb sometimes
508 when trying to connect from Windows machines. See below, too, when we talk 513connect from Windows machines. See below, too, when we talk about
509 about cupsaddsmb and the problems that can arise. Use a dedicated printer 514<c>cupsaddsmb</c> and the problems that can arise. Use a dedicated
510 user, like "printeruser" or "printer" or "printme" or whatever. It doesn't 515printer user, like <c>printeruser</c> or <c>printer</c> or
511 hurt and it will certainly protect you from a lot of problems. 516<c>printme</c> or whatever. It doesn't hurt and it will certainly
512 </li> 517protect you from a lot of problems.
513</ul> 518</warn>
514 519
515<p> 520<p>
516Now create the directories required for the minimum configuration of 521Now create the directories required for the minimum configuration of
517Samba to share the installed printer throughout the network. 522Samba to share the installed printer throughout the network.
518</p> 523</p>
539<p> 544<p>
540The Samba passwords need not be the same as the system passwords 545The Samba passwords need not be the same as the system passwords
541in <path>/etc/passwd</path>. 546in <path>/etc/passwd</path>.
542</p> 547</p>
543 548
549<p>
550You will also need to update <path>/etc/nsswitch.conf</path> so that Windows
551systems can be found easily using NetBIOS:
552</p>
553
554<pre caption="Editing /etc/nsswitch.conf">
555# <i>nano -w /etc/nsswitch.conf</i>
556<comment>(Edit the hosts: line)</comment>
557hosts: files dns <i>wins</i>
558</pre>
559
544</body> 560</body>
545</section>
546<section> 561</section>
562<section>
547<title>Configuring clam-av</title> 563<title>Configuring Clam AV</title>
548<body> 564<body>
549 565
550<p> 566<p>
551The configuration file specified to be used in <path>smb.conf</path> is 567The configuration file specified to be used in <path>smb.conf</path> is
552<path>/etc/samba/vscan-clamav.conf</path>. While these options are set 568<path>/etc/samba/vscan-clamav.conf</path>. While these options are set
575 591
576<comment>; if communication to clamd fails, should access to file denied? 592<comment>; if communication to clamd fails, should access to file denied?
577; (default: yes)</comment> 593; (default: yes)</comment>
578deny access on error = yes 594deny access on error = yes
579 595
580<comment>; if daemon files with a minor error (corruption, etc.), 596<comment>; if daemon fails with a minor error (corruption, etc.),
581; should access to file denied? 597; should access to file denied?
582; (default: yes)</comment> 598; (default: yes)</comment>
583deny access on minor error = yes 599deny access on minor error = yes
584 600
585<comment>; send a warning message via Windows Messenger service 601<comment>; send a warning message via Windows Messenger service
603; of period, samba-vscan use a last recently used file mechanism to avoid 619; of period, samba-vscan use a last recently used file mechanism to avoid
604; multiple scans of a file. This setting specified the maximum number of 620; multiple scans of a file. This setting specified the maximum number of
605; elements of the last recently used file list. (default: 100)</comment> 621; elements of the last recently used file list. (default: 100)</comment>
606max lru files entries = 100 622max lru files entries = 100
607 623
608<comment>; an entry is invalidad after lru file entry lifetime (in seconds). 624<comment>; an entry is invalidated after lru file entry lifetime (in seconds).
609; (Default: 5)</comment> 625; (Default: 5)</comment>
610lru file entry lifetime = 5 626lru file entry lifetime = 5
611 627
612<comment>; socket name of clamd (default: /var/run/clamd)</comment> 628<comment>; socket name of clamd (default: /var/run/clamd)</comment>
613clamd socket name = /var/run/clamd 629clamd socket name = /var/run/clamd
614</pre> 630</pre>
615 631
616<p> 632<p>
617It is generally a good idea to start the virus scanner immediately. Add 633It is generally a good idea to start the virus scanner immediately. Add
618it to the default runlevel and then start the clamd service immediately. 634it to the <e>default</e> runlevel and then start the <c>clamd</c> service immediately.
619</p> 635</p>
620 636
621<pre caption="Add clamd to bootup and start it"> 637<pre caption="Add clamd to bootup and start it">
622# <i>rc-update add clamd default</i> 638# <i>rc-update add clamd default</i>
623# <i>/etc/init.d/clamd start</i> 639# <i>/etc/init.d/clamd start</i>
628<section> 644<section>
629<title>Configuring CUPS</title> 645<title>Configuring CUPS</title>
630<body> 646<body>
631 647
632<p> 648<p>
633This is a little more complicated). CUPS' main config file is 649This is a little more complicated. CUPS' main config file is
634<path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's 650<path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's
635<path>httpd.conf</path> file, so many you may find it familiar. Outlined 651<path>httpd.conf</path> file, so many you may find it familiar. Outlined
636in the example are the directives that need to be changed: 652in the example are the directives that need to be changed:
637</p> 653</p>
638 654
672&lt;/Location&gt; 688&lt;/Location&gt;
673</pre> 689</pre>
674 690
675<p> 691<p>
676Edit <path>/etc/cups/mime.convs</path> to uncomment some lines. 692Edit <path>/etc/cups/mime.convs</path> to uncomment some lines.
677The changes to mime.convs and mime.types are needed to make CUPSprint Microsoft Office document files. 693The changes to <path>mime.convs</path> and <path>mime.types</path> are
694needed to make CUPS print Microsoft Office document files.
678</p> 695</p>
679 696
680<pre caption="/etc/cups/mime.convs"> 697<pre caption="/etc/cups/mime.convs">
681<comment>(The following line is found near the end of the file. Uncomment it)</comment> 698<comment>(The following line is found near the end of the file. Uncomment it)</comment>
682application/octet-stream application/vnd.cups-raw 0 699application/octet-stream application/vnd.cups-raw 0
709<section> 726<section>
710<title>Installing a printer for and with CUPS</title> 727<title>Installing a printer for and with CUPS</title>
711<body> 728<body>
712 729
713<p> 730<p>
714First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> 731First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to
715to find and download the correct PPD file for your printer and CUPS. To 732find and download the correct PPD file for your printer and CUPS. To do so,
716do so, click the link Printer Listings to the left. Select your 733click the link Printer Listings to the left. Select your printers manufacturer
717printers manufacturer and the model in the pulldown menu, eg HP and 734and the model in the pulldown menu, eg HP and DeskJet 930C. Click "Show". On
718DeskJet 930C. Click "Show". On the page coming up click the "recommended 735the page coming up click the "recommended driver" link after reading the
719driver" link after reading the various notes and information. Then fetch 736various notes and information. Then fetch the PPD file from the next page,
720the PPD file from the next page, again after reading the notes and 737again after reading the notes and introductions there. You may have to select
721introductions there. You may have to select your printers manufacturer 738your printers manufacturer and model again. Reading the <uri
722and model again. Reading the <uri link="http://www.linuxprinting.org/cups-doc.html">CUPS 739link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri>
723quickstart guide</uri> is also very helpful when working with CUPS. 740is also very helpful when working with CUPS.
724</p> 741</p>
725 742
726<p> 743<p>
727Now you have a PPD file for your printer to work with CUPS. Place it in 744Now you have a PPD file for your printer to work with CUPS. Place it in
728<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was 745<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was
729named HP-DeskJet_930C-hpijs.ppd. You should now install the printer. 746named <path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer.
730This can be done via the CUPS web interface or via command line. The web 747This can be done via the CUPS web interface or via command line. The web
731interface is found at http://PrintServer:631 once CUPS is running. 748interface is found at <path>http://PrintServer:631</path> once CUPS is running.
732</p> 749</p>
733 750
734<pre caption="Install the printer via command line"> 751<pre caption="Install the printer via command line">
735# <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>
736</pre> 753</pre>
737 754
738<p> 755<p>
739Remember to adjust to what you have. Be sure to have the name (-p) right (the 756Remember to adjust to what you have. Be sure to have the name
740name you set above during the Samba configuration!) and to put in the 757(<c>-p</c> argument) right (the name you set above during the Samba
741correct usb:/dev/usb/blah, parallel:/dev/blah or whatever device you 758configuration!) and to put in the correct <c>usb:/dev/usb/blah</c>,
742are using for your printer. 759<c>parallel:/dev/blah</c> or whatever device you are using for your
743</p> 760printer.
744
745<p> 761</p>
762
763<p>
746You should now be able to access the printer from the web interface. You 764You should now be able to access the printer from the web interface
747should now be able to print a test page. 765and be able to print a test page.
748</p> 766</p>
749 767
750</body> 768</body>
751</section> 769</section>
752<section> 770<section>
788<comment>(Only use this script if CUPS resides in /usr/share/cups)</comment> 806<comment>(Only use this script if CUPS resides in /usr/share/cups)</comment>
789# <i>./cups-samba.install</i> 807# <i>./cups-samba.install</i>
790</pre> 808</pre>
791 809
792<p> 810<p>
793cups-samba.ss is a TAR archive containing three files: 811<path>cups-samba.ss</path> is a TAR archive containing three files:
794cups5.hlp, cupsdrvr5.dll and cupsui5.dll. These are the actual driver 812<path>cups5.hlp</path>, <path>cupsdrvr5.dll</path> and
795files. 813<path>cupsui5.dll</path>. These are the actual driver files.
796</p> 814</p>
797 815
798<warn> 816<warn>
799The script cups-samba.install may not work for all *nixes (ie FreeBSD) 817The script <c>cups-samba.install</c> may not work for all *nixes (ie FreeBSD)
800because almost everything which is not part of the base system is 818because almost everything which is not part of the base system is
801installed somewhere under the prefix <path>/usr/local/</path>. This 819installed somewhere under the prefix <path>/usr/local/</path>. This
802seems not to be the case for most things you install under GNU/Linux. 820seems not to be the case for most things you install under GNU/Linux.
803However, if your CUPS installation is somewhere other than 821However, if your CUPS installation is somewhere other than
804<path>/usr/share/cups/</path> See the example below. 822<path>/usr/share/cups/</path> see the example below.
805</warn> 823</warn>
806 824
807<p> 825<p>
808Suppose your CUPS installation resides under 826Suppose your CUPS installation resides under
809<path>/usr/local/share/cups/</path>, and you want to install the drivers there. 827<path>/usr/local/share/cups/</path>, and you want to install the drivers there.
832</pre> 850</pre>
833 851
834<warn> 852<warn>
835The execution of this command often causes the most trouble. 853The execution of this command often causes the most trouble.
836Reading through the <uri 854Reading through the <uri
837link="http://forums.gentoo.com/viewtopic.php?t=110931">posts in this 855link="http://forums.gentoo.org/viewtopic.php?t=110931">posts in this
838thread</uri>. 856thread</uri>.
839</warn> 857</warn>
840 858
841<p> 859<p>
842Here are common errors that may happen: 860Here are common errors that may happen:
843</p> 861</p>
844 862
845<ul> 863<ul>
846 <li> 864 <li>
847 The hostname given as a parameter for -h and -H (PrintServer) often does 865 The hostname given as a parameter for <c>-h</c> and <c>-H</c>
848 not resolve correctly and doesn't identify the print server for CUPS/Samba 866 (<c>PrintServer</c>) often does not resolve correctly and doesn't
849 interaction. 867 identify the print server for CUPS/Samba interaction. If an error
850 If an error like: <b>Warning: No PPD file for printer "CUPS_PRINTER_NAME" - 868 like: <b>Warning: No PPD file for printer "CUPS_PRINTER_NAME" -
851 skipping!</b> occurs, the first thing you should do is substitute 869 skipping!</b> occurs, the first thing you should do is substitute
852 PrintServer with localhost and try it again. 870 <c>PrintServer</c> with <c>localhost</c> and try it again.
853 </li> 871 </li>
854 <li> 872 <li>
855 The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message 873 The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message
856 is quite common, but can be triggered by many problems. It's unfortunately 874 is quite common, but can be triggered by many problems. It's unfortunately
857 not very helpful. One thing to try is to temporarily set <b>security = 875 not very helpful. One thing to try is to temporarily set <c>security =
858 user</b> in your <path>smb.conf</path>. After/if the installation completes 876 user</c> in your <path>smb.conf</path>. After/if the installation completes
859 successfully, you should set it back to share, or whatever it was set to 877 successfully, you should set it back to share, or whatever it was set to
860 before. 878 before.
861 </li> 879 </li>
862</ul> 880</ul>
863 881
952</pre> 970</pre>
953 971
954</body> 972</body>
955</section> 973</section>
956</chapter> 974</chapter>
975
957<chapter> 976<chapter>
958<title>Configuration of the Clients</title> 977<title>Configuration of the Clients</title>
959<section> 978<section>
960<title>Printer configuration of *nix based clients</title> 979<title>Printer configuration of *nix based clients</title>
961<body> 980<body>
963<p> 982<p>
964Despite the variation or distribution, the only thing needed is CUPS. 983Despite the variation or distribution, the only thing needed is CUPS.
965Do the equivalent on any other UNIX/Linux/BSD client. 984Do the equivalent on any other UNIX/Linux/BSD client.
966</p> 985</p>
967 986
968<pre caption="Configuring a Gentoo system."> 987<pre caption="Configuring a Gentoo system">
969# <i>emerge cups</i> 988# <i>emerge cups</i>
970# <i>/etc/init.d/cupsd start</i> 989# <i>/etc/init.d/cupsd start</i>
971# <i>rc-update add cupsd default</i> 990# <i>rc-update add cupsd default</i>
972</pre> 991</pre>
973 992
974<p> 993<p>
975That should be it. Nothing else will be needed. Just point your web 994That should be it. Nothing else will be needed. Just point your web
976browser to http://localhost:631 (on the CLIENT) and you'll see that 995browser to <c>http://localhost:631</c> on the client and you'll see that
977PrintServer broadcasts all available printers to all CUPS clients. 996PrintServer broadcasts all available printers to all CUPS clients.
978</p> 997</p>
979 998
980<p> 999<p>
981To print, use for example 1000To print, use for example
985# <i>lpr -pHPDeskJet930C anything.txt</i> 1004# <i>lpr -pHPDeskJet930C anything.txt</i>
986# <i>lpr -PHPDeskJet930C foobar.whatever.ps</i> 1005# <i>lpr -PHPDeskJet930C foobar.whatever.ps</i>
987</pre> 1006</pre>
988 1007
989<p> 1008<p>
990In order to setup a default printer, you have to edit 1009In order to setup a default printer, you have to edit
991<path>/etc/cups/client.conf</path> and set the directive ServerName to 1010<path>/etc/cups/client.conf</path> and set the directive
992your printserver. In the case of this guide that would be the 1011<c>ServerName</c> to your printserver. In the case of this guide that
993following example. 1012would be the following example.
994</p> 1013</p>
995 1014
996<pre caption="/etc/cups/client.conf"> 1015<pre caption="/etc/cups/client.conf">
997ServerName PrintServer 1016ServerName PrintServer
998</pre> 1017</pre>
999 1018
1000<p> 1019<p>
1001The following will print foorbar.whatever.ps directly to the print 1020The following will print <path>foorbar.whatever.ps</path> directly to the print
1002server. 1021server.
1003</p> 1022</p>
1004 1023
1005<pre caption="Printing to the default printer"> 1024<pre caption="Printing to the default printer">
1006$ <i>lpr foobar.whatever.ps</i> 1025$ <i>lpr foobar.whatever.ps</i>
1011include the following: 1030include the following:
1012</p> 1031</p>
1013 1032
1014<ul> 1033<ul>
1015 <li> 1034 <li>
1016 Setting the ServerName in client.conf seems to work well for only one 1035 Setting the <c>ServerName</c> in <path>client.conf</path> seems to
1017 printer, there may be yet another way to set a client's default remote 1036 work well for only one printer, there may be yet another way to
1018 printer. 1037 set a client's default remote printer.
1019 </li> 1038 </li>
1020 <li> 1039 <li>
1021 Also, when accessing http://localhost:631 on the client now, no printers 1040 Also, when accessing <c>http://localhost:631</c> on the client
1022 seem to be "found" by the client-CUPS. This is to be expected when setting 1041 now, no printers seem to be "found" by the client-CUPS. This is to
1042 be expected when setting <c>ServerName</c> in
1023 ServerName in <path>client.conf</path>. 1043 <path>client.conf</path>.
1024 </li> 1044 </li>
1025</ul> 1045</ul>
1026 1046
1027</body> 1047</body>
1028</section> 1048</section>
1029<section> 1049<section>
1030<title>Mounting a Windows or Samba share in GNU/Linux</title> 1050<title>Mounting a Windows or Samba share in GNU/Linux</title>
1031<body> 1051<body>
1032 1052
1033<p> 1053<p>
1034Now is time to configure our kernel to support it the smbfs. Since I'm 1054Now is time to configure our kernel to support smbfs. Since I'm assumming we've
1035assumming we've all compiled at least one kernel, we'll need to make 1055all compiled at least one kernel, we'll need to make sure we have all the right
1036sure we have all the right options selected in our kernel. 1056options selected in our kernel. For simplicity sake, make it a module for ease
1037For simplicity sake, make it as a module for ease of use. It is the
1038authors opinion that kernel modules are a good thing and should be used 1057of use. It is the author's opinion that kernel modules are a good thing and
1039whenever possible. 1058should be used whenever possible.
1040</p> 1059</p>
1041 1060
1042<pre caption="Relevant kernel options" > 1061<pre caption="Relevant kernel options" >
1043CONFIG_SMB_FS=m 1062CONFIG_SMB_FS=m
1044CONFIG_SMB_UNIX=y 1063CONFIG_SMB_UNIX=y
1078<section> 1097<section>
1079<title>Printer Configuration for Windows NT/2000/XP clients</title> 1098<title>Printer Configuration for Windows NT/2000/XP clients</title>
1080<body> 1099<body>
1081 1100
1082<p> 1101<p>
1083That's just a bit of point-and-click. Browse to \\PrintServer and right 1102That's just a bit of point-and-click. Browse to
1084click on the printer (HPDeskJet930C) and click connect. This will 1103<path>\\PrintServer</path> and right click on the printer
1085download the drivers to the Windows client and now every application 1104(HPDeskJet930C) and click connect. This will download the drivers to
1086(such as Word or Acrobat) will offer HPDeskJet930C as an available 1105the Windows client and now every application (such as Word or Acrobat)
1087printer to print to. :-) 1106will offer HPDeskJet930C as an available printer to print to. :-)
1088</p> 1107</p>
1089 1108
1090</body> 1109</body>
1091</section> 1110</section>
1092</chapter> 1111</chapter>
1112
1093<chapter> 1113<chapter>
1094<title>Final Notes</title> 1114<title>Final Notes</title>
1095<section> 1115<section>
1096<title>A Fond Farewell</title> 1116<title>A Fond Farewell</title>
1097<body> 1117<body>
1103</p> 1123</p>
1104 1124
1105</body> 1125</body>
1106</section> 1126</section>
1107</chapter> 1127</chapter>
1128
1108<chapter> 1129<chapter>
1109<title>Links and Resources</title> 1130<title>Links and Resources</title>
1110<section> 1131<section>
1111<title>Links</title> 1132<title>Links</title>
1112<body> 1133<body>

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.10

  ViewVC Help
Powered by ViewVC 1.1.20