Hi, I've got an IPv6-only Linux machine (Debian wheezy, with Samba 4.1 from backports). It turns out that while it can use Samba itself just fine, winbind not so much. Any operation I do (e.g. wbinfo -u) yields WBC_ERR_DOMAIN_NOT_FOUND. Adding a working IPv4 address, e.g. by running dhclient eth0, pretty much immediately makes winbind work. As far as I understand, AD is supposed to work fine in a singlestacked IPv6 world, and I haven't seen any problems running AD over IPv6-only in Windows 7 (against the same AD PDC), so I suppose this is a client issue.
Can you run winbindd and wbinfo with debug 10 and get some logs for us to look at please ?
Created attachment 10609 [details] /var/log/samba, newly cleared before starting samba and winbind
Of course. Attached. I tried running (with some typos inbetween): root@nemesis:~# wbinfo -u root@nemesis:~# wbinfo -u root@nemesis:~# wbinfo -i sesse failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND Could not get info for user sesse I don't know, unfortunately, how to run wbinfo itself with debug 10. Could you enlighten me?
Just use: wbinfo -d10 <other args>
Nope, that gives me “Invalid option”.
Oh, my mistake - that should work globally in all Samba tools but I guess it got hijacked here for the "domain" option. Try setting: debug level = 10 in the smb.conf and re-doing the wbinfo.
Nope, wbinfo does not output any debug info even with debug level = 10. It doesn't even read smb.conf, from what I can gather from an strace.
Hm. I started debugging this, and now I'm suddenly unable to reproduce it. I can reboot and do operations just fine with IPv6-only. A bunch of things have changed, so it's hard to say what happened, but I'm closing this for now.
Great ! Did anything in winbindd change, or was it only other components ?
I didn't change any code short of applying the patch from #11049, which seems unrelated. So I believe the difference must either be a) luck, or b) configuration/environment/LDAP contents changes (of which there were quite a few).