since some weeks (after a smbclient update), KDE dolphin cannot access shares of a Win10PC in the local network via URLs like “smb://@/”.
Access to a LinuxPC running samba server with such URLs still works fine, als the NAS function of the FritzBox can accessed via “smb://fritz.box”.
Any hints, why Dolphin (or smbclient?) cannot access Win10 (latest patched version 21H2) any more?
KDE Dolphin is using
kio-extras that has the known bug.
Try to do:
Open System Settings → Search: “Windows Shares” → Give any name and any password
Check to access
smb://fritz.box. If it does not work, you have to give IP address of Fritzbox, not hostname. e.g.
The issue is related to
That looks like
samba 4.16.0 or newer broke the compatibility e.g.
Another reason why I use
systemd-mounts or Smb4K. The former, especially, bypasses bugs in KDE.
This reminds me of the other KDE bug in which you must select and apply a setting in order to use
another setting, because this “ritual” properly resets the config file behind-the-scenes. 
Does Fall Apart effect work in your Kde Plasma? - #13 by winnie
Look the solution:
Two different laptops with up-to-date Manjaro. One with KDE 5.24 on STABLE branch, one with KDE 5.25. Neither will browse SMB shares on my network.
Booting from my Manjaro 21.2.6 USB works normally. I am presented with an authentication dialog.
What has changed, and how do I fix?
EDIT: A user on Reddit found a fix: In System Settings–>Network Settings–>Windows Shares, add ANY text to the user and password fields and restart Dolphin. Now I get a password prompt and can view and mount shares.
Dolphin: The file or folder smb://servername.local does not exist.
thanks for the hint with “System Setttings…”.
Unbelievable, but it works fine!!
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.