[Samba] Issue with printer sharing

[Sébastien Le Ray]

Le 22/09/2014 18:26, Marc Muehlfeld a écrit :
> Am 22.09.2014 um 15:27 schrieb Sébastien Le Ray:
>> I restarted from scratch (net ads leave ; apt-get purge any samba
>> related packages, net ads join, print server set up /etc./)
>> Still the same issue
> Did you also removed all the Samba databases? I don't know apt-get. But
> usually the package tools don't remove databases. Search for the
> registry.tdb file. This one contains the printer settings. But you
> should remove all databases.

Yes all was removed. I just re-did the whole process (deleting all samba 
files, purging, reinstalling) to be sure, same issue…
Is point & click available on samba 3 ?
> One thing that is different to my environment is, that you have 
> configured to use windows ACLs globally vfs objects = acl_xattr map 
> acl inherit = yes I don't have this and I use Posix ACLs. See 
> https://wiki.samba.org/index.php/Samba_as_a_print_server#Setup_the_.5Bprint.24.5D_share 
> ("Example for Samba 3.x:"). If I have time later, I can try it using 
> the Windows ACLs. 

Done that to, no change

>> # seems harmless
>> [2014/09/22 15:14:17.653343,  2]
>> ../source3/rpc_client/cli_winreg_spoolss.c:626(winreg_create_printer)
>>    winreg_create_printer: Skipping, SOFTWARE\Microsoft\Windows
>> NT\CurrentVersion\Print\Printers\NameOfThePrinter already exists
>>
>> # don't know if it could be related
>> [2014/09/22 15:14:17.674177,  2]
>> ../source3/rpc_client/cli_winreg_spoolss.c:2036(winreg_get_printer_dataex)
>>    winreg_get_printer_dataex: Could not query value DriverPolicy:
>> WERR_BADFILE
> What log level did you used? Can you increase it to '10', reload Samba
> and go the the last step before it fails. Then clear the log
> # echo > /path/to/log.txt
> run the failing step and directly after that create a copy of the
> logfile (so no further logging stuff goes in). Then put it on
> http://cpaste.org/ or some other paste server and post the link. Maybe
> we see something interesting.

Will try this tomorrow, but I'm afraid the log gets rotated to fast to 
provide enough info…

Regards