From 20967627378194121bc48bf387838b8bd7682478 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 18 Mar 2003 16:48:14 +0000 Subject: Regenerate (This used to be commit 25db62e3101dbcae8e9daee3cb16430297afa223) --- docs/htmldocs/printing.html | 236 ++++++++++++++++++++------------------------ 1 file changed, 105 insertions(+), 131 deletions(-) (limited to 'docs/htmldocs/printing.html') diff --git a/docs/htmldocs/printing.html b/docs/htmldocs/printing.html index 92eb52c7cc..91a1ad72b0 100644 --- a/docs/htmldocs/printing.html +++ b/docs/htmldocs/printing.html @@ -5,7 +5,7 @@ >Printing Support

13.1. Introduction

13.1. Introduction

Beginning with the 2.2.0 release, Samba supports the native Windows NT printing mechanisms implemented via @@ -163,9 +163,9 @@ CLASS="SECT1" >

13.2. Configuration

13.2. Configuration

However, the initial implementation allowed for a -parameter named printer driver locationprinter driver location to be used on a per share basis to specify the location of the driver files associated with that printer. Another -parameter named printer driverprinter driver provided a means of defining the printer driver name to be sent to the client.

13.2.1. Creating [print$]

13.2.1. Creating [print$]

In order to support the uploading of printer driver files, you must first configure a file share named [print$]. @@ -270,11 +266,9 @@ CLASS="PROGRAMLISTING" >The write listwrite list is used to allow administrative level user accounts to have write access in order to update files @@ -414,12 +408,10 @@ one of two conditions must hold true:

printer - admin list.

Once you have created the required [print$] service and associated subdirectories, simply log onto the Samba server using -a root (or printer adminprinter admin) account from a Windows NT 4.0/2k client. Open "Network Neighbourhood" or "My Network Places" and browse for the Samba host. Once you have located @@ -452,9 +442,9 @@ CLASS="SECT2" >

13.2.2. Setting Drivers for Existing Printers

13.2.2. Setting Drivers for Existing Printers

The initial listing of printers in the Samba host's Printers folder will have no real printer driver assigned @@ -524,9 +514,9 @@ CLASS="SECT2" >

13.2.3. Support a large number of printers

13.2.3. Support a large number of printers

One issue that has arisen during the development phase of Samba 2.2 is the need to support driver downloads for @@ -547,9 +537,9 @@ of how this could be accomplished:

 
-$ $ rpcclient pogo -U root%secret -c "enumdrivers"
 Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
  
@@ -563,9 +553,9 @@ Printer Driver Info 1:
 Printer Driver Info 1:
      Driver Name: [HP LaserJet 4Si/4SiMX PS]
 				  
-$ $ rpcclient pogo -U root%secret -c "enumprinters"
 Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
      flags:[0x800000]
@@ -573,13 +563,13 @@ Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
      description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,]
      comment:[]
 				  
-$ $ rpcclient pogo -U root%secret \
-> >  -c "setdriver hp-print \"HP LaserJet 4000 Series PS\""
 Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
 Successfully set hp-print to driver HP LaserJet 4000 Series PS.

13.2.4. Adding New Printers via the Windows NT APW

13.2.4. Adding New Printers via the Windows NT APW

By default, Samba offers all printer shares defined in

The connected user is able to successfully execute an OpenPrinterEx(\\server) with administrative - privileges (i.e. root or printer adminprinter admin).

show - add printer wizard = yes (the default).

add -printer command must have a defined value. The program hook must successfully add the printer to the system (i.e. @@ -658,35 +642,29 @@ CLASS="FILENAME" not exist, smbd will execute the will execute the add printer -command and reparse to the smb.conf to attempt to locate the new printer share. If the share is still not defined, an error of "Access Denied" is returned to the client. Note that the -add printer programadd printer program is executed under the context of the connected user, not necessarily a root account.

There is a complementary delete -printer command for removing entries from the "Printers..." folder.

The following is an example add printer commandadd printer command script. It adds the appropriate entries to

13.2.5. Samba and Printer Ports

13.2.5. Samba and Printer Ports

Windows NT/2000 print servers associate a port with each printer. These normally take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the @@ -780,12 +756,10 @@ CLASS="FILENAME" > possesses a enumports -command which can be used to define an external program that generates a listing of ports on a system.

13.3. The Imprints Toolset

13.3. The Imprints Toolset

The Imprints tool set provides a UNIX equivalent of the Windows NT Add Printer Wizard. For complete information, please @@ -814,9 +788,9 @@ CLASS="SECT2" >

13.3.1. What is Imprints?

13.3.1. What is Imprints?

Imprints is a collection of tools for supporting the goals of

13.3.2. Creating Printer Driver Packages

13.3.2. Creating Printer Driver Packages

The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt also included @@ -862,9 +836,9 @@ CLASS="SECT2" >

13.3.3. The Imprints server

13.3.3. The Imprints server

The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each printer @@ -886,9 +860,9 @@ CLASS="SECT2" >

13.3.4. The Installation Client

13.3.4. The Installation Client

More information regarding the Imprints installation client is available in the

13.4. Diagnosis

13.4. Diagnosis

13.4.1. Introduction

13.4.1. Introduction

This is a short description of how to debug printing problems with Samba. This describes how to debug problems with printing from a SMB @@ -1052,7 +1026,7 @@ and it should be periodically cleaned out. Samba used the lpq command to determine the "job number" assigned to your print job by the spooler.

The %>letter< are "macros" that get dynamically replaced with appropriate +>The %>letter< are "macros" that get dynamically replaced with appropriate values when they are used. The %s gets replaced with the name of the spool file that Samba creates and the %p gets replaced with the name of the printer. The %j gets replaced with the "job number" which comes from @@ -1063,9 +1037,9 @@ CLASS="SECT2" >

13.4.2. Debugging printer problems

13.4.2. Debugging printer problems

One way to debug printing problems is to start by replacing these command with shell scripts that record the arguments and the contents @@ -1081,7 +1055,7 @@ CLASS="PROGRAMLISTING" /usr/bin/id -p >/tmp/tmp.print # we run the command and save the error messages # replace the command with the one appropriate for your system - /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print

Then you print a file and try removing it. You may find that the @@ -1120,9 +1094,9 @@ CLASS="SECT2" >

13.4.3. What printers do I have?

13.4.3. What printers do I have?

You can use the 'testprns' program to check to see if the printer name you are using is recognized by Samba. For example, you can @@ -1149,9 +1123,9 @@ CLASS="SECT2" >

13.4.4. Setting up printcap and print servers

13.4.4. Setting up printcap and print servers

You may need to set up some printcaps for your Samba system to use. It is strongly recommended that you use the facilities provided by @@ -1233,9 +1207,9 @@ CLASS="SECT2" >

13.4.5. Job sent, no output

13.4.5. Job sent, no output

This is the most frustrating part of printing. You may have sent the job, verified that the job was forwarded, set up a wrapper around @@ -1278,9 +1252,9 @@ CLASS="SECT2" >

13.4.6. Job sent, strange output

13.4.6. Job sent, strange output

Once you have the job printing, you can then start worrying about making it print nicely.

13.4.7. Raw PostScript printed

13.4.7. Raw PostScript printed

This is a problem that is usually caused by either the print spooling system putting information at the start of the print job that makes @@ -1339,9 +1313,9 @@ CLASS="SECT2" >

13.4.8. Advanced Printing

13.4.8. Advanced Printing

Note that you can do some pretty magic things by using your imagination with the "print command" option and some shell scripts. @@ -1355,9 +1329,9 @@ CLASS="SECT2" >

13.4.9. Real debugging

13.4.9. Real debugging

If the above debug tips don't help, then maybe you need to bring in the bug guns, system tracing. See Tracing.txt in this directory.