I’ve just setup Bazzite (atomic fedora) with KDE and was trying to access my SMB share (using ‘smb://host.domain.foo/share1/subfolder’).
I noticed, that I can access it without any authentication, as this specific share (‘share1’) is read-only accessible to anonymous users.
But as soon as I want to edit or create a file, it fails with a ‘permission denied’.
Even when specifying a permitted user to access this location with (using ‘smb://user@host.domain.foo/share1/subfolder’), I get a permission error and no chance to authenticate as my user.
One workaround I found was to go to my server and create a share (share-foo) that only this specific user has access to, not even enabling read-only access for anonymous users.
Trying to access share-foo, dolphin prompts me to authenticate. Here I can save my credentials and THEN have write access to my original share1.
Is there another way to force authentication in dolphin?
Or am I missing something obvious here?
This feels like a bug to me but I don’t want to rule out user error on my end.
What do you think?
Hi @johnandmegh,
Thank you for the link and suggestion!
The share is hosted by an UnraidOS server and it’s security level is set to ‘secure’, meaning:
The share is secured and all users, including guests, have read access. You can select which of your users have write access. ~ (Source: Unraid Docs [Links are prohibited ])
I also just noticed that I might not have explained my issue that well, I’ll try to clear it up:
My issue is not that anonymous- / guest-access is possible (It’s intended so I can access stuff in read-only without needing to log in).
My issue is that I wasn’t able to trigger any authentication flow in Dolphin to gain write access, although I had explicitely set a user in the connection string ‘user@host.domain.foo/share1’
So my expectation is to get an authentication prompt when specifying a user in the connection string, that hasn’t been used prior (or saved in a credential store like kwallet).
Right now I need to access a share that no one except my intended user has access to, to actually trigger the authentication prompt through the samba server.
I hope that clears up any confusion of my initial question.
Thanks - is it accurate to list out the sequence of events like this?
Two shares on one server
Share A: Anyone can read, but only you can write
Share B: Only you can read or write
Try to read A: Works
Try to write to A: Denied
Try to read B: Password prompt
Try to write to A: Works
I don’t personally know enough about Samba beyond the very basics, but if that’s an accurate framing then hopefully others here can recognize either a configuration trick needed, or a bug
I was working around ths issue by mounting my shares using fstab-mount-entries (and with the flag to make these mounts not a boot dependency / uncritical) and a locally stored credential file. Eventually, i moved to arch and away from atomic systems
Hi, I am in the same situation as OP and I’m baffled by the way Dolphin handles such a simple task that is to connect to a NAS using SMB without authentication by default.
No prompt, no asking what user I want to log into as… GNOME and Cinnamon have had this feature for a long time now. I don’t understand why no one bothered to make a default behavior that asks the user to enter login creds when attaching a drive.
I’ve had this issue with KDE since plasma 5. Its not a question of whether or not I can or can’t access a NAS SMB Share. It’s about the way I tend to need smb4k to save a default authentication config to access it in read/write, and launch it each time I log in instead of just being prompt to authenticate and save it for ever in Dolphin.
From my experience dating back to KDE4, it was always like that. (I’ve used Netrunner, KDE neon, Nobara) and the default behavior is always to automatically connect as Anonymous user.
Take a look at Gnome (ex. here being GNOME3), when you try to connect to a windows share, it ask you if you want to connect as a specific user instead of just defaulting to Anonymous (with no creds) by default.
The lack of prompt like this is what I find irritating in Dolphin (unless I’m missing something?) Like, sure, I can go and save it in a config file somewhere. But I would prefer for KDE to prompt me first to know what to do later with this connexion.
I don’t have the NAS setup required to replicate the exact steps, but so far, I’m not seeing that’s the case. Not a peep from stdout/stderr until I start looking at permissions.
Remember, on my Bazzite install, dolphin is a native binary, not a flatpak. So the entire flatpak permission model is out of scope (in my install, at least).
If the original peeps don’t reply this week, I’ll do my best to create some extra shares on my TrueNAS Scale box to try to replicate the issue more closely, but even without replicating the issue closely, just copying files between two Dolphin windows can get annoying on Bazzite. I’ve found myself resorting to smbclient more than once, and that is not a pleasant way to do things in comparison to Dolphin.
I’m using a fresh OpenSuse Tumbleweed install with Dolphin as a default with KDE Plasma.
I too have issues with the SMB not prompting me for credentials. For example I did a fresh initial boot yesterday (new HD and fresh install) and was happy because it prompted me to connect to my SMB share, I entered my creds and it worked as it should. I rebooted this morning and now there is no prompt and it won’t connect to the SMB share (because, apparently, I am trying to connect as AnonymousUser if this thread is accurate).
I can’t seem to determine the behavior, honestly - why it worked yesterday, then not today. Sometimes prompting, sometimes not. And there do not appear to be any options that I have been able to find to either set smb information, reset it, or even view what it’s doing.
I’d love to help out if I can, although I am new to all of this but have some programming experience.
])
