I can't seem to get an answer to this question... Should I use winbind if my Domain Controller is a samba machine? Or is it only useful if my DC is a real MS DC and I have other unix/linux client machines? I'm strictly wanting to provide file and domain logon services to Win2000 machines via a samba DC. There are no other DC's involved. After reading the 3.0 HowTo on winbind all I see are references to winbind helping linux/unix resolve usernames from a Windows DC. If I'm using a linux/samba box as the DC I don't need this for my win2000 users, in a domain on the Samba DC, to gain access to shares, right? Would winbind help me in any other way in trying to use ACL's? Regards Doug P
On Fri, 24 Oct 2003, Douglas Phillipson wrote:> I can't seem to get an answer to this question... > > Should I use winbind if my Domain Controller is a samba machine? Or is > it only useful if my DC is a real MS DC and I have other unix/linux > client machines?Winbind works with both Windows and Samba. If you want a distributed Samba environemnt you want samba and winbind. Is that definitive enough yet?> I'm strictly wanting to provide file and domain logon services to > Win2000 machines via a samba DC. There are no other DC's involved. > After reading the 3.0 HowTo on winbind all I see are references to > winbind helping linux/unix resolve usernames from a Windows DC. If I'm > using a linux/samba box as the DC I don't need this for my win2000 > users, in a domain on the Samba DC, to gain access to shares, right? > Would winbind help me in any other way in trying to use ACL's?Yes. - John T. -- John H Terpstra Email: jht@samba.org
On Friday 24 October 2003 3:28 pm, Douglas Phillipson wrote:> I can't seem to get an answer to this question... > > Should I use winbind if my Domain Controller is a samba machine? Or > is it only useful if my DC is a real MS DC and I have other > unix/linux client machines?It's still useful. If you have other unix machines, they can authenticate via samba/windows domain mechanism, without having a local machine (unix) account. Other samba file or print servers can use it to authenticate domain users. In either case, it can't hurt.