Il 16/02/19 18:15, Rowland Penny via samba ha scritto:> On Thu, 14 Feb 2019 09:30:00 +0100 > [...] > Hi Piviul, I have read that bug report and sorry but your smb.conf is > incorrect. > > try this one: > > [global] > workgroup = DOMINIOCSA > security = ADSfrom man smb.conf: SECURITY = ADS In this mode, Samba will act as a domain member in an ADS realm. but I have no ADS realm in my network: my domain is an old samba3 domain. Have a great day Piviul
On Mon, 18 Feb 2019 15:24:55 +0100 Piviul via samba <samba at lists.samba.org> wrote:> Il 16/02/19 18:15, Rowland Penny via samba ha scritto: > > On Thu, 14 Feb 2019 09:30:00 +0100 > > [...] > > Hi Piviul, I have read that bug report and sorry but your smb.conf > > is incorrect. > > > > try this one: > > > > [global] > > workgroup = DOMINIOCSA > > security = ADS > from man smb.conf: > > SECURITY = ADS > In this mode, Samba will act as a domain member in an ADS realm. > > but I have no ADS realm in my network: my domain is an old samba3 > domain. > > Have a great day > > Piviul >Then do things, stop trying to use winbind, use nslcd instead. Then start planning to update to a Samba AD domain, before it is too late. Rowland
Il 18/02/19 19:12, Rowland Penny ha scritto:> [...] > Then do things, stop trying to use winbind, use nslcd instead. > > Then start planning to update to a Samba AD domain, before it is too > late.Hi Rowland, I'm sorry but I'm not the one can decide to upgrade to samba4 the domain controller, and I'm not the one that administer the domain controller. I would like but I can't. Furthermore, in my opinion, until the developers of samba decide to support samba3 and winbind, bugs have to be reported and hopefully solved and the solution of these bugs is not to don't use them... in my opinion. Have a great day Piviul