https://bugs.kde.org/show_bug.cgi?id=431050
--- Comment #26 from fdkde <fd483721...@mailbox.org> --- For some time I was able to access the network shares via our fully qualified domain name. When I joined the machine with the domain by using sssd and realmd, the access to the DFS shares broke again. First I thought the domain join was the cause why it reappeared but on a fresh VM install with Fedora 39 I run into the same problem again: session setup failed: NT_STATUS_NO_MEMORY Unable to follow dfs referral [\filecluster\personal$] Could not resolve \Personal\* session setup failed: NT_STATUS_NO_MEMORY Unable to follow dfs referral [\filecluster\personal$] Could not resolve \Personal\ The only configuration changes I did to the VM: - Put our domain as workgroup in /etc/samba/smb.conf - Put the FQDN as search domain in the NetworkManager GUI for the Ethernet connection - Changed the hostname in /etc/hostname including the actual domain name as the hostname of the VM defaulted to "fedora" For some reason the VM can access the share via //filecluster (as proof see screenshot above) which is a (virtual) DNS name and a Active Directory object for our file server cluster. However KIO (still) complains about having not enough memory: kf.kio.core: "Fehler. Nicht genĂ¼gend Speicher.\nsmb://filecluster/personal$" That doesn't work at all on my domain-joined host machine. Dolphin: 23.08.1 Operating System: Fedora Linux 39 (KDE Spin) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.11-300.fc39.x86_64 (64-bit) Graphics platform: Wayland -- You are receiving this mail because: You are watching all bug changes.