Zen

Source string Source string

177/10000 · 177

The string is read only.

English Actions
Make sure you join the domain before starting Samba
After configuring the `/etc/samba/smb.conf` file, join the domain *before* starting Samba by typing the following command as `root`:
~]# net rpc join -U administrator%password
Note that the [option]`-S` option, which specifies the domain server host name, does not need to be stated in the [command]#net rpc join# command. Samba uses the host name specified by the `workgroup` directive in the `/etc/samba/smb.conf` file instead of it being stated explicitly.
====== Domain Controller indexterm:[Samba,server types,Domain Controller] A domain controller in Windows NT is functionally similar to a Network Information Service (NIS) server in a Linux environment. Domain controllers and NIS servers both host user and group information databases as well as related services. Domain controllers are mainly used for security, including the authentication of users accessing domain resources. The service that maintains the user and group database integrity is called the _Security Account Manager_ (SAM). The SAM database is stored differently between Windows and Linux Samba-based systems, therefore SAM replication cannot be achieved and platforms cannot be mixed in a PDC/BDC environment.
In a Samba environment, there can be only one PDC and zero or more BDCs.
A mixed Samba/Windows domain controller environment
Samba cannot exist in a mixed Samba/Windows domain controller environment (Samba cannot be a BDC of a Windows PDC or vice versa). Alternatively, Samba PDCs and BDCs *can* coexist.
Primary Domain Controller (PDC) Using `tdbsam`pass:attributes[{blank}]indexterm:[Samba,smb.conf,PDC using tdbsam]
The simplest and most common implementation of a Samba PDC uses the new default `tdbsam` password database back end. Replacing the aging `smbpasswd` back end, `tdbsam` has numerous improvements that are explained in more detail in xref:File_and_Print_Servers.adoc#sect-Samba-Account_Information-Databases[Samba Account Information Databases]. The `passdb backend` directive controls which back end is to be used for the PDC.
The following `/etc/samba/smb.conf` file shows a sample configuration needed to implement a `tdbsam` password database back end.
An Example Configuration of Primary Domain Controller (PDC) Using `tdbsam`
[global]
workgroup = DOCS
netbios name = DOCS_SRV
passdb backend = tdbsam
security = user
add user script = /usr/sbin/useradd -m "%u"
delete user script = /usr/sbin/userdel -r "%u"
add group script = /usr/sbin/groupadd "%g"
delete group script = /usr/sbin/groupdel "%g"
add user to group script = /usr/sbin/usermod -G "%g" "%u"
add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null -g machines "%u"
# The following specifies the default logon script
# Per user logon scripts can be specified in the user
# account using pdbedit logon script = logon.bat
# This sets the default profile path.
# Set per user paths with pdbedit
logon drive = H:
domain logons = yes
os level = 35
preferred master = yes
domain master = yes
[homes]
comment = Home Directories
valid users = %S
read only = no
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon/scripts
browseable = no
read only = no
# For profiles to work, create a user directory under the
# path shown.
# mkdir -p /var/lib/samba/profiles/john
[Profiles]
comment = Roaming Profile Share
path = /var/lib/samba/profiles
read only = no
browseable = no
guest ok = yes
profile acls = yes
# Other resource shares ... ...
To provide a functional PDC system which uses `tdbsam` follow these steps:
Adjust the `smb.conf` configuration file as shown in xref:File_and_Print_Servers.adoc#exam-Samba_Domain_Controller-PDC_Using_tdbsam[An Example Configuration of Primary Domain Controller (PDC) Using `tdbsam`].
Add the `root` user to the Samba password database. You will be prompted to provide a new Samba password for the `root` user:
~]# smbpasswd -a root
New SMB password:
Start the `smb` service:
~]# service smb start
Make sure all profile, user, and netlogon directories are created.
Add groups that users can be members of:
~]# groupadd -f users
~]# groupadd -f nobody
~]# groupadd -f ntadmins
Associate the UNIX groups with their respective Windows groups.
~]# net groupmap add ntgroup="Domain Users" unixgroup=users
~]# net groupmap add ntgroup="Domain Guests" unixgroup=nobody
~]# net groupmap add ntgroup="Domain Admins" unixgroup=ntadmins
Grant access rights to a user or a group. For example, to grant the right to add client machines to the domain on a Samba domain controller, to the members to the Domain Admins group, execute the following command:
~]# net rpc rights grant 'DOCS\Domain Admins' SetMachineAccountPrivilege -S PDC -U root
Keep in mind that Windows systems prefer to have a primary group which is mapped to a domain group such as Domain Users.
Windows groups and users use the same namespace thus not allowing the existence of a group and a user with the same name like in UNIX.

Loading…

User avatar None

Source string added

  1. fedora-docs-l10n/fedora-system-administrat
  2. f26/pages/_partials/servers/Samba
  3. English
[Profiles]
comment = Roaming Profile Share
path = /var/lib/samba/profiles
read only = no
browseable = no
guest ok = yes
profile acls = yes
# Other resource shares ... ...
4 years ago
Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Multiple failing checks

Following checks are failing:
Unchanged translation: Spanish, Indonesian

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: delimited block -
Flags
no-wrap, read-only
Source string location
./pages/_partials/servers/Samba.adoc:632
String age
4 years ago
Last updated
10 months ago
Source string age
4 years ago
Translation file
pot/f26/pages/_partials/servers/Samba.pot, string 168