Can't connect to samba after update; Service is running (2022-08-13++)

[Tacklezaza]

[ Dirty way Solution here]

Hello, Manjaro users!

I have very weird problem about Samba that service is working fine but I can’t connect to samba, every computer in my house that running latest version of Manjaro KDE is unable to connect to samba each other.

(2022-08-11 Is working fine, but after ~2022-08-13 Samba is broken )

[Samba working fine]
ManjaroLinux 21.3.6 (Ruah)

… Then full system update …

[Samba service is working but can’t access]
ManjaroLinux 21.3.6 (Ruah)

Output of systemctl status smb

● smb.service - Samba SMB Daemon
     Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; preset: disabled)
     Active: active (running) since Mon 2022-08-15 12:43:18 +07; 3min 25s ago
       Docs: man:smbd(8)
             man:samba(7)
             man:smb.conf(5)
   Main PID: 18333 (smbd)
     Status: "smbd: ready to serve connections..."
      Tasks: 4 (limit: 38440)
     Memory: 7.0M
        CPU: 308ms
     CGroup: /system.slice/smb.service
             ├─18333 /usr/bin/smbd --foreground --no-process-group
             ├─18335 /usr/bin/smbd --foreground --no-process-group
             ├─18336 /usr/bin/smbd --foreground --no-process-group
             └─18340 /usr/bin/smbd --foreground --no-process-group

ส.ค. 15 12:43:18 tackle-gaming smbd[18333]: [2022/08/15 12:43:18.098719,  0] ../../source3/smbd/server.c:1741(main)
ส.ค. 15 12:43:18 tackle-gaming smbd[18333]:   smbd version 4.16.4 started.
ส.ค. 15 12:43:18 tackle-gaming smbd[18333]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
ส.ค. 15 12:43:18 tackle-gaming systemd[1]: Started Samba SMB Daemon.
ส.ค. 15 12:43:19 tackle-gaming smbd[18339]: pam_unix(samba:session): session closed for user nobody
ส.ค. 15 12:43:19 tackle-gaming smbd[18360]: pam_unix(samba:session): session closed for user nobody
ส.ค. 15 12:43:27 tackle-gaming smbd[18423]: pam_unix(samba:session): session closed for user nobody
ส.ค. 15 12:44:27 tackle-gaming smbd[18867]: pam_unix(samba:session): session closed for user nobody
ส.ค. 15 12:45:27 tackle-gaming smbd[19261]: pam_unix(samba:session): session closed for user nobody
ส.ค. 15 12:46:27 tackle-gaming smbd[19716]: pam_unix(samba:session): session closed for user nobody

Output of systemctl status nmb

● nmb.service - Samba NMB Daemon
     Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled; preset: disabled)
     Active: active (running) since Mon 2022-08-15 12:43:18 +07; 4min 42s ago
       Docs: man:nmbd(8)
             man:samba(7)
             man:smb.conf(5)
   Main PID: 18332 (nmbd)
     Status: "nmbd: ready to serve connections..."
      Tasks: 1 (limit: 38440)
     Memory: 2.9M
        CPU: 35ms
     CGroup: /system.slice/nmb.service
             └─18332 /usr/bin/nmbd --foreground --no-process-group

ส.ค. 15 12:43:18 tackle-gaming systemd[1]: Starting Samba NMB Daemon...
ส.ค. 15 12:43:18 tackle-gaming nmbd[18332]: [2022/08/15 12:43:18.060525,  0] ../../source3/nmbd/nmbd.c:901(main)
ส.ค. 15 12:43:18 tackle-gaming nmbd[18332]:   nmbd version 4.16.4 started.
ส.ค. 15 12:43:18 tackle-gaming nmbd[18332]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
ส.ค. 15 12:43:18 tackle-gaming systemd[1]: Started Samba NMB Daemon.
ส.ค. 15 12:43:18 tackle-gaming nmbd[18332]: [2022/08/15 12:43:18.065878,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
ส.ค. 15 12:43:18 tackle-gaming nmbd[18332]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.6 for name TACKLE<1d>.
ส.ค. 15 12:43:18 tackle-gaming nmbd[18332]:   This response was from IP 192.168.1.25, reporting an IP address of 192.168.1.25.

My Samba config smb.conf

[global]
   workgroup = TACKLE
   dns proxy = no
   log file = /var/log/samba/%m.log
   max log size = 1000
   client min protocol = SMB2
   server role = standalone server
   passdb backend = tdbsam
   obey pam restrictions = yes
   unix password sync = yes
   passwd program = /usr/bin/passwd %u
   passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
   pam password change = yes
   map to guest = Bad Password
   usershare allow guests = yes
   name resolve order = lmhosts bcast host wins
   security = user
   guest account = nobody
   usershare path = /var/lib/samba/usershare
   usershare max shares = 100
   usershare owner only = yes
   force create mode = 0070
   force directory mode = 0070

[D]
   comment = Local Disk 01
   path = "/mnt/Local_Disk_01/"
   guest ok = no
   writable = yes
   browsable = yes
   valid users = tackle

I already tried Minimal configuration Like this one But still not working

This is used to be working but latest update it’s break Samba in someway that I can’t find solution…
I can’t create share as well (Before full update is working)

I have no idea what wrong with my Samba, I never facing this problem before
Any comment or suggestion is appreciated

Sorry for my English

Thank you
Apidech T.

[linux-aarhus]

@Tacklezaza

   force create mode = 0070
   force directory mode = 0070

At first glance - that looks weird

You are using nmb but you have no netbios name = in smb.conf

It is difficult to point out what exactly is your issue - my best suggestion is to go over the Arch Wiki on Samba.

https://wiki.archlinux.org/title/Samba#Advanced_Configuration

[Tacklezaza]

Hello,

Thank you for your quick reply, I sorry but I think I don’t need to be in Advance Configuration Can I just use something that simple like normal user? since I’m still new to Samba

Now I’m change my config to something that very basic, but still not working

My current smb.conf

[global]
   workgroup = TACKLE
   server string = Manjaro Samba Server
   server role = standalone server
   log file = /var/log/samba/log.%m
   max log size = 50
   guest account = nobody
   map to guest = Bad Password

   min protocol = SMB2
   max protocol = SMB3

[D]
   comment = Local Disk 01
   path = "/mnt/Local_Disk_01/"
   guest ok = no
   writable = yes
   browsable = yes
   valid users = tackle

After change my config, systemctl status smb output still the same, Loaded: loaded, Active: active (running)
Do I have to disable nmb service? or what should I do that I can use Samba like normal people do

Now my Dolphin and smbclient still unable to connect to Samba

Thank you
Apidech T.

//Edit more info
Enable Usershares I’m already follow that (Enable Usershares) but still no luck

net usershare add: cannot convert name "Everyone" to a SID. The transport connection is now disconnected..

net usershare add: cannot convert name "tackle" to a SID. The transport connection is now disconnected..

[Tacklezaza]

Maybe I have to stay in old version while I’m experiment and troubleshooting my Samba. Or maybe I have to try Samba in Fresh Install Manjaro in VM

For now I’m using Timeshift back to previous version, since I use samba in my daily workflow.

I’m gonna stop post this thread until I found solution or someone reply this thread. I’m always searching for solution…

If I found solution or I have any update, I’ll post it here.
Any comment or suggestion is appreciated

Thank you
Apidech T.

[joseheitor]

Same problem on my system++

Also reverted to prior-to-upgrade on the 13th with Timeshift and proper operation restored.

Had a look at the changelog for Samba (which was upgraded in the update from 4.16.4-2 to 4.16.4-3), and looks like minimal changes made. (https://github.com/archlinux/svntogit-packages/commit/ad2a775e789845c23b0a6ac48136b732cef11821)

Hopefully a Samba guru will have some idea of what caused the problem and how to address it? (Although, simply excluding the SAMBA package from the update does not prevent the problem…so the problem could lie within a dependency?)

[grendelx]

Hello everyone,
I am experiencing the same challenge(or should we call it a nightmare?) as you guys, just on the Manjaro Gnome Edition.
everything works again by reverting through timeshift to a previous date. (halleluja!!!)
So I did a new install of Manjaro Gnome on a second partition. tried the same smb.conf from the old install without success.
Installing the smb.conf from manjaro-setting-samba in the Manjaro repo, the share to the Home folders is working, but creating a new share on another drive, added to the same smb.conf, doesn’t.
Downgrading to a previous Samba Version, the same 4.16.1-4 from the old install, onto the new install did not solve the problem.
Days Ago, before everything stopped working, I noticed I could not access the host directly through a windows client, but I had to address the host share directly.
Then after one of the latest updates, not even that.

In not a Linux Guru, but I’m able to fix usually things by going through the Forums,
but this time it’s beyond beyond.

I’m on the reverted setup atm, so I don’t remember the error messages exactly,
but Windows clients complain about not having the proper access rights.
the same happens when trying with Gnome files on the same machine.

So maybe it’s not Samba but the way access rights and ownership are granted to the mounted and shared resources that have changed between updates.
Just my 2cents…

[yarass]

Hi, This is my first forum post. I have been fighting a similar problem since Thursday. First I noticed that there is an update from samba 4.16.4-1 to 4.16.4-2, on Saturday there was a re-update on 4.16.4-3 and there was still this problem both mate at the top. I checked on a clean install on virtualbox and upgrading to samba 4.16.4-3 everything works fine. The current system update also turns off avahi-daemon automatically. With resource access it looks like the update changes the permissions on individual resources and you have to do chmod manually. I also change the permissions in the system, but I don’t know exactly where. Getting to the bottom, I accidentally booted from pendriva live install and did not format the drive on which the system is installed. It turned out that all my personal settings were kept, because I didn’t throw anything from the home directory, but it also fixed sambe and other file permissions on the system. Samba is working fine. I don’t know if this is a coincidence, but it helped me. Sorry for my english, but i don’t know the language and i use google translator.

[Tacklezaza]

Thank you for all reply, comment and suggestion!
I’m glad that I’m not facing this problem alone

I hope guru or someone will solve our problem soon…

[grendelx]

tried a partial update, office, kernel and major apps we use.
after reboot, everything works. (blessed be the fruit!)

tried another partial update, this time only Samba & smbclient.
after reboot shares are not accessible! (WTF)

timeshifted back and updated everything else but Samba & smbclient.
after reboot shares are not accessible! (WTF2)
so it looks like the issue is not only in the samba packages.

so I’m doing the timeshifting again…

[linux-aarhus]

I think there has been bugfixes to samba.

This could possibby include permissions which where previously not enforced - but now they are - and therefore your shares fail - due to permissions or lack thereof perhaps even user/group inconsistencies.

You should all check how your samba user(s) and their groups and how permissions are defined and reflected on the actual filesystem.

[grendelx]

believing this to be the culprit, I tried every possible combo, but still no joy.

my shares are mounted in /run/media/grendelx through fstab
I tried to mount them as root and as a user with all permissions drwxrwxrwx
I added myself to the samba users
in every case, the resources are accessible through filemanager, just not through the network,
doesn’t matter if using the windows client or the host machine itself.

I tried arch wiki, manjaro how-to, and all the recent tutorials I could find, and i can’t get samba shares to work on the last system update.

I don’t think I have enough know-how to solve this issue by myself.

but if I may suggest…
if you “linus-aarhus” are running the latest release of manjaro
if you could try to mount a second drive under /run/media/youraccount through fstab
and try to mount it as a share with samba and browse it through a file manager or windows client
just to confirm if it works or not

[linux-aarhus]

@grendelx

if you “linus-aarhus” are running the latest release of manjaro
if you could try to mount a second drive under /run/media/youraccount through fstab

I am - and no I wont use /run/media in /etc/fstab

@grendelx

/run/media/youraccount

But that is where you make a huge mistake - you cannot use /run - it is volatile an recreated on each boot.

If you wanna make sure your shares are consistent - use a predicatable - non system mountpoint.

NEVER use

• /run/..... bla
• /mnt/.....bla

Create your own predictable structure - I really don’t care what you call it - I always use /data/…bla or as I have lately been doing /a/…bla

[yarass]

/ media / dev1
/ mount / drive1

won’t work, I tried

permission changes, i tried, doesn’t work

I just managed to get it to share

smb: // host / home_dir /

and nothing else could be accessed

later only detection works on smb: // ip / homedir /

and nothing but the home directory could be shared

[linux-aarhus]

I don’t know what to advise - Linux is not Windows

Linux requires a thought through setup when it comes to sharing - and quite frankly there is a huge diffference between being a server or a client - samba wise.

You cannot use LInux as you use Windows because Linux is a born networked system - Windows network sharing has always been an afterthought.

I remember Window 3.11 - workgroups edition - the worst network client ever invented.

I created peer-to-peer sharing using Novell networking client using token ring networking back in late 80’ies

[grendelx]

ok, that is maybe not the proper place to mount stuff
this solution came up years ago following howtos and tutorials on arch & manjaro forums
so I will mount them somewhere else.

but if you could try it your way whatever it is, to see if we are dealing with a samba problem or our incompetence, I think it would go a long way…

[linux-aarhus]

It appears you are having an xyproblem

you are mounting shares based on external device using a volatile location

That is going to create unpredictable issues with samba filesharing and as you don’t what you doing so you blame samba which is not your root cause

Your root cause is ignorance and windows expactations

• [root tip] [How To] Use systemd to mount ANY device

[yarass]

I don’t know what to sadvise - Linux is not Windows

Linux requires a thought through setup when it comes to sharing - and quite frankly there is a huge diffference between being a server or a client - samba wise.

Cytat

You cannot use LInux as you use Windows because Linux is a born networked system - Windows network sharing has always been an afterthought.

I remember Window 3.11 - workgroups edition - the worst network client ever invented.

I created peer-to-peer shareing using Novell networking client using token ring networking back in late 80’ies

Cytat
You write generics, we know it, linux is not windows.

The problem is that a clean fresh install of the system and updating samba to 4.16.4-3 works fine. And when there is some time the system on the disk and you are doing the update, samba crashes. Have you seen a system that does this?
changing permissions, writing, reading resources does not change anything after such a strange update.

And here everything has fallen apart, so we are looking for a solution. The np file of my samba configuration is the same as it was. Resource permissions have always been and I have been fine. After the last update, the only resource I can share is the home / public directory.

[global]
   workgroup = WORKGROUP
   dns proxy = no
   log file = /var/log/samba/%m.log
   max log size = 1000
   client min protocol = SMB2
   server role = standalone server
   disable netbios = no
   dns proxy = no
   passdb backend = tdbsam
   obey pam restrictions = yes
   unix password sync = yes
   passwd program = /usr/bin/passwd %u
   passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
   pam password change = yes
   map to guest = Bad Password
   usershare owner only = false
   usershare allow guests = yes
   name resolve order = lmhosts bcast host wins
   security = user
   guest account = nobody
   usershare path = /var/lib/samba/usershare
   usershare max shares = 100
   usershare owner only = yes
   force create mode = 0070
   force directory mode = 0070
   load printers = no
   printing = bsd
   printcap name = /dev/null
   disable spoolss = yes
   show add printer wizard = no

[homes]
   comment = Home Directories
   browseable = no
   read only = yes
   create mask = 0700
   directory mask = 0700
   valid users = %S

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no

[mp3]
   comment =  mp3
   path = /media/work/mp3/
   public = yes
   writable = yes
   browsable = yes
   read only = no
   available = yes
   guest ok = yes
   create mask = 0777
   directory mask = 0777

[filmy]
   comment =  filmy
   path = /media/work/Filmy/
   public = yes
   writable = yes
   browsable = yes
   read only = no
   available = yes
   guest ok = yes
   create mask = 0777
   directory mask = 0777

[yarass]
   comment =  yarass
   path = /home/yarass/
   public = yes  
   writable = yes
   browsable = yes
   read only = no
   available = yes
   guest ok = yes
   create mask = 0777
   directory mask = 0777

This configuration on a fresh install + update works fine.

On old installation + update only works

[yarass]
   comment =  yarass
   path = /home/yarass/
   public = yes  
   writable = yes
   browsable = yes
   read only = no
   available = yes
   guest ok = yes
   create mask = 0777
   directory mask = 0777

[linux-aarhus]

you are so completely messing system permissions

@yarass

   path = /home/yarass/
   public = yes  
   writable = yes
   browsable = yes
   read only = no
   available = yes
   guest ok = yes
   create mask = 0777
   directory mask = 0777

what do you think you are doing?

making everything inside your home world read/write?

No matter what you tell samba to do here your effecitive filesystem permission prevents it.

Samba will never exceed actual filesytem permissions - no matter what you tell it to do.

[yarass]

This is what it is supposed to be, this is my internal home network, it is used by 2 users and they are both supposed to have access to this place.
I might as well provide a public directory.

  path = /user/public
   public = yes  
   writable = yes
   browsable = yes
   read only = no
   available = yes
   guest ok = yes
   create mask = 0777
   directory mask = 0777

[linux-aarhus]

The majority of issues regarding samba is the ignorance surrounding windows file sharing - which is not samba. Samba is an implementation using the Windows filesharing protocols and thus needs to be setup correctly. It is not like Windows → rightclick → share → done

Even if the file manager pretents to be able to do it - a lot of setup is assumed for this to work.

@yarass

path = /user/public

Then what are your effective filesystem permissions on the folder?
And did you create a priviliged group?
And did you assign the relevant users as members of group?