Bug 57868 - Windows Point'n'Print driver download loops with UCS 5.2-0, failing to install the driver
Summary: Windows Point'n'Print driver download loops with UCS 5.2-0, failing to instal...
Status: NEW
Alias: None
Product: UCS
Classification: Unclassified
Component: Samba
Version: UCS 5.2
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: Samba maintainers
QA Contact: Samba maintainers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-16 18:01 CET by Arvid Requate
Modified: 2025-01-22 17:04 CET (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
Max CVSS v3 score:


Attachments
p4win11.ps (4.40 MB, application/postscript)
2025-01-16 18:01 CET, Arvid Requate
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2025-01-16 18:01:36 CET
Created attachment 11272 [details]
p4win11.ps

Windows Point'n'Print driver download loops with UCS 5.2-0, failing to install the driver.

Following the guide

https://docs.software-univention.de/manual/5.0/en/print-services/windows-clients.html

the driver upload to a UCS 5.2-0 Samba/AD DC works (Windows 11 and Windows 10), but
when assigning the driver the downloads starts (at point 9 of the guide in the manual) and the popup shows the normal download progress of several files, but finally after the download completed and the popup closes, the popup dialog opens again, asking again if I trust the server and if it may download the driver files. This game can be played again and again.

The only way I could make printing work was to install the driver (Windows 10) locally (HP Universal Printing PCL6) and then assign that. After that I could successfully print a test page (see attachment as proof).
Comment 1 Arvid Requate univentionstaff 2025-01-16 18:19:16 CET
One note: Looking at the server side logs I see a lot of messages
of this kind:
===
[2025/01/16 17:59:17.062630,  0, pid=363692] ../../lib/krb5_wrap/krb5_samba.c:3987(smb_krb5_init_context_common)
  smb_krb5_init_context_common: Krb5 context initialization failed (Ist kein Verzeichnis)
[2025/01/16 17:59:17.062654,  1, pid=363692] ../../source4/auth/kerberos/krb5_init_context.c:787(smb_krb5_init_context)
  smb_krb5_context_init_basic failed (Ist kein Verzeichnis)     ## German for "Is not a directory"
===

in /var/log/samba/log.rpcd_spoolss and also sometimes:

===
[2025/01/16 17:59:17.274840,  0, pid=363944] ../../librpc/rpc/dcesrv_handles.c:130(dcesrv_handle_lookup)
  dcesrv_handle_lookup: Attempt to use invalid sid S-1-5-21-2950701298-995968954-901794811-500 - S-1-5-21-2950701298-995968954-901794811-2100
===
That second SID is the Windows 11 client, the first one is the standard Domain Administrator account I was using on the Windows (10 + 11) clients.

Not sure if this is related though.
Comment 2 Arvid Requate univentionstaff 2025-01-16 18:24:37 CET
Found the "dcesrv_handle_lookup: Attempt to use invalid sid" message also in:

https://ask.linuxmuster.net/t/lmn-7-2-aktueller-stand-win10-client-drucker-gehen-nur-zeitweise/11095