samba - May 2010 - win 7, samba 3.4.7, error 0x000003e6 with some printers

Hello,

I'm testing windows 7 with samba 3.4.7 and I'm using PrintUIEntry to 
connect the printers.
With some of those printers the connection fails (client side) with 
error 0x000003e6.
The strange thing is that:

1) trying the same connection against samba 3.0.11 works (alas, no 
domain functionality with that old version) and

2) two of the failing printers share the same driver with one that works

Looking at the level 10 log I see some WERR_INSUFFICIENT_BUFFER errors, 
but those are present also in the log for the printer that can connect 
successfully.
Diffing the log between a functioning printer and a failing one, the 
only difference (apart from the names) is that the failing printer has 
the PRINTER_ATTRIBUTE_PUBLISHED set.

Needless to say, windows xp has no problem with either samba 3.0.11 or 
samba 3.4.7.

Any hint?

Bye
-- 
Luca Olivetti
Wetron Automatizaci?n S.A. http://www.wetron.es/
Tel. +34 93 5883004 (Ext.133)  Fax +34 93 5883007

En/na Luca Olivetti ha escrit:
> Hello,
> 
> I'm testing windows 7 with samba 3.4.7 and I'm using PrintUIEntry
to
> connect the printers.
> With some of those printers the connection fails (client side) with 
> error 0x000003e6.
> The strange thing is that:
> 
> 1) trying the same connection against samba 3.0.11 works (alas, no 
> domain functionality with that old version) and
> 
> 2) two of the failing printers share the same driver with one that works
> 
> Looking at the level 10 log I see some WERR_INSUFFICIENT_BUFFER errors, 
> but those are present also in the log for the printer that can connect 
> successfully.
> Diffing the log between a functioning printer and a failing one, the 
> only difference (apart from the names) is that the failing printer has 
> the PRINTER_ATTRIBUTE_PUBLISHED set.
> 
> Needless to say, windows xp has no problem with either samba 3.0.11 or 
> samba 3.4.7.
> 
> Any hint?
Never mind, deleting the conflicting printers from win 7 and reassigning 
the already available driver (with the ensuing dance of printer 
renaming) seems to have fixed it.

Bye
-- 
Luca Olivetti
Wetron Automatizaci?n S.A. http://www.wetron.es/
Tel. +34 93 5883004 (Ext.133)  Fax +34 93 5883007

On Tue, May 4, 2010 at 11:58 AM, Luca Olivetti <luca at wetron.es>
wrote:
> En/na Ryan Suarez ha escrit:
>
>>>
>>> Never mind, deleting the conflicting printers from win 7 and
reassigning
>>> the already available driver (with the ensuing dance of printer
renaming)
>>> seems to have fixed it.
>>
>> Are you testing with Win7 64 bit? ?AFAIK, samba 3.4.x series does not
play
>> nicely with 64bit printing...
>> http://bit.ly/cX8UNL
>
> Nope, 32 bits. 64 bits will be next :-(
>
3.4.6 was supposed to fix the printing bug:

http://samba.org/samba/history/samba-3.4.6.html

John

John Drescher wrote:
> On Tue, May 4, 2010 at 11:58 AM, Luca Olivetti <luca at wetron.es>
wrote:
>   
>> En/na Ryan Suarez ha escrit:
>>
>>     
>>>> Never mind, deleting the conflicting printers from win 7 and
reassigning
>>>> the already available driver (with the ensuing dance of printer
renaming)
>>>> seems to have fixed it.
>>>>         
>>> Are you testing with Win7 64 bit?  AFAIK, samba 3.4.x series does
not play
>>> nicely with 64bit printing...
>>> http://bit.ly/cX8UNL
>>>       
>> Nope, 32 bits. 64 bits will be next :-(
>>
>>     
>
> 3.4.6 was supposed to fix the printing bug:
>
> http://samba.org/samba/history/samba-3.4.6.html
>   
Thanks John, good to know!  Do you know if v3.5.x works with 64bit as 
well now?
> John
>