[Samba] Point and Print Nightmare ? Samba4 ? or a simple driver issue ?

Achim Gottinger achim at ag-web.biz
Sat Jan 29 22:49:55 UTC 2022

Am 24.01.22 um 22:12 schrieb Michael Evans via samba:
> You have a working Samba print server?
> I've been unable to reproduce that and have also done my best to follow the
> directions on the wiki.
> Could you please post a sanitized version of any files from the printserver
> that you feel are relevant to success?  Possibly smb.conf krb5.conf
> cupsd.conf?
> Maybe I'll be able to enlighten myself by comparing working results to buggy
> ones.
>> -----Original Message-----
>> From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Björn
>> JACKE via samba
>> Sent: Monday, January 24, 2022 8:21 AM
>> To: Olivier BILHAUT
>> Cc: samba
>> Subject: Re: [Samba] Point and Print Nightmare ? Samba4 ? or a simple
> driver
>> issue ?
>> On 2021-11-29 at 14:17 +0100 Olivier BILHAUT via samba sent off:
>>> We've kindly followed
>>> all the recommandations about the 3 GPOs. We've updated to Samba
>> 4.15.2
>>> and Windows to 21H2.
>>> But no way, when the driver is downloaded by the
>>> client, at the "Installing driver" step, the following error raise :
>> we've analyzed the problem, it happens if you have the print server
> running
>> on
>> a AD DC Samba server only. Microsoft is running RPC via SMB with the
> printer
>> nightmare patches now. On a Samba print server, which is running as a
>> member
>> server the problem did not show up.  The patch for master, which makes it
>> work
>> in a AD DC also is here:
>> https://gitlab.com/samba-team/samba/-/merge_requests/2343.patch
>> Best regards
>> Björn
>> --
>> SerNet GmbH - Bahnhofsallee 1b - 37081 Göttingen
>> phone: +495513700000  mailto:contact at sernet.com
>> AG Göttingen: HR-B 2816 - https://www.sernet.com
>> Manag. Directors Johannes Loxen and Reinhild Jung
>> data privacy policy https://www.sernet.de/privacy
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
Since the december 2021 Updates samba as a printserver shoould work again with this registry key set on your client.


I assume this restores the old behaviour and comes with security risks.

I explicitly tested it again now against an old samba 4.7 ad-dc acting as an printserver. I had held back the cumulatiive updates since the january updates which had been deployed last weekend. So far no printing issues occured but we run w10 1809 LTSC everywhere.


More information about the samba mailing list