In Debian Buster "client max protocol = NT1" in smb.conf global section was needed to see all smb servers (older smb servers included). After setting this Dolphin and smb4k worked fine enough again.
In Debian Bullseye this is no longer the case: Dolphin works fine without "client max protocol = NT1" and stops working when protocol is forced to NT1. smb4k does not find shares with or without NT1 inplace.
Shipped version in Bullseye is 3.0.1 - it not longer allows to switch between nmblookup or net lookup method, what is it using these days?
nmblookup -w DOMAIN does list all present IPs in DOMAIN, so it should work fine if smb4k still uses nmblookup.
Last edit: Tuxo Holic 2021-04-20
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for not answering the first time. I seem to have missed your post.
Yes, this is the right setting for Smb4K 3.0.x and earlier. With the release of Smb4K 3.1.0, this adjustment in the smb.conf is obsolete, though. Here, DNS-SD (and optionally WS-Discovery) is used to find the servers. Also, you can adjust the protocol versions in Smb4K, if you need to.
Last edit: Alexander Reinholdt 2021-05-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just installed Zorin 16 and installed Smb4K. I've done the suggestions above to smb.conf and I still get the error message upon opening Smb4K. "The network communication failed with the following error message: The URL does not exist
Trying to connect to a Windows 10 file share.
Any other suggestions?
Last edit: James Lenaburg 2021-11-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In Debian Buster "client max protocol = NT1" in smb.conf global section was needed to see all smb servers (older smb servers included). After setting this Dolphin and smb4k worked fine enough again.
In Debian Bullseye this is no longer the case: Dolphin works fine without "client max protocol = NT1" and stops working when protocol is forced to NT1. smb4k does not find shares with or without NT1 inplace.
Shipped version in Bullseye is 3.0.1 - it not longer allows to switch between nmblookup or net lookup method, what is it using these days?
nmblookup -w DOMAIN does list all present IPs in DOMAIN, so it should work fine if smb4k still uses nmblookup.
Last edit: Tuxo Holic 2021-04-20
Update: Fix is to add "client min protocol = NT1" and "client max protocol = NT1" in the client smb.conf.
Last edit: Tuxo Holic 2021-05-27
Sorry for not answering the first time. I seem to have missed your post.
Yes, this is the right setting for Smb4K 3.0.x and earlier. With the release of Smb4K 3.1.0, this adjustment in the smb.conf is obsolete, though. Here, DNS-SD (and optionally WS-Discovery) is used to find the servers. Also, you can adjust the protocol versions in Smb4K, if you need to.
Last edit: Alexander Reinholdt 2021-05-27
Just installed Zorin 16 and installed Smb4K. I've done the suggestions above to smb.conf and I still get the error message upon opening Smb4K. "The network communication failed with the following error message: The URL does not exist
Trying to connect to a Windows 10 file share.
Any other suggestions?
Last edit: James Lenaburg 2021-11-30
Which version of Smb4K are you using?
Version 3.0.4 installed via Zorin Software app 3.36.1.
I tried downloading 3.1.1 and installing but the instructions in the readme do not work on Zorin 16.
If you want to try out Smb4K 3.1.1, maybe you would like to try the Smb4K binary from here: https://software.opensuse.org//download.html?project=home%3Aareinholdt&package=smb4k
Please follow the instructions given for Debian 11. I recommend that you add the repository under sources.list.d as described.
Smb4K 3.1.x should work with any recent Samba version.
Last edit: Alexander Reinholdt 2021-12-03