After server update today no client can access SMB share

My main box running 15.3 is also a SMB and NFS server for devices in the local network, namely two fireTV sticks (using Kodi) and VLC on a couple of android phones. The devices only access share Gravados of the shares below:

bruno-03:~> cat /etc/samba/smb.conf 
# smb.conf is the main Samba configuration file. You find a full commented 
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the 
# samba-doc package is installed. 
[global] 
        workgroup = WORKGROUP 
        passdb backend = tdbsam 
        printing = cups 
        printcap name = cups 
        printcap cache time = 750 
        cups options = raw 
        map to guest = Bad User 
        logon path = \\%L\profiles\.msprofile 
        logon home = \\%L\%U\.9xprofile 
        logon drive = P: 
        usershare allow guests = No 
        wins support = No 
        netbios name = bruno-03 
        min protocol = SMB2 
        add machine script = /usr/sbin/useradd  -c Machine -d /var/lib/nobody -s /bin/false %m$ 
        domain logons = No 
        domain master = No 
        security = user 

[homes] 
        comment = Home Directories 
        valid users = %S, %D%w%S 
        browseable = No 
        read only = No 
        inherit acls = Yes 
[profiles] 
        comment = Network Profiles Service 
        path = %H 
        read only = No 
        store dos attributes = Yes 
        create mask = 0600 
        directory mask = 0700 
[users] 
        comment = All users 
        path = /home 
        read only = No 
        inherit acls = Yes 
        veto files = /aquota.user/groups/shares/ 
[groups] 
        comment = All groups 
        path = /home/groups 
        read only = No 
        inherit acls = Yes 

## Share disabled by YaST 
# [printers] 
#       comment = All Printers 
#       path = /var/tmp 
#       printable = Yes 
#       create mask = 0600 
#       browseable = No 

## Share disabled by YaST 
# [print$] 
#       comment = Printer Drivers 
#       path = /var/lib/samba/drivers 
#       write list = @ntadmin root 
#       force group = ntadmin 
#       create mask = 0664 
#       directory mask = 0775 

[Publico] 
        comment = All users 
        inherit acls = Yes 
        path = /home/blimmer/Torrents/Gravados/Publico 
        read only = no 
        guest ok = Yes 

**Gravados**] 
        comment = All users 
        inherit acls = Yes 
        path = /home/blimmer/Torrents/Gravados 
        read only = Yes 
        guest ok = Yes 

[Trabalho] 
        comment = Trabalhos em curso 
        inherit acls = Yes 
        path = /home/blimmer/Trabalhos em curso 
        read only = No 
        guest ok = Yes 

[Arquivo] 
        comment = Arquivos de trabalho 
        guest ok = Yes 
        inherit acls = Yes 
        path = /home/trabalho/Arquivo 
        read only = Yes 

bruno-03:~> 

After yast update today, when IINM there were some smb updates, none of the devices can see the share anymore.

Tested with firewall disabled through yast.

This is a recurring problem, both with SMB and NFS (v3), which currently is also not working.

Any tips?

Thanks

Hi Bruno,

That’s strange. Both is working well on my homeserver with latest 15.3 updates. All setup done with YaST. For starters I’d check “systemctl status smb” but how should that be related to nfs? Can you ping that box at all?

Hi kasi,

No, nfs is another matter, not related to this issue. I just mentioned it because I was out of sharing options.

What devices are you accessing your working smb share?

Anyway, I’ve made some progress.

I created a smb share in another box that is running LEAP 15.2, samba version 4.11.14+git…, and it is accessed normally by both the fireTV stiks and VLC on mobiles.

So I downgraded samba on the server from 4.15.4+git… to 4.13.13+git…, and it is working again.

Now, I still couldn’t access a share from a W10 machine, so:

bruno-03:~> systemctl status smb 
**●** smb.service - Samba SMB Daemon 
     Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled) 
     Active: **failed** (Result: exit-code) since Tue 2022-02-08 16:15:58 -03; 4h 18min ago 
       Docs: man:smbd(8) 
             man:samba(7) 
             man:smb.conf(5) 
   Main PID: 2926 (code=exited, status=1/FAILURE) 
     Status: "daemon failed to start: Samba failed to init printing subsystem" 
blimmer@bruno-03:~> systemctl start smb     
blimmer@bruno-03:~> systemctl status smb 
**●** smb.service - Samba SMB Daemon 
     Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled) 
     Active: **active (running)** since Tue 2022-02-08 20:34:55 -03; 3s ago 
       Docs: man:smbd(8) 
             man:samba(7) 
             man:smb.conf(5) 
    Process: 8894 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS) 
   Main PID: 8898 (smbd) 
     Status: "smbd: ready to serve connections..." 
      Tasks: 4 (limit: 4915) 
     CGroup: /system.slice/smb.service 
             ├─8898 /usr/sbin/smbd --foreground --no-process-group 
             ├─8900 /usr/sbin/smbd --foreground --no-process-group 
             ├─8901 /usr/sbin/smbd --foreground --no-process-group 
             └─8902 /usr/sbin/smbd --foreground --no-process-group 
bruno-03:~> 

I think that it is actually a problem with the update, either it is a regression (or a feature), or it just didn’t restart samba.

I’ll probably update again and see if smb is restarted automatically or not, but not now.

Regards

delete the print share lines in /etc/samba/smb.conf - these are what I had to remove to get smb to start.

[printers]
    comment = All Printers
    path = /var/tmp
    printable = Yes
    create mask = 0600
    browseable = No
[print$]
    comment = Printer Drivers
    path = /var/lib/samba/drivers
    write list = @ntadmin root
    force group = ntadmin
    create mask = 0664
    directory mask = 0775

That is what I had to do to get it to work. then sudo systemctl restart smb nmb.

That’s actually just my wife’s office W10 laptop. I just set up a few shares for her in homeoffice. And it worked yesterday for a test with Dolphin on my laptop. Company W10 laptop can’t access as it is dedicated to company domain. (I guess that’s the reason.)

Here it’s the latest samba version:

~> LANG=C zypper if samba 
Loading repository data... 
Reading installed packages... 


Information for package samba: 
------------------------------ 
Repository     : Update repository with updates from SUSE Linux Enterprise 15 
Name           : samba 
Version        : 4.15.4+git.324.8332acf1a63-150300.3.25.3 
Arch           : x86_64 
Vendor         : SUSE LLC <https://www.suse.com/> 
Installed Size : 1.7 MiB 
Installed      : Yes 
Status         : up-to-date 
Source package : samba-4.15.4+git.324.8332acf1a63-150300.3.25.3.src 
Summary        : A SMB/CIFS File, Print, and Authentication Server 
Description    :  
    Samba is a suite of programs that allows SMB/CIFS clients to use the 
    Unix file space, printers, and authentication subsystem. 

    The package named samba contains all programs that are needed to act as 
    a server.  The binaries expect the configuration file to be found in 
    /etc/samba/smb.conf

It’s also working with printer config lines - which I actually don’t use. After some wrong moves with permissions I could share it from the server via cups.

I had a similar issue, but possibly not the same, yesterday. Some Googling came up with this:
https://bbs.archlinux.org/viewtopic.php?id=269906

Adding:

disable spoolss = yes

Worked for me, but I don’t have shared printers on my server.

I had the same problem sins last kernel update and still had today after another another kernel update:


 ## systemd[1]: Starting Samba SMB Daemon... 
Feb 11 11:08:52 ## smbd[16228]: **[2022/02/11 11:08:52.837618,  0] ../../source3/smbd/server.c:1734(main)**
Feb 11 11:08:52 ## smbd[16228]: **  smbd version 4.15.4-git.324.8332acf1a63150300.3.25.3-SUSE-oS15.0-x86_64 started.**
Feb 11 11:08:52 ## smbd[16228]: **  Copyright Andrew Tridgell and the Samba Team 1992-2021**
Feb 11 11:08:52 ## systemd[1]: Started Samba SMB Daemon. 
Feb 11 11:08:52 ## smbd[16228]: **[2022/02/11 11:08:52.860214,  0] ../../lib/util/become_daemon.c:120(exit_daemon)**
Feb 11 11:08:52 ## smbd[16228]: **  exit_daemon: daemon failed to start: Samba failed to init printing subsystem, error code 13**
Feb 11 11:08:52 ## systemd[1]: **smb.service: Main process exited, code=exited, status=1/FAILURE**
Feb 11 11:08:52 ## systemd[1]: **smb.service: Failed with result 'exit-code'.**

Tested the solution above with downgrade to 4.13.13:


Feb 11 12:54:07 ## systemd[1]: Starting Samba SMB Daemon... 
Feb 11 12:54:07 ## smbd[21921]: **[2022/02/11 12:54:07.269289,  0] ../../lib/util/become_daemon.c:153(daemon_ready)**
Feb 11 12:54:07 ## systemd[1]: Started Samba SMB Daemon. 
Feb 11 12:54:07 ## smbd[21921]: **  daemon_ready: daemon 'smbd' finished starting up and ready to serve connections**

Viola! Now its working again with Win10/11 and Android :slight_smile: Thanks forum :wink: Maybe someone… Bugreport?

Same issue here. downgrading fixed the problem.

Adding

disable spoolss = yes

Under [Global] and then starting smbd will also remediate this issue.