Package: winbind Version: 2:4.4.3+dfsg-4 Severity: important Dear Maintainer,
I have my debian stretch system set to use wins in nsswitch.conf. This has worked fine until recently, where I can no longer resolve Windows clients on the network. Using nmblookup and wbinfo manually works fine, ping does not. Linux clients broadcasting netbios names are resolved correctly. I've ensured that this is the case by temporarily having only wins support in the hosts entry of nsswitch.conf, where ping to the Linux clients worked fine. Stopping the nmbd service on the Linux clients stops name resolution, proving that it was in fact netbios resolution that was working. I've reproduced the issue in a VM, where I set up two clean installed Jessie installations. Both worked fine. I upgraded one of them to Stretch (dist-upgrade), and the Stretch VM could no longer ping the Windows clients. The Windows client I've tested with is Windows 10, version 1511. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages winbind depends on: ii libbsd0 0.8.3-1 ii libc6 2.22-9 ii libldap-2.4-2 2.4.42+dfsg-2+b2 ii libpopt0 1.16-10 ii libtalloc2 2.1.6-1 ii libtdb1 1.3.9-1 ii libtevent0 0.9.28-1 ii libwbclient0 2:4.4.3+dfsg-4 ii samba-common 2:4.4.3+dfsg-4 ii samba-common-bin 2:4.4.3+dfsg-4 ii samba-libs 2:4.4.3+dfsg-4 winbind recommends no packages. Versions of packages winbind suggests: ii libnss-winbind 2:4.4.3+dfsg-4 ii libpam-winbind 2:4.4.3+dfsg-4 -- no debconf information
