Xerox Global Printer Driver not printing jobs

[Frank Lascheit]

Hi,

we are selling a print spooling device which is based upon Samba and
Cups. I have to get as many drivers as possibly working on that platform
for our customers.
I haven't tested any special configurations and don't know nothing about
auditron.

Regards,

Frank Lascheit

Am Donnerstag, den 17.01.2013, 17:26 +0100 schrieb Stéphane PURNELLE:
> Hi,
> 
> Xerox Global Printer Driver and xerox driver are very special and @!# 
> driver.
> We have xerox driver but because we have some problem with driver 
> configuration, we have moved not print server to a windows server.
> 
> Have you printer who use printer authentification (xerox auditron) for 
> color right ?
> 
> 
> -----------------------------------
> Stéphane PURNELLE                         Admin. Systèmes et Réseaux 
> Service Informatique       Corman S.A.           Tel : 00 32 (0)87/342467
> 
> samba-technical-bounces at lists.samba.org wrote on 17/01/2013 17:21:07:
> 
> > De : Frank Lascheit <fl at seh.de>
> > A : samba-technical at lists.samba.org, 
> > Date : 17/01/2013 17:22
> > Objet : Xerox Global Printer Driver not printing jobs
> > Envoyé par : samba-technical-bounces at lists.samba.org
> > 
> > Hi all,
> > 
> > since it's "Fix my printer" day I'd like to offer a little fix to get
> > the "Xerox Global Printer Driver" going. Nobody seems to have reported
> > any problems recently, but here's what I've found anyway.
> > 
> > Samba does not support SetJob requests with info level 2 and replies
> > with "Unknown info level". Then the print job gets aborted.
> > 
> > wireshark snippet:
> > 
> > 5838   33.658687   192.168.3.158   192.168.3.167   SPOOLSS   SetJob 
> request,
> > Resume jobid 2[Long frame (620 bytes)]
> > 5839   33.659368   192.168.3.167   192.168.3.158   SPOOLSS   SetJob 
> response,
> > Unknown info level
> > 5840   33.660049   192.168.3.158   192.168.3.167   SPOOLSS 
> > AbortPrinter request
> > 5841   33.661100   192.168.3.167   192.168.3.158   SPOOLSS 
> > AbortPrinter response
> > 
> > Implementing level 2 by simply copying the spoolss_setjob_1() function
> > seems to fix the problem.
> > 
> > 
> > Kind regards,
> > 
> > Frank Lascheit
> > 
> > [attachment "patch.diff" deleted by Stéphane PURNELLE/COR/SOPARIND]