WSD Suppresses NetBIOS Discovery in Unraid 7.2.0-beta.1

📢 Bug Report: WSD Suppresses NetBIOS Discovery in Unraid 7.2.0-beta.1

Summary:
Starting with Unraid 7.1.4 and continuing in 7.2.0-beta.1, when WSD (wsdd2) is enabled, it suppresses NetBIOS-based network discovery on Windows clients. As a result, only one Unraid server with WSD enabled is visible in the “Network” section of Windows Explorer at a time — even though NetBIOS is also enabled on all servers.

🧪 Tested Configuration:

🔍 Diagnostic Results:

• When both UNRAID-03 and UNRAID-05 have WSD enabled:

  • Only one shows up in Windows Explorer (the “winner” of the WSD response)

  • The other is not visible — even though NetBIOS is still enabled and functional

• Manually typing \\UNRAID-03 or \\UNRAID-05 still works, proving Samba is fine

• Disabling WSD restores visibility via NetBIOS — but only if no other 7.2 server has WSD enabled

🔄 Expected Behavior:

• NetBIOS discovery should still function if disable netbios = no is explicitly configured

• WSD should not interfere with NetBIOS visibility

• Multiple Unraid servers should appear simultaneously in Windows Explorer, whether via WSD or NetBIOS

🧵 smb-extra.conf sample (on 7.2.0-beta.1 servers):

[global]

netbios name = UNRAID-03

local master = no

preferred master = no

os level = 20

disable netbios = no

wins support = no

✅ Related Windows Config:

• SMB1 client: Disabled

• NetBIOS over TCP/IP: Enabled

• nbtstat -A and nmblookup show proper NetBIOS registration

• WSD port 3702 open and used by /usr/sbin/wsdd2 -d -4

🧩 Conclusion:

This behavior appears to be a regression introduced in 7.1.4+, where the wsdd2 process is interfering with NetBIOS browsing — possibly due to conflicts in advertising the same Workgroup services or improper integration.

🙏 Request:

• Please confirm if this is an intentional change

• If not, could you investigate wsdd2 behavior and restore NetBIOS discovery support when enabled?