Bug#825380: [Pkg-samba-maint] Bug#825380: Bug#825380: winbind: Netbios name resolution can't find Windows clients

2017-01-29 Thread Tim Boundy
No, I said the patch resolves the second issue (system error ping failure regression) I found while testing to see if the first had changed at all. To summarise, the original problem reported was that when nmblookup finds two potential addresses for a NETBIOS name, ping no longer attempts to

Bug#825380: [Pkg-samba-maint] Bug#825380: Bug#825380: winbind: Netbios name resolution can't find Windows clients

2017-01-29 Thread Mathieu Parent
" 2017-01-28 15:51 GMT+01:00 Tim Boundy : > Why was this bug closed? The original reported issue hasn't been addressed > at all. I thought it was, as you said "That patch seems to have resolved the System error issue". Can you strace it again? Regards -- Mathieu Parent

Bug#825380: [Pkg-samba-maint] Bug#825380: winbind: Netbios name resolution can't find Windows clients

2017-01-28 Thread Tim Boundy
Why was this bug closed? The original reported issue hasn't been addressed at all.

Bug#825380: [Pkg-samba-maint] Bug#825380: winbind: Netbios name resolution can't find Windows clients

2016-11-13 Thread Tim Boundy
That patch seems to have resolved the System error issue. On 14 November 2016 at 07:24, Mathieu Parent wrote: > Hi TIm, > > Can you try the proposed patch: > https://bugzilla.samba.org/attachment.cgi?id=12657=edit > > Regards > > 2016-11-13 2:39 GMT+01:00 Tim Boundy

Bug#825380: [Pkg-samba-maint] Bug#825380: winbind: Netbios name resolution can't find Windows clients

2016-11-13 Thread Mathieu Parent
Hi TIm, Can you try the proposed patch: https://bugzilla.samba.org/attachment.cgi?id=12657=edit Regards 2016-11-13 2:39 GMT+01:00 Tim Boundy : > Yes, I have 2:4.4.7+dfsg-1 of libnss-winbind installed > > I've attached the 'strace ping google.com' output when using wins in >

Bug#825380: [Pkg-samba-maint] Bug#825380: winbind: Netbios name resolution can't find Windows clients

2016-11-12 Thread Tim Boundy
Yes, I have 2:4.4.7+dfsg-1 of libnss-winbind installed I've attached the 'strace ping google.com' output when using wins in nsswitch.conf On 13 November 2016 at 08:44, Mathieu Parent wrote: > is.Hello, > > 2016-11-09 10:14 GMT+01:00 Tim Boundy : > >

Bug#825380: [Pkg-samba-maint] Bug#825380: winbind: Netbios name resolution can't find Windows clients

2016-11-12 Thread Mathieu Parent
is.Hello, 2016-11-09 10:14 GMT+01:00 Tim Boundy : > I've just updated to 2:4.4.7+dfsg-1 to see if there's any improvement. > Massive regression. Now I can't ping via dns. > > ping: google.com: System error > > If I remove wins from nsswitch.conf, dns starts working again. Do

Bug#825380: winbind: Netbios name resolution can't find Windows clients

2016-11-09 Thread Tim Boundy
I've just updated to 2:4.4.7+dfsg-1 to see if there's any improvement. Massive regression. Now I can't ping via dns. ping: google.com: System error If I remove wins from nsswitch.conf, dns starts working again.

Bug#825380: winbind: Netbios name resolution can't find Windows clients

2016-06-09 Thread Tim Boundy
I've noticed that my Windows client is advertising multiple entries: root@fusion:~# nmblookup prodigy 192.168.0.55 prodigy<00> 192.168.56.1 prodigy<00> It is doing this because there is a virtual network switch (VirtualBox) and it's accessible through either IP address. If I disable the virtual

Bug#825380: winbind: Netbios name resolution can't find Windows clients

2016-05-26 Thread Tim Boundy
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,