https://bugs.kde.org/show_bug.cgi?id=431050
--- Comment #29 from Kai Krakow <[email protected]> --- I think there are several failure modes with DFS, and they do not properly bubble up into kioworker or Dolphin: 1. If the DFS referal doesn't include the FQDN, this often results in slow operation or timeouts for Linux clients: - Usually, smbclient will show "do_connect: Connection to srv-file-01 failed (Error NT_STATUS_NOT_FOUND)". - Dolphin will show no error but present an empty folder. FIX -> ask your admins to setup the DFS referals with the FQDN, otherwise there are multiple failure scenarios if connected via VPN, or slow DNS resolves because other local domains are queried first and may even resolve the IP. Always use FQDNs. 2. If you do not supply your logon domain with your user name, following the DFS referal will end in authentication errors because you did not get negotiate a session valid across the whole domain: - Usually, smbclient will show "session setup failed: NT_STATUS_LOGON_FAILURE". - Dolphin currently shows no error but presents an empty folder, I think it showed an auth error in an older version but leaving you clueless why it asked... FIX -> Supply your logon domain with your username, e.g. "smbclient -U DOMAIN/user ...". If Dolphin asks, try "[email protected]" instead. 3. I'm not sure why the last error occurs that some users reported: - smbclient can show "session setup failed: NT_STATUS_NO_MEMORY". - Again, Dolphin likely doesn't show the error but shows an empty folder instead. GUESS -> I fixed both problems 1 and 2 here, smbclient works, Dolphin still fails (or kioworker?) - so maybe I got problem 3 now, or a whole different problem? kioworker doesn't log much. It seems to log only its own interpretation of the error situation which is obviously wrong, I only see variantes of the following: Dez 28 17:16:08 jupiter kioworker[3216102]: Socket not connected QLocalSocket::PeerClosedError Dez 28 17:16:08 jupiter kioworker[3216102]: An error occurred during write. The worker terminates now. Dez 29 02:40:42 jupiter kioworker[30530]: Connection::send() called with connection not inited Dez 29 02:40:42 jupiter kioworker[30530]: An error occurred during write. The worker terminates now. These are the only two different messages logged by kioworker. Dolphin shows none of them but instead shows an empty folder. I didn't even try to write a file at this point - because it's obviously wrong that the folder is empty. That said, Dolphin seems to have very funny problems on its own with evaluating permissions or other properties. I have an NFS mount (not via kio) where Dolphin refuses to create folder or files directly in the mount point itself - it says "no permissions" or "not enough space". Creating files or folders via CLI shows no such problems. If I created a sub folder in the mount point, Dolphin no longer complains about it. So whatever problems Dolphin shows, there are at least two possible sources: kioworker and Dolphin itself. Since kioworker doesn't log anything useful, and Dolphin doesn't seem to pass errors from kio properly to the user but "invents" its own (seemingly sometimes purely based on wild guessing of an observed situation), debugging the situation is almost impossible. -- You are receiving this mail because: You are watching all bug changes.
