FS#72605 - Problem with cups printing over samba

Attached to Project: Arch Linux
Opened by Danny Schneider (schnedan) - Monday, 01 November 2021, 20:46 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 05 December 2021, 08:28 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I have 3 computers A,B,C
A - printerserver, current samba version
B - printing client, current samba version
C - printing client, samba version 4.14

Printing from B & C to A used to work until recently

Now, printing from B to A does not work and Cups logs a samba error "Tree connect failed (NT_STATUS_BAD_NETWORK_NAME)"

Printing from C to A still works all fine

Additional info:
* package version(s)
extra/samba 4.15.1-1
extra/cups 1:2.3.3op2-3
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
Print from B to A with any Programm fails
Print from C to A with any Programm works
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Sunday, 05 December 2021, 08:28 GMT
Reason for closing:  None
Comment by Andreas Radke (AndyRTR) - Tuesday, 02 November 2021, 17:58 GMT
How is samba related to printing in your setup?
Comment by Danny Schneider (schnedan) - Tuesday, 02 November 2021, 18:32 GMT
I am printing over samba? like I can access the Printerserver from Linux and Windows?

The Printer is configured like this:
smb://Printerserver/Printername
Comment by Andreas Radke (AndyRTR) - Tuesday, 02 November 2021, 20:43 GMT
@tpowa: please have look. This seems samba version update related.
Comment by Tobias Powalowski (tpowa) - Friday, 05 November 2021, 07:11 GMT
Please check how authentification is done and how the client communicates to the server, mostly old protocols are the error source.
Comment by Danny Schneider (schnedan) - Wednesday, 10 November 2021, 23:36 GMT
When I test my configs with testpram, its reported that weak crypto is allowed, smb version 2 till 3,
cups is configured with user/password - no kerberos or domains. Simple plain old workgroup model.

All configs are more or less 1:1 what is still in the wiki...

I do not see any error or problem here.
Comment by Tobias Powalowski (tpowa) - Thursday, 11 November 2021, 07:24 GMT
Try to use smb3 and do not allow smb2 anymore.
Comment by Danny Schneider (schnedan) - Friday, 19 November 2021, 11:00 GMT
In what sense that should be related to the fact: old package and Windows as printing client works, linux and new package not. And what should I do with printing clients which I can not update to smb3?

Is the reported error message Tree connect failed (NT_STATUS_BAD_NETWORK_NAME) related with smb2/3 ? I would like to understand why I should change something prior to just change it.
Comment by Danny Schneider (schnedan) - Saturday, 20 November 2021, 20:43 GMT
so I set both newer samba Computers to smb3 and also variated some other things. Result: many wasted hours, no success. The old PC with the lesser version still prints instantly as soon I hit print, the newer version dont.
also my sat-receiver with an older samba version is able to scan and show all PC's with samba and all shares.
All PC's with arch (also the one with printing is OK), do not show anything with smbtree (that worked in the past!, but I cant say when it stopped working)
Comment by Danny Schneider (schnedan) - Saturday, 20 November 2021, 22:57 GMT
Ok, seems like I was able to resolve the Problem
Comment by Andreas Radke (AndyRTR) - Sunday, 21 November 2021, 09:09 GMT
For documentation please let other know what was your solution.

Loading...