Thats not true. What dev23 is probably talking about is the security=domain option which allows your Samba server to authenticate users against an NT domain.
To actually log into an NT domain you need Winbind.
If you want to access resources on a NT/W2K machine you could use the smbclient, just use an account that exists in the Domain. (eg: [DOMAIN]\[user])
Winbind is for mapping NT Users to unix users and use them on a Linux machine
eg: using NT Domain Server as a Password Authentication Server, that includes Telnet, FTP access, SSH etc (you name it, if you configure PAM to also check with winbind)
You can always configure a Samba machine to 'take part' in the domain (e.g. Print/File Server), so Security=domain is partially correct.
It all depends on what you expect to do 'in' the domain, if it's just getting files from a Server you don't have to make the Samba machine a Member of the domain. if you want users to connect to that machine you should consider using security=domain, and add the samba server to the domain.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.