Tuxo Holic

Hello, with Debian Buster & Bullseye my bookmark stop working when the ip lease changes the next day. My router does offer dnsmasq for hostname advertising using dns or netbios using nmbd. testparm on my debian desktop tells me my name lookup is configured like this: name resolve order = bcast host lmhosts wins Is the ip value stored in the bookmark always used and the unc //hostname value ignored?

Update: Fix is to add "client min protocol = NT1" and "client max protocol = NT1" in the client smb.conf.

Update: Fix is to add "client max protocol = NT1" and "client max protocol = NT1" in the client smb.conf.

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...

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...

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...

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 share with or without NT1 inplace. Shipped version in Bullseye is 3.0.1 - it not longer allows to switch between nmblookup or net...

well, I don't have much time with the merge window closing soon so, there goes nothing ... I filed for a version bump in debian/testing and hope they also consider your patch and give you credits for it. Thank you Thomas for helping me out once again!