samba - Nov 2009 - strange issue with xerox printer: unable to configure driver

Hello list.

I've a strange issue with a samba 3.4.3 print server. Everything is fine 
with most printers, meaning drivers are assigned on server side and 
automatically distributed to the clients as expected. However, I fail to 
configure a Xerox document center 7435 the same way.

When I attempt to assign a driver to the printer, from a windows client 
with admin privileges,  I get an 'unexpected error occured in the print 
driver, close this windows and retry' error message, twice. More 
precisely, I can see initial renaming of the printer according to the 
driver name, then the error occurs, then the printer get renamed to '' 
(which is a bit painful :P)

I previously had a slightly different model (document center pro c2636) 
which was working fine. The other working printers are not xerox ones.

The driver is OK: it works fine when accessing the printer directly, and 
also when used from a windows print server. Also, I tried other variants 
(such as PCL driver instead of PS one), without success.

When configuring the same printer from a Windows system, I had to 
configure it with raw socket connection, because IPP connection didn't 
allowed me to share it at all, and CIFS connection to the print queue 
caused me some troubles (the printer didn't appeared in the 'fax and 
printers list' of the server from remote hosts).

The underlying printing system, cups, works perfectly. I've tried to 
switch from IPP to raw socket connection, because of the behaviour 
changes found with windows server, it didn't change anything.

I performed a network capture both on server and client side while 
triggering the error. The result is available as:
http://www.zarb.org/~guillomovitch/server.pcap
http://www.zarb.org/~guillomovitch/client.pcap

I can see some suspicious messages such as:
WINREG	OpenKey response, Error: WERR_BADFILE
SPOOLSS	GetPrinterData response, PrintProcCaps_NT EMF 1.008, File not 
found (pathname error)
SPOOLSS	SetPrinterDataEx response, Access denied

But nothing really useful.

I'm joining my samba configuration file. I'm using mandriva 2009.0 as 
server, and windows XP enterprise as client.

Any hint appreciated.
-- 
BOFH excuse #198:

Post-it Note Sludge leaked into the monitor.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: smb.conf
URL:
<http://lists.samba.org/pipermail/samba/attachments/20091127/660885aa/attachment.ksh>

Am 27.11.2009 18:32, schrieb Guillaume Rousse:
> Hello list.
Hello,
>
> I've a strange issue with a samba 3.4.3 print server. Everything is
fine
> with most printers, meaning drivers are assigned on server side and
> automatically distributed to the clients as expected. However, I fail to
> configure a Xerox document center 7435 the same way.
Well.. We use only xerox printers in our company and the newer ones 
(Phaser 3600 and up) gave allway headaches to me when samba came into 
play, esp. the large printers like Work Centres 7xxx. No matter what 
I've tried, PS-Driver, Universal Printer Driver, or last option: ignore 
the error message, connect the printer to the admin-PC over the server, 
nothing helped. As last resort I've installed it via tcp/ip-port on the 
workstation from a script and with holp of OPSI.
Finally we moved over to AD because of these problems and a redesign of 
our Network.

Sorry, I think you're out of luck in this case

Matthias


-- 
Menschen - kleine S?cke aus denkendem Wasser, zusammengehalten von
fragilen Kalzium-Ansammlungen

Hi,

I've been having the same problem on a 7328 if I remember well.

The problem is that the Xerox driver uses some proprietary print
processor. Under windows, the print server is expected to run the print
processor (which is not possible with samba as the print processor is a
w32
exec).

You have (as far as I know) 2 options here :
- Setup the printer in samba without specifying the driver (samba will
then only be used as a spooler for win clients). Point and print can then
no more be used
- Buy the postscript option from Xerox and use the print driver from cups
for the win clients

Fran?ois



On Fri, 27 Nov 2009 18:32:58 +0100, Guillaume Rousse
<Guillaume.Rousse at inria.fr> wrote:
> Hello list.
> 
> I've a strange issue with a samba 3.4.3 print server. Everything is
fine
> with most printers, meaning drivers are assigned on server side and 
> automatically distributed to the clients as expected. However, I fail to
> configure a Xerox document center 7435 the same way.
> 
> When I attempt to assign a driver to the printer, from a windows client 
> with admin privileges,  I get an 'unexpected error occured in the print
> driver, close this windows and retry' error message, twice. More 
> precisely, I can see initial renaming of the printer according to the 
> driver name, then the error occurs, then the printer get renamed to
''
> (which is a bit painful :P)
> 
> I previously had a slightly different model (document center pro c2636) 
> which was working fine. The other working printers are not xerox ones.
> 
> The driver is OK: it works fine when accessing the printer directly, and
> also when used from a windows print server. Also, I tried other variants
> (such as PCL driver instead of PS one), without success.
> 
> When configuring the same printer from a Windows system, I had to 
> configure it with raw socket connection, because IPP connection didn't 
> allowed me to share it at all, and CIFS connection to the print queue 
> caused me some troubles (the printer didn't appeared in the 'fax
and
> printers list' of the server from remote hosts).
> 
> The underlying printing system, cups, works perfectly. I've tried to 
> switch from IPP to raw socket connection, because of the behaviour 
> changes found with windows server, it didn't change anything.
> 
> I performed a network capture both on server and client side while 
> triggering the error. The result is available as:
> http://www.zarb.org/~guillomovitch/server.pcap
> http://www.zarb.org/~guillomovitch/client.pcap
> 
> I can see some suspicious messages such as:
> WINREG	OpenKey response, Error: WERR_BADFILE
> SPOOLSS	GetPrinterData response, PrintProcCaps_NT EMF 1.008, File not 
> found (pathname error)
> SPOOLSS	SetPrinterDataEx response, Access denied
> 
> But nothing really useful.
> 
> I'm joining my samba configuration file. I'm using mandriva 2009.0
as
> server, and windows XP enterprise as client.
> 
> Any hint appreciated.

Hi,

I'm having the same problem w/ samba v3.3.9 and Xerox 7346 drivers.

When I try to edit default driver properties I get function errors and 
operation could not be completed (screenshots attached).

I'm currently working with Xerox 2nd level engineering on this.  I'll 
let you know if anything comes of it although I'm not feeling 
particularly optimistic.

regards,
Ryan

Guillaume Rousse wrote:
> Hello list.
>
> I've a strange issue with a samba 3.4.3 print server. Everything is 
> fine with most printers, meaning drivers are assigned on server side 
> and automatically distributed to the clients as expected. However, I 
> fail to configure a Xerox document center 7435 the same way.
>
> When I attempt to assign a driver to the printer, from a windows 
> client with admin privileges,  I get an 'unexpected error occured in 
> the print driver, close this windows and retry' error message, twice. 
> More precisely, I can see initial renaming of the printer according to 
> the driver name, then the error occurs, then the printer get renamed 
> to '' (which is a bit painful :P)
>
> I previously had a slightly different model (document center pro 
> c2636) which was working fine. The other working printers are not 
> xerox ones.
>
> The driver is OK: it works fine when accessing the printer directly, 
> and also when used from a windows print server. Also, I tried other 
> variants (such as PCL driver instead of PS one), without success.
>
> When configuring the same printer from a Windows system, I had to 
> configure it with raw socket connection, because IPP connection didn't 
> allowed me to share it at all, and CIFS connection to the print queue 
> caused me some troubles (the printer didn't appeared in the 'fax
and
> printers list' of the server from remote hosts).
>
> The underlying printing system, cups, works perfectly. I've tried to 
> switch from IPP to raw socket connection, because of the behaviour 
> changes found with windows server, it didn't change anything.
>
> I performed a network capture both on server and client side while 
> triggering the error. The result is available as:
> http://www.zarb.org/~guillomovitch/server.pcap
> http://www.zarb.org/~guillomovitch/client.pcap
>
> I can see some suspicious messages such as:
> WINREG    OpenKey response, Error: WERR_BADFILE
> SPOOLSS    GetPrinterData response, PrintProcCaps_NT EMF 1.008, File 
> not found (pathname error)
> SPOOLSS    SetPrinterDataEx response, Access denied
>
> But nothing really useful.
>
> I'm joining my samba configuration file. I'm using mandriva 2009.0
as
> server, and windows XP enterprise as client.
>
> Any hint appreciated.

Hi,

Still working this out with the vendor.

Could you guys try this driver with the Xerox 7xxx model and let me know 
if it plays nicer with samba?

http://www.support.xerox.com/go/getfile.asp?Xlang=fr_FR&XCntry=FRA&objid=55425&EULA=1&prodID=WC7228_WC7235_WC7245&Family=WorkCentre&ripId=&langs=English%20(US)&plats=Windows%20XP&Xtype=download&uType

Their thoughts is the device mode issue which we're all familiar with:
"Be aware that a valid device mode can only be initiated by a _printer 
admin_ 
<http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/smb.conf.5.html>
or root (the reason should be obvious). Device modes can be correctly 
set only by executing the printer driver program itself. Since Samba 
cannot execute this Win32 platform driver code, it sets this field 
initially to NULL (which is not a valid setting for clients to use). 
Fortunately, most drivers automatically generate the printer driver data 
that is needed when they are uploaded to the/ [print$]/ share with the 
help of the APW or rpcclient. "

nabil at alanbar.us wrote:
> Hey Ryan, 
>      I am having the same problem. A client bought two of the bigger xerox
printers, a 7655 and a 5225. We would much prefer to run them through Samba. I
was wondering if you and the engineers were able to come up with something. Any
help would be hugely appreciated.
>
> _Nabil 
>
> Ryan Suarez wrote:
>   
>> Hi,
>>
>> I'm having the same problem w/ samba v3.3.9 and Xerox 7346 drivers.
>>
>> When I try to edit default driver properties I get function errors and 
>> operation could not be completed (screenshots attached).
>>
>> I'm currently working with Xerox 2nd level engineering on this. 
I'll
>> let you know if anything comes of it although I'm not feeling 
>> particularly optimistic.
>>
>> regards,
>> Ryan
>>
>> Guillaume Rousse wrote:
>>     
>>> Hello list.
>>>
>>> I've a strange issue with a samba 3.4.3 print server.
Everything is
>>> fine with most printers, meaning drivers are assigned on server
side
>>> and automatically distributed to the clients as expected. However,
I
>>> fail to configure a Xerox document center 7435 the same way.
>>>
>>> When I attempt to assign a driver to the printer, from a windows 
>>> client with admin privileges,  I get an 'unexpected error
occured in
>>> the print driver, close this windows and retry' error message,
twice.
>>> More precisely, I can see initial renaming of the printer according
to
>>> the driver name, then the error occurs, then the printer get
renamed
>>> to '' (which is a bit painful :P)
>>>
>>> I previously had a slightly different model (document center pro 
>>> c2636) which was working fine. The other working printers are not 
>>> xerox ones.
>>>
>>> The driver is OK: it works fine when accessing the printer
directly,
>>> and also when used from a windows print server. Also, I tried other
>>> variants (such as PCL driver instead of PS one), without success.
>>>
>>> When configuring the same printer from a Windows system, I had to 
>>> configure it with raw socket connection, because IPP connection
didn't
>>> allowed me to share it at all, and CIFS connection to the print
queue
>>> caused me some troubles (the printer didn't appeared in the
'fax and
>>> printers list' of the server from remote hosts).
>>>
>>> The underlying printing system, cups, works perfectly. I've
tried to
>>> switch from IPP to raw socket connection, because of the behaviour 
>>> changes found with windows server, it didn't change anything.
>>>
>>> I performed a network capture both on server and client side while 
>>> triggering the error. The result is available as:
>>> http://www.zarb.org/~guillomovitch/server.pcap
>>> http://www.zarb.org/~guillomovitch/client.pcap
>>>
>>> I can see some suspicious messages such as:
>>> WINREG    OpenKey response, Error: WERR_BADFILE
>>> SPOOLSS    GetPrinterData response, PrintProcCaps_NT EMF 1.008,
File
>>> not found (pathname error)
>>> SPOOLSS    SetPrinterDataEx response, Access denied
>>>
>>> But nothing really useful.
>>>
>>> I'm joining my samba configuration file. I'm using mandriva
2009.0 as
>>> server, and windows XP enterprise as client.
>>>
>>> Any hint appreciated.
>>>       
>> -- 
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
>>     
> Quoted from: 
>
http://old.nabble.com/strange-issue-with-xerox-printer%3A-unable-to-configure-driver-tp26545715p26576396.html
>
>