Bug 56140 - Microsoft Windows 11 22H2 cannot access Samba print server
Microsoft Windows 11 22H2 cannot access Samba print server
Status: NEW
Product: UCS manual
Classification: Unclassified
Component: Services for Windows
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Docu maintainers
Samba maintainers
:
Depends on:
Blocks: 54492
  Show dependency treegraph
 
Reported: 2023-06-12 18:29 CEST by Arvid Requate
Modified: 2024-01-08 14:52 CET (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.103
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2024010821000346
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2023-06-12 18:29:10 CEST
Testing with a Microsoft Windows 11 client showed that it seems to refuse to talk to a UCS Samba print server:

* While the Windows 10 printmanagement app can connect to the UCS (replica) Samba DC, the Windows 11 printmanagement app doesn't show printers and uploaded drivers. After a short while of adding the UCS Samba printserver to the list of servers in the GUI app, it shows a red down-arrow next to the UCS server icon.

* Accessing the printer from Windows explorer (<Windows-E> \\replica.fqdn\ and then double click on any of the shown printer shares) fails with:

 Operation could not be completed (error 0x00000709).
 Double check the printer name and make sure that the printer is connected to the network.

This is due to a change in 22H2:

https://answers.microsoft.com/en-us/windows/forum/all/windows-11-error-message-0x00000709-while/c16a136d-a935-43a2-bbe1-9364a8d9379c ( or https://www.winhelponline.com/blog/printer-error-0x00000bc4-0x00000709-windows-11-22h2/ )

Can be adjusted either
* via GPO: enable "Administrative Templates>Printers>Configure RPC connection settings" and select "RPC over named pipes"
* via local regedit: Create new DWORD value in [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Printers\RPC] named RpcUseNamedPipeProtocol and set it to 1 (switching to RpcOverNamedPipes instead of RpcOverTcp)
Comment 1 Christina Scheinig univentionstaff 2024-01-08 14:52:35 CET
A customer asks for a solution. He has BYOD and therefor GPOs are not working for him. Local editing for each Device may also not the nicest workaround.
Do we have a solution in our product?