Network printing via samba error (Canon MF4010)

Hello everyone!

In my work i use a pc in office LAN. The pc is running under Debian 10 "Buster" (gnome). In the LAN there is a pc running win xp with cannon MF4010 printer connected to it. This printer is shared in the LAN. Win xp pc domain name in the LAN is "PRINTERPC" and it's internal IP in 192.168.128.91.

Unfortunately i can't find a way to connect to the printer from my work pc. I have samba and smbclient installed as well as cups (it was in standard installation). Cups and samba services runs without errors or warnings. Automatic printer finder in gnome doesn't find the printer. I tried to find win xp pc and printer from terminal with

smbclient -L "PRINTERPC" -I 192.168.128.91 -N

My try was successful. I saw "Canon MF4010" in the output of the command (it's shared printer name). Anyway i couldn't find a way to print from it with terminal or from cups administrative tool. I always get

NT_STATUS_UNSUCCESSFUL

error.

I used this guide to set up printer. I found that on win xp pc NetBIOS it turned on so it cannot be a reason of the error. I'm certain that on any other pc in the LAN running windows i can print with the printer connected to the win xp pc.

I tried to set up the printer in cups web interface - windows printer via samba, address

smb://PRINTERPC/Canon MF4010

or

smb://PRINTERPC/Canon%20MF4010

or

smb://WORGROUP/PRINTERPC/Canon%20MF4010

The same error occurs if i tried to print something even test page.

There is no password needed to connect to the printer. Any ideas?

Please show your current /etc/samba/smb.conf configuration, in particular the '[global]' section. This is likely to be due to a SMB version mismatch. Windows XP is very old, and using SMBv1, while recent Linux samba clients will be using SMBv2. Using SMBv1 presents a well-known significant security risk...

https://techcommunity.microsoft.com/...B1/ba-p/425858
https://community.spiceworks.com/top...-smb1-insecure

Ideally, you should consider upgrading the Windows server, but it may be possible to upgrade the server to support a later samba protocol.

Try adding the following to the smb.conf global section

min protocol = SMB1

Restart cups.

That is an option, although it should probably be

client min protocol = NT1

(or similar), but be aware of the security risks with using this protocol.

Your probably correct. cups has it's own SMB backend i.e. smbspool but not exactly sure how it works in relationship with smb.conf except I read other threads that indicated it worked.