/[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.4 Revision 1.5
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.5 2004/05/30 13:24:49 neysx 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/Clam AV 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>
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.3</version>
23<date>May 18, 2004</date> 24<date>May 18, 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
35architectures and technologies, come together in a productive, 36architectures and technologies, come together in a productive,
36happily coexisting 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
42virtually all known variations of *nix. 43virtually all known variations of *nix.
43</p> 44</p>
44 45
45<p> 46<p>
46This HOWTO originally started not as a HOWTO, but as a FAQ. It was 47This HOWTO originally started not as a HOWTO, but as a FAQ. It was
47intended to explore the functionality and power of the Gentoo system, 48intended to explore the functionality and power of the Gentoo system,
48portage and the flexibility of USE flags. Like so many other projects, 49portage and the flexibility of USE flags. Like so many other projects,
75 76
76<ul> 77<ul>
77 <li> 78 <li>
78 <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO 79 <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO
79 CUPS+Samba: printing from Windows &amp; Linux</uri> 80 CUPS+Samba: printing from Windows &amp; Linux</uri>
80 </li> 81 </li>
81</ul> 82</ul>
82 83
83</body> 84</body>
84</section> 85</section>
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>
101<title>Brief Overview</title> 101<title>Brief Overview</title>
102<body> 102<body>
103 103
104<p> 104<p>
105After presenting the various USE flags, the following list will outline 105After presenting the various USE flags, the following list will outline
106all of the topics covered as they are presented: 106all of the topics covered as they are presented:
107</p> 107</p>
108 108
109<ul> 109<ul>
110 <li>On the Samba server: 110 <li>On the Samba server:
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>
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 161net-mail/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>
173 174
174<p> 175<p>
175Before emerging anything, take a look at the various USE flags 176Before emerging anything, take a look at the various USE flags
176available to Samba. 177available to Samba.
177</p> 178</p>
178 179
179<pre caption="Samba uses the following USE Variables:"> 180<pre caption="Samba uses the following USE Variables:">
180kerberos mysql xml acl cups ldap pam readline python oav 181kerberos mysql xml acl cups ldap pam readline python oav
181</pre> 182</pre>
182 183
290 </li> 291 </li>
291 <li> 292 <li>
292 While Active Directory, ACL, and PDC functions are out of the intended 293 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: 294 scope of this HOWTO, you may find these links as helpful to your cause:
294 <ul> 295 <ul>
295 <li><uri>http://www.bluelightning.org/linux/samba_acl_howto/</uri></li> 296 <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://open-projects.linuxcare.com/research-papers/winbind-08162000.html</uri></li>
297 <li><uri>http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory</uri></li> 298 <li><uri>http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory</uri></li>
298 </ul> 299 </ul>
299 </li> 300 </li>
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 <path>/etc/hosts</path> file. 316or appropriate entries in your <path>/etc/hosts</path> file.
315<c>cupsaddsmb</c> often borks if hostnames don't point to the correct 317<c>cupsaddsmb</c> often borks if hostnames don't point to the correct
316machines. 318machines.
317</p> 319</p>
318 320
319<p> 321<p>
379<section> 381<section>
380<title>Emerging net-print/hpijs</title> 382<title>Emerging net-print/hpijs</title>
381<body> 383<body>
382 384
383<p> 385<p>
384You only need to emerge this if you use an HP printer. 386You only need to emerge this if you use an HP printer.
385</p> 387</p>
386 388
387<pre caption="Emerge hpijs"> 389<pre caption="Emerge hpijs">
388# <i>emerge net-print/hpijs</i> 390# <i>emerge net-print/hpijs</i>
389</pre> 391</pre>
390 392
391</body> 393</body>
392</section> 394</section>
393</chapter> 395</chapter>
396
394<chapter> 397<chapter>
395<title>Server Configuration</title> 398<title>Server Configuration</title>
396<section> 399<section>
397<title>Configuring Samba</title> 400<title>Configuring Samba</title>
398<body> 401<body>
399 402
400<p> 403<p>
401The main Samba configuration file is <path>/etc/samba/smb.conf</path>. 404The main Samba configuration file is <path>/etc/samba/smb.conf</path>.
402It is divided in sections indicated by [sectionname]. Comments are either 405It is divided in sections indicated by [sectionname]. Comments are either
403# 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
404suggestions for modifications. If more details are required, see the 407suggestions for modifications. If more details are required, see the
405man page for <path>smb.conf</path>, the installed 408man page for <path>smb.conf</path>, the installed
406<path>smb.conf.example</path>, the Samba Web site or any of the 409<path>smb.conf.example</path>, the Samba Web site or any of the
407numerous Samba books available. 410numerous Samba books available.
408</p> 411</p>
484printer admin = <i>root</i> 487printer admin = <i>root</i>
485 488
486<comment># We create a new share that we can read/write to from anywhere 489<comment># We create a new share that we can read/write to from anywhere
487# This is kind of like a public temp share, anyone can do what 490# This is kind of like a public temp share, anyone can do what
488# they want here.</comment> 491# they want here.</comment>
489[public] 492[public]
490comment = Public Files 493comment = Public Files
491browseable = yes 494browseable = yes
492public = yes 495public = yes
493create mode = 0766 496create mode = 0766
494guest ok = yes 497guest ok = yes
495path = /home/samba/public 498path = /home/samba/public
496</pre> 499</pre>
497 500
498<warn> 501<warn>
499
500If you like to use Samba's guest account to do anything concerning 502If you like to use Samba's guest account to do anything concerning
501printing from Windows clients: don't set <c>guest only = yes</c> in 503printing from Windows clients: don't set <c>guest only = yes</c> in
502the <c>[global]</c> section. The guest account seems to cause 504the <c>[global]</c> section. The guest account seems to cause
503problems when running <c>cupsaddsmb</c> sometimes when trying to 505problems when running <c>cupsaddsmb</c> sometimes when trying to
504connect from Windows machines. See below, too, when we talk about 506connect from Windows machines. See below, too, when we talk about
505<c>cupsaddsmb</c> and the problems that can arise. Use a dedicated 507<c>cupsaddsmb</c> and the problems that can arise. Use a dedicated
506printer user, like <c>printeruser</c> or <c>printer</c> or 508printer user, like <c>printeruser</c> or <c>printer</c> or
507<c>printme</c> or whatever. It doesn't hurt and it will certainly 509<c>printme</c> or whatever. It doesn't hurt and it will certainly
508protect you from a lot of problems. 510protect you from a lot of problems.
509</warn> 511</warn>
510 512
511<p> 513<p>
512Now create the directories required for the minimum configuration of 514Now create the directories required for the minimum configuration of
513Samba to share the installed printer throughout the network. 515Samba to share the installed printer throughout the network.
514</p> 516</p>
561 563
562<comment>; log all file access (yes/no). If set to yes, every access will 564<comment>; log all file access (yes/no). If set to yes, every access will
563; be logged. If set to no (default), only access to infected files 565; be logged. If set to no (default), only access to infected files
564; will be logged</comment> 566; will be logged</comment>
565verbose file logging = no 567verbose file logging = no
566 568
567<comment>; if set to yes (default), a file will be scanned while opening</comment> 569<comment>; if set to yes (default), a file will be scanned while opening</comment>
568scan on open = yes 570scan on open = yes
569<comment>; if set to yes, a file will be scanned while closing (default is yes)</comment> 571<comment>; if set to yes, a file will be scanned while closing (default is yes)</comment>
570scan on close = yes 572scan on close = yes
571 573
572<comment>; if communication to clamd fails, should access to file denied? 574<comment>; if communication to clamd fails, should access to file denied?
573; (default: yes)</comment> 575; (default: yes)</comment>
574deny access on error = yes 576deny access on error = yes
575 577
576<comment>; if daemon files with a minor error (corruption, etc.), 578<comment>; if daemon fails with a minor error (corruption, etc.),
577; should access to file denied? 579; should access to file denied?
578; (default: yes)</comment> 580; (default: yes)</comment>
579deny access on minor error = yes 581deny access on minor error = yes
580 582
581<comment>; send a warning message via Windows Messenger service 583<comment>; send a warning message via Windows Messenger service
582; when virus is found? 584; when virus is found?
583; (default: yes)</comment> 585; (default: yes)</comment>
584send warning message = yes 586send warning message = yes
585 587
586<comment>; what to do with an infected file 588<comment>; what to do with an infected file
587; quarantine: try to move to quantine directory; delete it if moving fails 589; quarantine: try to move to quantine directory; delete it if moving fails
588; delete: delete infected file 590; delete: delete infected file
589; nothing: do nothing</comment> 591; nothing: do nothing</comment>
590infected file action = <comment>delete</comment> 592infected file action = <comment>delete</comment>
591 593
592<comment>; where to put infected files - you really want to change this! 594<comment>; where to put infected files - you really want to change this!
593; it has to be on the same physical device as the share!</comment> 595; it has to be on the same physical device as the share!</comment>
594quarantine directory = /tmp 596quarantine directory = /tmp
595<comment>; prefix for files in quarantine</comment> 597<comment>; prefix for files in quarantine</comment>
596quarantine prefix = vir- 598quarantine prefix = vir-
597 599
598<comment>; as Windows tries to open a file multiple time in a (very) short time 600<comment>; as Windows tries to open a file multiple time in a (very) short time
599; of period, samba-vscan use a last recently used file mechanism to avoid 601; 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 602; multiple scans of a file. This setting specified the maximum number of
601; elements of the last recently used file list. (default: 100)</comment> 603; elements of the last recently used file list. (default: 100)</comment>
602max lru files entries = 100 604max lru files entries = 100
603 605
604<comment>; an entry is invalidad after lru file entry lifetime (in seconds). 606<comment>; an entry is invalidated after lru file entry lifetime (in seconds).
605; (Default: 5)</comment> 607; (Default: 5)</comment>
606lru file entry lifetime = 5 608lru file entry lifetime = 5
607 609
608<comment>; socket name of clamd (default: /var/run/clamd)</comment> 610<comment>; socket name of clamd (default: /var/run/clamd)</comment>
609clamd socket name = /var/run/clamd 611clamd socket name = /var/run/clamd
610</pre> 612</pre>
611 613
612<p> 614<p>
613It is generally a good idea to start the virus scanner immediately. Add 615It is generally a good idea to start the virus scanner immediately. Add
614it to the <e>default</e> runlevel and then start the <c>clamd</c> service immediately. 616it to the <e>default</e> runlevel and then start the <c>clamd</c> service immediately.
615</p> 617</p>
616 618
617<pre caption="Add clamd to bootup and start it"> 619<pre caption="Add clamd to bootup and start it">
618# <i>rc-update add clamd default</i> 620# <i>rc-update add clamd default</i>
619# <i>/etc/init.d/clamd start</i> 621# <i>/etc/init.d/clamd start</i>
696<comment>(To start CUPS on boot)</comment> 698<comment>(To start CUPS on boot)</comment>
697# <i>rc-update add cupsd default</i> 699# <i>rc-update add cupsd default</i>
698<comment>(To start CUPS if it isn't started)</comment> 700<comment>(To start CUPS if it isn't started)</comment>
699# <i>/etc/init.d/cupsd start</i> 701# <i>/etc/init.d/cupsd start</i>
700<comment>(If CUPS is already started we'll need to restart it!)</comment> 702<comment>(If CUPS is already started we'll need to restart it!)</comment>
701# <i>/etc/init.d/cupsd restart</i> 703# <i>/etc/init.d/cupsd restart</i>
702</pre> 704</pre>
703 705
704</body> 706</body>
705</section> 707</section>
706<section> 708<section>
707<title>Installing a printer for and with CUPS</title> 709<title>Installing a printer for and with CUPS</title>
708<body> 710<body>
709 711
710<p> 712<p>
711First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> 713First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to
712to find and download the correct PPD file for your printer and CUPS. To 714find and download the correct PPD file for your printer and CUPS. To do so,
713do so, click the link Printer Listings to the left. Select your 715click the link Printer Listings to the left. Select your printers manufacturer
714printers manufacturer and the model in the pulldown menu, eg HP and 716and the model in the pulldown menu, eg HP and DeskJet 930C. Click "Show". On
715DeskJet 930C. Click "Show". On the page coming up click the "recommended 717the page coming up click the "recommended driver" link after reading the
716driver" link after reading the various notes and information. Then fetch 718various notes and information. Then fetch the PPD file from the next page,
717the PPD file from the next page, again after reading the notes and 719again after reading the notes and introductions there. You may have to select
718introductions there. You may have to select your printers manufacturer 720your printers manufacturer and model again. Reading the <uri
719and model again. Reading the <uri link="http://www.linuxprinting.org/cups-doc.html">CUPS 721link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri>
720quickstart guide</uri> is also very helpful when working with CUPS. 722is also very helpful when working with CUPS.
721</p> 723</p>
722 724
723<p> 725<p>
724Now you have a PPD file for your printer to work with CUPS. Place it in 726Now 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 727<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was
726named <path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer. 728named <path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer.
727This can be done via the CUPS web interface or via command line. The web 729This can be done via the CUPS web interface or via command line. The web
728interface is found at <path>http://PrintServer:631</path> once CUPS is running. 730interface is found at <path>http://PrintServer:631</path> once CUPS is running.
729</p> 731</p>
730 732
731<pre caption="Install the printer via command line"> 733<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> 734# <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i>
733</pre> 735</pre>
734 736
735<p> 737<p>
940<p> 942<p>
941It would probably be prudent to check our logs at this time also. 943It would probably be prudent to check our logs at this time also.
942We will also want to take a peak at our Samba shares using 944We will also want to take a peak at our Samba shares using
943<c>smbclient</c>. 945<c>smbclient</c>.
944</p> 946</p>
945 947
946<pre caption="Checking the shares with smbclient"> 948<pre caption="Checking the shares with smbclient">
947# <i>smbclient -L localhost</i> 949# <i>smbclient -L localhost</i>
948Password: 950Password:
949<comment>(You should see a BIG list of services here.)</comment> 951<comment>(You should see a BIG list of services here.)</comment>
950</pre> 952</pre>
951 953
952</body> 954</body>
953</section> 955</section>
954</chapter> 956</chapter>
957
955<chapter> 958<chapter>
956<title>Configuration of the Clients</title> 959<title>Configuration of the Clients</title>
957<section> 960<section>
958<title>Printer configuration of *nix based clients</title> 961<title>Printer configuration of *nix based clients</title>
959<body> 962<body>
960 963
961<p> 964<p>
962Despite the variation or distribution, the only thing needed is CUPS. 965Despite the variation or distribution, the only thing needed is CUPS.
963Do the equivalent on any other UNIX/Linux/BSD client. 966Do the equivalent on any other UNIX/Linux/BSD client.
964</p> 967</p>
965 968
966<pre caption="Configuring a Gentoo system."> 969<pre caption="Configuring a Gentoo system">
967# <i>emerge cups</i> 970# <i>emerge cups</i>
968# <i>/etc/init.d/cupsd start</i> 971# <i>/etc/init.d/cupsd start</i>
969# <i>rc-update add cupsd default</i> 972# <i>rc-update add cupsd default</i>
970</pre> 973</pre>
971 974
972<p> 975<p>
973That should be it. Nothing else will be needed. Just point your web 976That should be it. Nothing else will be needed. Just point your web
974browser to <c>http://localhost:631</c> on the client and you'll see that 977browser to <c>http://localhost:631</c> on the client and you'll see that
975PrintServer broadcasts all available printers to all CUPS clients. 978PrintServer broadcasts all available printers to all CUPS clients.
976</p> 979</p>
977 980
978<p> 981<p>
979To print, use for example 982To print, use for example
980</p> 983</p>
981 984
1018 <li> 1021 <li>
1019 Also, when accessing <c>http://localhost:631</c> on the client 1022 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 1023 now, no printers seem to be "found" by the client-CUPS. This is to
1021 be expected when setting <c>ServerName</c> in 1024 be expected when setting <c>ServerName</c> in
1022 <path>client.conf</path>. 1025 <path>client.conf</path>.
1023 </li> 1026 </li>
1024</ul> 1027</ul>
1025 1028
1026</body> 1029</body>
1027</section> 1030</section>
1028<section> 1031<section>
1029<title>Mounting a Windows or Samba share in GNU/Linux</title> 1032<title>Mounting a Windows or Samba share in GNU/Linux</title>
1030<body> 1033<body>
1031 1034
1032<p> 1035<p>
1033Now is time to configure our kernel to support smbfs. Since I'm 1036Now is time to configure our kernel to support smbfs. Since I'm assumming we've
1034assumming we've all compiled at least one kernel, we'll need to make 1037all compiled at least one kernel, we'll need to make sure we have all the right
1035sure we have all the right options selected in our kernel. 1038options selected in our kernel. For simplicity sake, make it a module for ease
1036For simplicity sake, make it a module for ease of use. It is the
1037authors opinion that kernel modules are a good thing and should be used 1039of use. It is the author's opinion that kernel modules are a good thing and
1038whenever possible. 1040should be used whenever possible.
1039</p> 1041</p>
1040 1042
1041<pre caption="Relevant kernel options" > 1043<pre caption="Relevant kernel options" >
1042CONFIG_SMB_FS=m 1044CONFIG_SMB_FS=m
1043CONFIG_SMB_UNIX=y 1045CONFIG_SMB_UNIX=y
1044</pre> 1046</pre>
1045 1047
1046<p> 1048<p>
1047Then make the module/install it; insert them with: 1049Then make the module/install it; insert them with:
1048</p> 1050</p>
1049 1051
1050<pre caption="Loading the kernel module"> 1052<pre caption="Loading the kernel module">
1051# <i>modprobe smbfs</i> 1053# <i>modprobe smbfs</i>
1052</pre> 1054</pre>
1053 1055
1077<section> 1079<section>
1078<title>Printer Configuration for Windows NT/2000/XP clients</title> 1080<title>Printer Configuration for Windows NT/2000/XP clients</title>
1079<body> 1081<body>
1080 1082
1081<p> 1083<p>
1082That's just a bit of point-and-click. Browse to 1084That's just a bit of point-and-click. Browse to
1083<path>\\PrintServer</path> and right click on the printer 1085<path>\\PrintServer</path> and right click on the printer
1084(HPDeskJet930C) and click connect. This will download the drivers to 1086(HPDeskJet930C) and click connect. This will download the drivers to
1085the Windows client and now every application (such as Word or Acrobat) 1087the Windows client and now every application (such as Word or Acrobat)
1086will offer HPDeskJet930C as an available printer to print to. :-) 1088will offer HPDeskJet930C as an available printer to print to. :-)
1087</p> 1089</p>
1088 1090
1089</body> 1091</body>
1090</section> 1092</section>
1091</chapter> 1093</chapter>
1094
1092<chapter> 1095<chapter>
1093<title>Final Notes</title> 1096<title>Final Notes</title>
1094<section> 1097<section>
1095<title>A Fond Farewell</title> 1098<title>A Fond Farewell</title>
1096<body> 1099<body>
1097 1100
1098<p> 1101<p>
1099Well that should be it. You should now have a successful printing enviroment 1102Well that should be it. You should now have a successful printing enviroment
1100that is friendly to both Windows and *nix as well as a fully virus-free working 1103that is friendly to both Windows and *nix as well as a fully virus-free working
1101share! 1104share!
1102</p> 1105</p>
1103 1106
1104</body> 1107</body>
1105</section> 1108</section>
1106</chapter> 1109</chapter>
1110
1107<chapter> 1111<chapter>
1108<title>Links and Resources</title> 1112<title>Links and Resources</title>
1109<section> 1113<section>
1110<title>Links</title> 1114<title>Links</title>
1111<body> 1115<body>
1112 1116
1113<p> 1117<p>
1114These are some links that may help you in setting up, configuration and 1118These are some links that may help you in setting up, configuration and
1115troubleshooting your installation: 1119troubleshooting your installation:
1116</p> 1120</p>
1117 1121
1118<ul> 1122<ul>
1119 <li><uri link="http://www.cups.org/">CUPS Homepage</uri></li> 1123 <li><uri link="http://www.cups.org/">CUPS Homepage</uri></li>
1120 <li><uri link="http://www.samba.org/">Samba Homepage</uri></li> 1124 <li><uri link="http://www.samba.org/">Samba Homepage</uri></li>
1121 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li> 1125 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li>

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.5

  ViewVC Help
Powered by ViewVC 1.1.20