Table of Contents
Advertisement
Chapter 14. Samba
NT4-based domain member server. Becoming a member server of an NT4-based domain is
similar to connecting to an Active Directory. The main difference is NT4-based domains do not
use Kerberos in their authentication method, making the
the Samba member server serves as a pass through to the NT4-based domain server.
[global]
workgroup = DOCS
netbios name = DOCS_SRV
security = domain
[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No
[public]
comment = Data
path = /export
force user = docsbot
force group = users
guest ok = Yes
Having Samba as a domain member server can be useful in many situations. There are times
where the Samba server can have other uses besides file and printer sharing. It may be
beneficial to make Samba a domain member server in instances where Linux-only applications
are required for use in the domain environment. Administrators appreciate keeping track of all
machines in the domain, even if not Windows-based. In the event the Windows-based server
hardware is deprecated, it is quite easy to modify the
Samba-based PDC. If Windows NT-based servers are upgraded to Windows 2000/2003, the
file is easily modifiable to incorporate the infrastructure change to Active Directory if
smb.conf
needed.
Important
After configuring the
typing the following command as root:
root# net rpc join -U administrator%password
Note that the
option, which specifies the domain server hostname, does not need to be
-S
stated in the
net rpc join
directive in the
smb.conf
3.3. Domain Controller
256
file, join the domain before starting Samba by
smb.conf
command. Samba uses the hostname specified by the
file instead of it being stated explicitly.
file simpler. In this instance,
smb.conf
file to convert the server to a
smb.conf
workgroup
Advertisement
Table of Contents
