SMB Not working after last updates

[brucecadieux]

Since the latest updates to Tumbleweed, None of the computers on my network can reach my tumbleweed machines file shares, I have shared the directories in /home. This has been working flawlessly as it always does for a very long time, but this last batch of updates seems to have broken something, SMB, NMB, and WSD are all running, not sure if it is a kernel issue, or a change in the smb protocols.
Running KDE PLasma, and as I said, documents, downloads, videos, music are all be ing shared and previous to the last batch of updates were all working perfectly.

Any assistance would be greatly appreciated.

[myswtest]

@brucecadieux wrote:

Since the latest updates to Tumbleweed, None of the computers on my network can reach my tumbleweed machines file shares, I have shared the directories in /home.

So, the machine sharing /home sub-directories … it’s running TW.

1. Are the other machines running TW?
2. Are there any error messages displayed at the remote machines when attempting to access the TW share machine?

[deano_ferrari]

I haven’t looked into this myself, but perhaps related to that reported here?

Anyone else seeing CIFS problems in Tumbleweed 7.x kernels?

I’m seeing problems with mounted SMB v1 folders in Tumbleweed with kernel 7.x. So far I’ve tested with 7.0.2, 7.0.7, 7.0.9, and 7.0.10 and have seen problems with all of them. The current longterm kernels, including the most recent 6.18.34 don’t seem to have this problem. The trouble seems to happen only with SMB v1 and not SMB v2 or v3 mounts and manifests as incomplete or garbled directory listings. Anyone else seeing this or have some clue on what’s happening or how to fix it?

Check existing bug reports too…
https://bugzilla.opensuse.org/buglist.cgi?quicksearch=smb&list_id=14258502

[brucecadieux]

From tumbleweed I get “No Shared Folders Found” message.

From Windows I get “This Folder is empty” message

[deano_ferrari]

Can you first verify that Samba is working locally on the Tumbleweed machine itself?
smbclient -L localhost -U <your_username>

[brucecadieux]

I have had the previous 7 kernels with no problems, only the latest updates did this, I downgraded the kernel to the previous one, and had teh same problem, so I am not sure what the issue is. These are not mounts, just simple smb shares on my network that I access in dolphin, or in explorer from windows…

[deano_ferrari]

Report back with the smbclient findings (my previous post).

Also testparm -s output please.

[brucecadieux]

ruce@Minisforum-PC:~> smbclient -L localhost -U bruce
Password for [WORKGROUP\bruce]:

    Sharename       Type      Comment
    ---------       ----      -------
    IPC$            IPC       IPC Service (Samba 4.24.3-git.475.629de6765b9SUSE-oS16.9-x86_64)

SMB1 disabled – no workgroup available
bruce@Minisforum-PC:~>

[brucecadieux]

bruce@Minisforum-PC:~> testparm -s
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback)

Server role: ROLE_STANDALONE

Global parameters

[global]
logon drive = P:
logon home = \%L%U.9xprofile
logon path = \%L\profiles.msprofile
map to guest = Bad User
printcap name = cups
usershare max shares = 100
idmap config * : backend = tdb
cups options = raw
bruce@Minisforum-PC:~>

[deano_ferrari]

Ok, so no shares listed. Are they defined in /etc/samba/smb.conf?

[brucecadieux]

It was set up through yast a long time ago, and has worked perfectly until last updates, TBH none of that output looks even relmotely to what it should be

[deano_ferrari]

Right… did you perhaps have these configured as usershares via Dolphin/Plasma (Properties > Share), rather than defining them manually in /etc/samba/smb.conf?

If so, please show the output from…

net usershare list
testparm -sv | grep usershare
ls -l /var/lib/samba/usershares

[brucecadieux]

I got it working, Very odd, smb.conf showed just homes, I added one share manually /home/bruce/Pictures restarted smd and nmb, and checked from windows and all of my shares were back, I am very confused, but it is working now and will leave it as is LOL

[deano_ferrari]

Just in case these are helpful to getting usershares (re)created…

Getting the infamouse "net usershare: usershares are currently disabled."

Searched and searched, tried every article that has that statement in it, all to no avail… # 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 = SOPRANOS 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\%…

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

[deano_ferrari]

Oh, good outcome. Case closed!

[brucecadieux]

Used to be all I had to do in Yast was tell it allow users to share home directories and that would allow me to share my folders using Dolphin setting up shares, apparantly something went haywire with the most recnt updates, needless to say it is working again . Thank you everyone fore your input

[deano_ferrari]

Yes, I think under the hood the YaST utility was essentially enabling Samba’s usershare functionality. Anyway, for others who may come searching, here’s what is required under the hood…

[global]
    usershare path = /var/lib/samba/usershares
    usershare max shares = 100
    usershare allow guests = no
    usershare owner only = yes

Of course the usershare directory needs to exist…

mkdir -p /var/lib/samba/usershares
chown root:users /var/lib/samba/usershares
chmod 1770 /var/lib/samba/usershares

Once that’s configured, there are a few different methods to create/manage usershares…

• Via Dolphin, select directory > Properties > Share
• Using net usershare.... commands
• Cockpit’s File Sharing module (where available)

I have cockpit-file-sharing installed (third-party means), and it does work, but the initial smb.conf usershare configuration had to be made first of course.

Another fishhook for Leap 16 users, is that it has adopted the modern user private groups (UPG) model by default, where each user’s primary group is the same as their username. That impacts on users being able to share folders conveniently. However, they could still use something like
sudo net usershare add Downloads /home/dean/Downloads and then check with sudo net usershare list.

`