hi,
Is it necessary the "ADS support compilation" for Samba 3.x.x if I just need to join Linux Server in a AD Domain as member server, without elect Samba server as a Domain Controller ?
I think you can just run netjoin from the command line to have your server be listed in AD.
If you are not using the samba server as a DC, what would be the benefit of joining it to AD? Tracking purposes?
I used samba integrated to AD to be able to pull user and group rights down into the samba server for authentication and file management of the file server via AD.
hi Gb0mb,
the scope to join a Samba server in a Windows Domain is
for authentication. The user has to exist in Unix users
(/etc/passwd) and then in samba user list (using command smbpasswd -a <username>). However you have to do this operation also if server is joined.
What you avoid to do (for the user) if the server is joined, is tha the user has not to change his samba password(using command) smbpasswd when he changes password at windows level, becouse Samba server checks the couple user/password on the "Windows Password Server",
typically the DC of Windows Domain.
In Samba 3 exist commands
"net join"
and
"net ads join"
What I need to know is the difference between these commands:
"net ads join" is used to join Samba server to AD domain (and "net join" to join to a NT4 domain)
OR
"net ads join" is used to promote the samba server as DC (and "net join" to join as member server in any Windows 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.