[Samba] Q: Samba & CUPS & Win Print Processor

[Martin Zielinski]

Hi,

there is currently no way to use the functionality of print processors 
with samba - shared printers.

The reason lies in the way windows handles print processors that are 
provided by servers. There is no way to let windows use them locally. 
They *MUST* be executed on the server (normally they receive EMF format 
and play around with it, and give the resulting EMF to the driver).

Of course they currently can not run on the server so samba only reports
to have winprint installed.

I've even tried to use a print processor together with wine - but no 
success. Help and ideas welcome.

Sorry,

Martin

Albrecht Dreß schrieb:
> Hi all,
> 
> I have a problem while trying to migrate print services from a Win server to Samba 3.0.23c on an old FC 4 box.  The Samba box is part of a AD domain, with spoolss enabled:
> 
> <snip>
> security = ads
> domain master = no
> local master = no
> preferred master = no
> disable spoolss = no
> use client driver = no
> </snip>
> 
> On the Linux box, I also have Cups 1.2.12 (self-compiled) running, with a number of printer queues.  I added all printers to Samba as described in the howto's, and uploaded the Win drivers.  Now, when a client connects to the printer, some advanced printing options for HP Postscript printers, like n-up printing, are simply gone, which *are* present when using the Win server with the *same* driver.  I noticed that in the propertied dialogue, tab "Advanced" under "Print Processor" only "winprint" is listed for Samba, whereas the Win server supports more and different ones with more options.  Unfortunately, the only pointer Google found was [1] which is (surprise) not helpful.
> 
> Does anyone have an idea what actually goes wrong here?  Of course, I would like to have the simple "Connect" method to activate the printers on any Win client, but of course *with* the advanced driver capabilities.
> 
> Any help would be really appreciated!
> 
> Thanks in advance,
> Albrecht
> 
> [1] http://support.microsoft.com/kb/884897
>