Printing problems in cups+samba in slackware-current

sairum · 05-09-2019, 09:02 AM

Configuration: Slackware-current from today (9/5/2019)
CUPS : cups-2.2.11-x86_64-1
SAMBA: samba-4.10.2-x86_64-1

Printing to a printer share in a windows machine fails. Test with smbclient to check if connection is OK (10.221.100.2 is a printer server, not a networked printer! CIBIO is a Xerox Printer)

Code:

bash-5.0# smbclient -L 10.221.100.2 -U user%password 

        Sharename       Type      Comment
        ---------       ----      -------
        C$              Disk      Default share
        CIBIO           Printer   CIBIO - Cor
        Dados           Disk        
        Scanner         Disk      
Reconnecting with SMB1 for workgroup listing.
do_connect: Connection to 10.221.100.2 failed (Error NT_STATUS_RESOURCE_NAME_NOT_FOUND)
Unable to connect with SMB1 -- no workgroup available

According to this thread, the main developer of CUPS blames samba. I've tried the patch suggested (--with-experimental-mit-ad-dc in configure) with no success. Downgraded to samba-4.4.4-x86_64-3.txz (in slackware 14.2) and printing start working. Test with smbclient gives

Code:

bash-5.0# smbclient -L 10.221.100.2 -U user%password 
Domain=[ICAV] OS=[Windows Server 2012 R2 Standard 9600] Server=[Windows Server 2012 R2 Standard 6.3]

        Sharename       Type      Comment
        ---------       ----      -------
        C$              Disk      Default share
        CIBIO           Printer   CIBIO - Cor
        Dados           Disk        
        Scanner         Disk 
Connection to 10.221.100.2 failed (Error NT_STATUS_RESOURCE_NAME_NOT_FOUND)
NetBIOS over TCP disabled -- no workgroup available

TurboBlaze · 05-10-2019, 03:35 AM

Hi sairum

Open /etc/samba/smb.conf and add

Code:

client max protocol = NT1

for example

Code:

[global]
name resolve order = wins lmhosts bcast
# workgroup = NT-Domain-Name or Workgroup-Name, eg: LINUX2
   workgroup = WORKGROUP
   client max protocol = NT1
# server string is the equivalent of the NT Description field
   server string = Samba Server

and restart samba server

Code:

/etc/rc.d/rc.samba restart

BTW, for system-config-printer you can use pysmbc

sairum · 05-10-2019, 07:45 AM

Thanks TurboBlaze!

I've tried the client max protocol = NT1 setting in smb.conf already without any success. Note also that I don't have to restart samba (as you suggest in your post) because I have no samba server. I'm using only the client part of samba to be able to connect to a shared windows printer. The smbclient that comes with slackware 14.2 works as expected. The first line in the command output shows that it correctly identifies the server, its domain and its type

Code:

bash-5.0$ smbclient -L 10.221.100.2 -U user%password
Domain=[ICAV] OS=[Windows Server 2012 R2 Standard 9600] Server=[Windows Server 2012 R2 Standard 6.3]

                    Sharename       Type      Comment
[...]

On the contrary, the smb package provided by slackware current (4.10.2) doesn't work at all. The output of smbclient is

Code:

bash-5.0$ smbclient -L 10.221.100.2 -U user%password
Unable to initialize messaging context


                    Sharename       Type      Comment
[...]

Unable to connect with SMB1 -- no workgroup available

There were several things changing between stock-samba (4.4.4) and current-samba (4.10.2), apparently connected with encryption, and that may break compatibility with windows protocols, especially the old ones. Mind you that our windows server is quite dated (Windows Server 2012 R2). Meanwhile, because I usually avoid printing as much as I can, I can have a working smbclient (using old samba-4.4.4) and change it to samba-4.10.2 with CUPS in debug mode to try to figure out what the problem is. My only problem is time available do debug this. Nonetheless, although I know that I have a very particular configuration (slackware-current, Windows Server 2012 R2 and a Xerox 7830 printer) I opened this thread in case other people encounter a similar problem!

Cheers

TurboBlaze · 05-11-2019, 02:51 AM

sairum, two of the most important issues are reported on Launchpad at: