Hello.
The dolphin smb protocol stopped working after updating samba.
Everything works fine after restoring the update.
Slackware64-15.0 , samba-4.15.5-x86_64-1.txz

I'm having the same issue on current since the 4.15 update. 4.16 didn't fix it, either. If I try to load a samba share, I get an error that the file/folder doesn't exist. (I can ssh and ftp into it via console.) I can at least log in using Thunar, but if I try to load a directory on the server, it doesn't even give an error, time out, or hang. I was wondering if it were an issue with our fileserver, since it's a bit wonky. (Not sure what versions of samba my partner and my father-in-law are using since they're on Windows and OSX, respectively.)

Bug with samba 4.15 and above, or did a setting change?

I'm having similar issues on Slackware64-15.0 with thunar:
after updating samba from 4.15.5 to 4.15.7, both on the server and 4 clients, I'm no more able to browse the samba shares.
Dolphin continues to work normally, so I'm thinking about a thunar issue.

Cheers

A multilib issue? (I'm using multilib.)

Desktop issue? It was doing the same behavior on both XFCE and Enlightenment.

In my case, I don't use multilib.
Only kde.

After upgrading the samba, I compiled the dolphin and dolphin-plugins from the kde package but that didn't fix the problem.

Well I don't know if this will help or not

But samba-4.15.7 is running on my end on Slackware 15.0-64 being accessed via Dolphin (Not rebuilt) under KDE (no multilib)

When you updated from samba*.5 to samba*.7 did you perhaps overwrite your config files?

I don't think I did anything to the config...Rather, I was able to connect to our fileserver straight out of the box, as it were.

I didn't change anything in the configuration files.
I'm using a Synology server with smb3, smb2, smb1 support.

Oh, hey, I'm using a Synology server, too. Maybe the version of samba they're using? I don't think our Raspberry Pis are having the same issue, but I haven't updated mine to bullseye yet.

It seems the problem is with Synology.
Maybe there will be an update, we'll see.

I don't think it's a synology issue. Rolling back samba on slackware allows it to connect, although with current there have been some other library changes involved in samba. I installed 4.14 from the cumulative archive, and the error went away, but it didn't resolve the connection either. (Not unexpected, given how it's been recompiled against a few other library changes.)

ETA: https://community.synology.com/enu/forum/1/post/152404 Looks like it's got a very, very old version of samba. Probably just not compatible?

Yes, it is supposed to be a big update.
My DSM DS220+, SMB Service 4.10.18-0434

https://www.synology.com/en-us/relea...2B#ver_42661-1

https://www.reddit.com/r/slackware/c...hares_anymore/ Someone else having the same issue. No follow ups, though. Not sure what version of samba they're using on the hosts.

For me, this is a problem on the Synology side.
When I run the samba server on the local machine, everything works.

https://forum.garudalinux.org/t/dolp...nd-fails/18610 Someone else with the same thing. They didn't solve it, though, but instead switched to ssh/ftp.