i’ve been having some problems with opensuse. As a result of this i’m planing on moving (the workstations of the company i work for) from opensuse to kubuntu.
Among other problems, however, there is one i’m particularly curious about why it is the way it is: SAMBA.
In KDE Neon (that i’m trying at the moment), when i access a windows share it opens blazing fast (like 1/2 sec at the most) while on the same machine, with opensuse (either leap or tumbleweed in a clean boot) it takes something like 20-30sec to open the same folder.
I would like to know why is that? What’s the problem?
Hi
Can’t comment on the desktop environment, but first thing I would look at is using the samba client to connect with some debug to compare, what versions of samba are in use across the systems, what about the /etc/samba/smb.conf files like. This will confirm it’s a desktop looking issue…
Almost 5 months later - i’m terribly sorry but the end&beginning of the year is totally crazy in this business (more even with all this covid thing)
In the meanwhile i had the move some machines to *buntu based-systems as a workaround.
But since i never actually liked it and always intended to return to suse here’s the wireshark output:
the thing is that it took something like a minute or more just to get the directory listed (in the file attached). it never takes less that ~45 seconds to list remote directories.
This does not happen in neon, for example, where i get the dirs list in something like ~1 second (i can post a neon output as well if you want)
I don’t get it!
Again, sorry for the late reply and thank you for your help
I had a quick look at your wireshark log, and I noticed a lot of ’ ICMP 148 Destination unreachable (Host administratively prohibited)’ events. So, I assume your server is blocking these pings from the client? (192.168.1.92 -> 192.168.1.33)
This may well be impacting with the samba session…
The weird thing is that this is happening only from the opensuse machines.
for example: Clean install from opensuse vs clean install from neon -> Suse takes +1min, neon takes ms to open the same remote directory.
So… i assumed it wasn’t a server problem, but a client problem.
I also considered that opensuse could be using some communication method that neon wasn’t… i’ve been sniffing around on the server trying to find some service or something i could enable to solve the problem - but with no luck what so ever.
I’m not observing this with my home or work environments. FWIW, I did find this long-running KDE thread of which I noted comment#17 which suggested possible issues related to user authentication (which may or may not be applicable to you)…
KDE System Settings > Network > Settings > Windows Shares
(…which apparently applies only in the context of network browsing.)
I have performed the “upgrade” to Argon/KDE repos but the problem still persists (even with the config on KDE System Settings > Network > Settings > Windows Shares).
I will try to format and make a clean install of Argon directly to see if it fixes the problem (but, TBH, i don’t have much faith in this).
If there is any more clues about it, please shoot…
Have you tried mounting the shares locally and accessing that way? You could try installing the Gnome file manager (nautilus) via the package manager, and see if the same behavior exists.