Thanks. I actually started with wsdd2 before removing it and installing
to wsdd to see if it made a difference (no).
Launching wsd with -vvv shows nothing when typing "net view \\debian"
on
Windows, so I suspect it's something in Windows, although the two
WSD-related services are running: ?Function Discovery Provider Host? and
?Function Discovery Resource Publication? are both "Running" and
"Manual/Manual (Trigger Start)".
Maybe for some reaons, my Windows 10 is not calling WSD and relying on
broadcasting?
On 17/10/2024 15:18, Ingo Asche via samba wrote:> If you're running Bookworm you can try WSDD2:
> https://packages.debian.org/bookworm/net/wsdd2
>
> Maybe it's faster...
>
> Regards
> Ingo
> https://github.com/WAdama
>
>
>
> Gilles via samba schrieb am 17.10.2024 um 15:01:
>> On 17/10/2024 12:52, Rowland Penny via samba wrote:
>> > You only need nmbd if you are using SMBv1 (which from your
smb.conf
>> > file you are not), I would disable it and add 'disable netbios
>> > = yes' to the 'global' part of your smb.conf file.
NetBIOS provided
>> > 'Network Browsing' which has been replaced by 'Network
Discovery' and
>> > that is what wsdd is for, but wsdd has nothing to do with Samba.
>> >
>> > You might as well disable the 'samba-ad-dc' service, you
are not
>> > running a Samba AD DC.
>>
>> Thanks for the infos. wsdd takes as much time to respond, but since
>> it has nothing to do with with Samba, I'll look at that particular
>> piece of software.
>>
>> =======>> systemctl stop nmbd
>> systemctl disable nmbd
>>
>> systemctl stop samba-ad-dc
>> systemctl disable samba-ad-dc
>>
>> vi /etc/samba/smb.conf:
>> [global]
>> ?
>> disable netbios = yes
>>
>> smbcontrol smbd reload-config
>> =======>>
>
>