Miguel Medalha
2015-Apr-23 15:45 UTC
[Samba] RFC2307 attributes not being read by DC2 in 4.2.1
> > If you read what I wrote, you will see I said to replace 'winbindd' with > 'winbind'. We are referring to samba 4.2.1, as standard this uses the > separate 'winbindd' daemon instead of the 'winbind' built into the samba > daemon. >I read what I wrote but what I am saying is something different. The problem may lie not in the use of winbindd per se, it may lie in the use of winbindd *without disabling the internal winbind*. Maybe I'm wrong but trying it is not so big of an effort....
Rowland Penny
2015-Apr-23 16:11 UTC
[Samba] RFC2307 attributes not being read by DC2 in 4.2.1
On 23/04/15 16:45, Miguel Medalha wrote:>> If you read what I wrote, you will see I said to replace 'winbindd' with >> 'winbind'. We are referring to samba 4.2.1, as standard this uses the >> separate 'winbindd' daemon instead of the 'winbind' built into the samba >> daemon. >> > I read what I wrote but what I am saying is something different. The > problem may lie not in the use of winbindd per se, it may lie in the use > of winbindd *without disabling the internal winbind*. Maybe I'm wrong but > trying it is not so big of an effort.... > > >with a samba 4.2.1 AD DC you automatically use the separate 'winbindd' deamon and the 'winbind' deamon built into the samba daemon should be ignored. There is no way that I know to 'disable' the winbind built into samba, but there is a way to turn it on and turn off 'winbindd', which is the way I suggested. Rowland
Miguel Medalha
2015-Apr-23 16:33 UTC
[Samba] RFC2307 attributes not being read by DC2 in 4.2.1
> with a samba 4.2.1 AD DC you automatically use the separate 'winbindd' > deamon and the 'winbind' deamon built into the samba daemon should be > ignored. There is no way that I know to 'disable' the winbind built into > samba, but there is a way to turn it on and turn off 'winbindd', which > is the way I suggested. >The Samba 4.2 release notes contains the following: If required the old internal winbind can be activated by setting 'server services = +winbind -winbindd'. Upgrading users with a server services parameter specified should ensure they change 'winbind' to 'winbindd' to obtain the new functionality. So what I was proposing was the equivalent (-winbind +winbindd) of the inversion of this parameter and see what happens. Since you are admitting this can be a bug in Samba, why not a bug in the turning the winbind types on and off? Maybe I am very wrong, but I only wanted to help with something that is very easy to test.