SPOOLSS in 2.2.2: can print test page but not from apps

[Gerald Carter]

On Thu, 17 Jan 2002, Daron Kallan wrote:

> I have been using samba 2.2.2 with "use client driver" and "disable
> spoolss" because of the problems I am having with SPOOLSS.  I am
> printing to an EPSON Stylus C80 through CUPS 1.1.12, and without
> SPOOLSS this configuration works fine.
>
> When SPOOLSS is enabled it causes problems with Windows 2000 that I
> cannot seem to pin down.  From Win2K I am able to connect to the
> shared printer and automatically install the printer drivers.  But I
> am not able to print to the printer from Win2K applications.  What is
> strange about this is that I *CAN* Print Test Pages from the Printer
> Properties, and I *CAN* perform all utilities such as Nozzle Checks
> from the Printer Preferences.
>
> Some applications such as Internet Explorer do not report printing
> failure (I guess they don't bother to check), but programs like MSWord
> and Photoshop complain of being unable to access the printer [file].
> Microsoft's recommendation is to reinstall the printer driver (done
> that repeatedly) and to try to print a test page (always works).  I
> have read through all of the new printing documentation.  I created
> printing packages with imprints and installed them as directed (they
> are installed in the correct place and visible through rpcclient -c
> "enumdrivers).  Like I said earlier, Win2K is able to connect to and
> add the printer using the drivers served through SPOOLSS.  The problem
> only seems to occur when printing from an application (and not from
> the Win2K system's Printer Properties and Printer Preferences
> dialogs).

Seems like a lot of people are having problems with Epson drivers.

Could you try this?  Download the latest SAMBA_2_2 cvs code
and add "default devmode = yes" to your printer share.
Also remove set "use client driver = no" and "disable
spoolss = no".

The "default devmode" parameter is undocumented at the moment
(i'll correct that today I hope).  It controls whether or not
smbd will generate a default device mode for the printer.
This is not optimum as the devmode should really be created by
the printer driver itself.  However, experience has shown me
that some drivers crash with a NULL devmode (badly written driver
that doesn't check for NULL pointers in the PRINTER_INFO
struc) and some crash with a devmode that they did not create
themselves (more bad assumptions on the contents of the devmode).






chau, jerry
 ---------------------------------------------------------------------
 Hewlett-Packard                                     http://www.hp.com
 SAMBA Team                                       http://www.samba.org
 --                                            http://www.plainjoe.org
 "Sam's Teach Yourself Samba in 24 Hours" 2ed.      ISBN 0-672-32269-2
 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--