Setting up Samba as an Active Directory Domain Controller: Difference between revisions
Mmuehlfeld (talk | contribs) (Added --use-rfc2307 and short explanation to the provisioning command) |
m (/* Added how to create he reverse zone) |
||
(192 intermediate revisions by 19 users not shown) | |||
Line 1: | Line 1: | ||
= Introduction = |
|||
= HOWTO to set up Samba as an Active Directory compatible Domain Controller = |
|||
Starting from version 4.0, Samba is able to run as an Active Directory (AD) domain controller (DC). If you are installing Samba in a production environment, it is recommended to run two or more DCs for failover reasons. |
|||
This document explains how to setup a simple Samba |
|||
server as a Domain Controller compatible with Microsoft's Active Directory, for use particularly by Microsoft Windows clients that are joined to the Active Directory Domain, for services such as Domain Logon. We refer to this capability as being an AD DC for short. |
|||
This documentation describes how to set up Samba as the first DC to build a new AD forest. Additionally, use this documentation if you are migrating a Samba NT4 domain to Samba AD. To join Samba as an additional DC to an existing AD forest, see [[Joining_a_Samba_DC_to_an_Existing_Active_Directory|Joining a Samba DC to an Existing Active Directory]]. |
|||
== Video Demonstrations of This HOWTO == |
|||
Samba as an AD DC only supports: |
|||
A set of [[samba4/videos|demonstration videos]] is available that |
|||
* the integrated LDAP server as AD back end. For details, see the frequently asked question (FAQ) [[FAQ#Does_Samba_AD_DCs_Support_OpenLDAP_or_Other_LDAP_Servers_as_Back_End.3F|Does Samba AD DCs Support OpenLDAP or Other LDAP Servers as Back End?]] |
|||
may provide a useful overview of the contents of this HOWTO. |
|||
* the [https://web.mit.edu/kerberos/ MIT] and [http://www.h5l.se/ Heimdal] Kerberos Key Distribution Center (KDC). |
|||
: Samba uses the MIT KDC provided by your operating system if you run Samba 4.7 or later and has been built using the <code>--with-system-mitkrb5</code> option. In other cases Samba uses the Heimdal KDC included in Samba. For further details about Samba using the MIT KDC, see [[Running a Samba AD DC with MIT Kerberos KDC]]. |
|||
== A Note on Versions == |
|||
Samba is developing rapidly. This HOWTO is frequently updated to reflect the latest changes in the Samba git repository. Please see the [[Release_Planning_for_Samba_4.0|Samba 4.0 Release Planning]] for more specifics on the release planning. |
|||
Please review the [[Samba4#Previous_Releases|Release Notes]] for the version you have installed, it may contain important information not yet reflected in this HOWTO. |
|||
== Installing Samba == |
|||
= Preparing the Installation = |
|||
You will either need to install samba from a your distributions package manager or [[Build_Samba| Build Samba]]. At this time the packages are generally older and very hard to support due to the rapid development of the samba project, so it is recommended to build from source. |
|||
* Select a host name for your AD DC. |
|||
=== Upgrading === |
|||
: Do not use NT4-only terms as host name, such as <code>PDC</code> or <code>BDC</code>. These modes do not exist in an AD and cause confusion. |
|||
* Select a DNS domain for your AD forest. The name will also be used as the AD Kerberos realm. |
|||
If you are upgrading from a previous release of Samba 4.x, be sure to review all the [[Samba4#Previous_Releases|Release Notes]] for the new version, as well as the notes for all the interim versions. |
|||
: {{Imbox |
|||
| type = important |
|||
| text = Make sure that you provision the AD using a DNS domain that will not need to be changed. Samba does not support renaming the AD DNS zone and Kerberos realm. |
|||
}} |
|||
: For additional information, see [[Active_Directory_Naming_FAQ|Active Directory Naming FAQ]]. |
|||
* Use a static IP address on the DC. |
|||
If you are upgrading from source please refer to the [[Build_Samba#Upgrading_a_source_version|upgrading a source version]] otherwise please consult your distributions upgrade procedure. |
|||
* Disable tools, such as <code>resolvconf</code>, that automatically update your <code>/etc/resolv.conf</code> DNS resolver configuration file. AD DCs and domain members must use an DNS server that is able to resolve the AD DNS zones. |
|||
== Server Information == |
|||
For the rest of this tutorial, we will be using the following configuration for our example AD DC configuration. |
|||
* Verify that no Samba processes are running: |
|||
Installation Directory: /usr/local/samba |
|||
# ps ax | egrep "samba|smbd|nmbd|winbindd" |
|||
Server Hostname: samba (Your linux hostname will be used here) |
|||
: If the output lists any <code>samba</code>, <code>smbd</code>, <code>nmbd</code>, or <code>winbindd</code> processes, shut down the processes. |
|||
DNS Domain Name: samdom.example.com (This will also be your '''realm''') |
|||
NT4 Domain Name: samdom |
|||
IP Address: 192.168.1.2 |
|||
Server Role: DC |
|||
* Verify that the <code>/etc/hosts</code> file on the DC correctly resolves the fully-qualified domain name (FQDN) and short host name to the LAN IP address of the DC. For example: |
|||
== Step 1: Provision Samba == |
|||
127.0.0.1 localhost localhost.localdomain |
|||
10.99.0.1 DC1.samdom.example.com DC1 |
|||
:The host name and FQDN must not resolve to the <code>127.0.0.1</code> IP address or any other IP address than the one used on the LAN interface of the DC. |
|||
* If you previously ran a Samba installation on this host: |
|||
The provision step sets up a basic user database, and is used when you are setting up your Samba |
|||
:* Remove the existing <code>smb.conf</code> file. To list the path to the file: |
|||
server in its own domain. If you instead want to setup your Samba server as an additional domain controller |
|||
in an existing domain, then please see the [[#Joining a Windows Domain Controller as an Additional DC in a Domain|Joining a Windows Domain Controller as an Additional DC in a Domain]] section on this page. If you want to migrate an existing Samba 3.x domain to Samba 4.0 as an AD DC, see the [[#Migrating_an_Existing_Samba_Domain_to_Samba|Migrating an Existing Samba 3 Domain to Samba 4]] section on this page. |
|||
# smbd -b | grep "CONFIGFILE" |
|||
The provision step must be run as a user with permission to write to the install directory. |
|||
CONFIGFILE: /usr/local/samba/etc/samba/smb.conf |
|||
:* Remove all Samba database files, such as <code>*.tdb</code> and <code>*.ldb</code> files. To list the folders containing Samba databases: |
|||
# /usr/local/samba/bin/samba-tool domain provision --use-rfc2307 |
|||
# smbd -b | egrep "LOCKDIR|STATEDIR|CACHEDIR|PRIVATE_DIR" |
|||
This will run the provision tool interactively. For realm use something like <tt>samdom.example.com</tt>, for domain (it should suggest this) use <tt>samdom</tt>. |
|||
LOCKDIR: /usr/local/samba/var/lock/ |
|||
STATEDIR: /usr/local/samba/var/locks/ |
|||
CACHEDIR: /usr/local/samba/var/cache/ |
|||
PRIVATE_DIR: /usr/local/samba/private/ |
|||
: Starting with a clean environment helps to prevent confusion and ensures that no files from any previous Samba installation will be mixed with your new domain DC installation. |
|||
The <tt>--use-rfc2307</tt> allows you to store posix attributes in your Active Directory, too. It e. g. enables user accounts having automatically the objectClass posixAccount added and you can administrate the unix extensions in ADUC. |
|||
* Remove an existing <code>/etc/krb5.conf</code> file: |
|||
If you run the previous command with a user who does not have write permission to the install directory, you will get an error similar to this: |
|||
tdb_open_ex: could not open file /usr/local/samba/private/sam.ldb.d/DC=SAMDOM,DC=EXAMPLE,DC=COM. ldb: Permission denied |
|||
# rm /etc/krb5.conf |
|||
You can pass options to <tt>samba-tool domain provision</tt> command. You can run it with the <tt>--help</tt> option to see a list of them. |
|||
* Note: As of Samba 4.0.0 RC1 the provision command now uses Samba's internal DNS server by default, if you would like to use [[Dns-backend_bind|Bind as DNS backend]], add <tt>--dns-backend=BIND9_DLZ</tt> to the above provision command. |
|||
* Note: You may need to remove the <tt>/usr/local/samba/etc/smb.conf</tt> file if you are re-running the provision command. |
|||
* Note: If you use the --adminpass='password' switch, be aware that there are password complexity requirements, so if you are getting some odd error with provision, try a more complex password ie. 'Pa$$w0rd' |
|||
* Note: If you have a "password complexity" failure during domain provisioning - read the following! The password complexity requirement is at least one uppercase letter, and one number, and at least eight characters long. If you don't use a complex enough password, the provision script will error, and you will need to delete the /usr/local/samba/private and /usr/local/samba/etc directories, then run samba-tool domain provision again - with a better password. |
|||
== Step 2: Starting your Samba AD DC == |
|||
If you are planning to run Samba as a production server, then just run the <tt>samba</tt> binary as root |
|||
# /usr/local/samba/sbin/samba |
|||
= Installing Samba = |
|||
That will run Samba in 'standard' mode, which is suitable for |
|||
production use. Samba doesn't yet have init scripts included |
|||
for each platform, but making one for your platform should not be |
|||
difficult. There are some example scripts (for RedHat/Fedora, Debian and Ubuntu) on the [[Samba4/InitScript]] page. |
|||
For details, see [[Installing_Samba|Installing Samba]]. |
|||
If you are running Samba as a developer you may find |
|||
the following more useful: |
|||
{{Imbox |
|||
# /usr/local/samba/sbin/samba -i -M single |
|||
| type = note |
|||
| text = Only install a maintained Samba version. For details, see [[Samba_Release_Planning|Samba Release Planning]]. |
|||
}} |
|||
This will start <tt>samba</tt> with all log messages printed to stdout, and restricting it to a |
|||
single process. That mode of operation makes debugging <tt>samba</tt> with <tt>gdb</tt> |
|||
easier. |
|||
If you want to launch it under <tt>gdb</tt>, run <tt>samba</tt> as follows: |
|||
# gdb --args /usr/local/samba/sbin/samba -i -M single |
|||
Note that if you are running any Samba 3 <tt>smbd</tt> or <tt>nmbd</tt> processes |
|||
they need to be stopped before starting <tt>samba</tt> from Samba 4. |
|||
= Provisioning a Samba Active Directory = |
|||
Take care when running Samba commands if you also have a previous version of Samba installed. To avoid inadvertently running the wrong version, you should consider putting the <tt>/usr/local/samba/bin</tt> and <tt>/usr/local/samba/sbin</tt> directories in the beginning of your <tt>PATH</tt> variable. |
|||
The Samba AD provisioning process creates the AD databases and adds initial records, such as the domain administrator account and required DNS entries. |
|||
You can see what version of Samba, if any, is in your <tt>PATH</tt> variable by running the following: |
|||
# samba -V |
|||
If you are migrating a Samba NT4 domain to AD, skip this step and run the Samba classic upgrade. For details, see [[Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade)|Migrating a Samba NT4 Domain to Samba AD (Classic Upgrade)]]. |
|||
== Step 3: Testing connectivity to your Samba AD DC == |
|||
{{Imbox |
|||
First check you have the right version of <tt>smbclient</tt> by running the following command: |
|||
| type = note |
|||
| text = The AD provisioning requires root permissions to create files and set permissions. |
|||
}} |
|||
$ /usr/local/samba/bin/smbclient --version |
|||
The <code>samba-tool domain provision</code> command provides several parameters to use with the interactive and non-interactive setup. For details, see: |
|||
This should show you a version starting with "Version 4.0.XXXXX". |
|||
# samba-tool domain provision --help |
|||
Now run this command to list the shares on your Samba server: |
|||
$ /usr/local/samba/bin/smbclient -L localhost -U% |
|||
{{Imbox |
|||
The output of the command should be similar to what is shown below: |
|||
| type = note |
|||
| text = When provisioning a new AD, it is recommended to enable the NIS extensions by passing the <code>--use-rfc2307</code> parameter to the <code>samba-tool domain provision</code> command. This enables you to store Unix attributes in AD, such as user IDs (UID), home directories paths, group IDs (GID). Enabling the NIS extensions has no disadvantages. However, enabling them in an existing domain requires manually extending the AD schema. For further details about Unix attributes in AD, see: |
|||
* [[Setting_up_RFC2307_in_AD|Setting up RFC2307 in AD]] |
|||
* [[Idmap_config_ad|idmap config = ad]] |
|||
}} |
|||
Sharename Type Comment |
|||
--------- ---- ------- |
|||
netlogon Disk |
|||
sysvol Disk |
|||
IPC$ IPC IPC Service (Samba 4.0.0) |
|||
The <tt>netlogon</tt> and <tt>sysvol</tt> shares are basic shares needed for Active Directory server |
|||
operation. |
|||
== Parameter Explanation == |
|||
If the command failed, restart samba by running the following: |
|||
Set the following parameters during the provisioning: |
|||
# killall samba |
|||
# /usr/local/samba/sbin/samba |
|||
{| class="wikitable" |
|||
To test that authentication is working, you should try to connect to the <tt>netlogon</tt> share |
|||
!Interactive Mode Setting |
|||
using the Administrator password you set earlier: |
|||
!Non-interactive Mode Parameter |
|||
!Explanation |
|||
|- |
|||
|<code>--use-rfc2307</code> |
|||
|<code>--use-rfc2307</code> |
|||
|Enables the NIS extensions. |
|||
|- |
|||
|<code>Realm</code> |
|||
|<code>--realm</code> |
|||
|Kerberos realm. This is also used as the AD DNS domain. For example: <code>samdom.example.com</code>. |
|||
|- |
|||
|<code>Domain</code> |
|||
|<code>--domain</code> |
|||
|NetBIOS domain name. It is recommended to use the first part of the AD DNS domain. For example: <code>samdom</code>. |
|||
|- |
|||
|<code>Server Role</code> |
|||
|<code>--server-role</code> |
|||
|Installs the domain controller <code>DC</code> role. |
|||
|- |
|||
|<code>DNS backend</code> |
|||
|<code>--dns-backend</code> |
|||
|Sets the DNS back end. The first DC in an AD must be installed using a DNS back end. Note that the <code>BIND9_FLATFILE</code> is not supported and will be removed in a future Samba version. |
|||
|- |
|||
|<code>DNS forwarder IP address</code> |
|||
|not available |
|||
|This setting is only available when using the <code>SAMBA_INTERNAL</code> DNS back end. For details, see [[Samba_Internal_DNS_Back_End#Setting_up_a_DNS_Forwarder|Setting up a DNS Forwarder]]. |
|||
|- |
|||
|<code>Administrator password</code> |
|||
|<code>--adminpass</code> |
|||
|Sets the domain administrator password. If the password does not match the complexity requirements, the provisioning fails. For details, see [https://technet.microsoft.com/en-us/library/cc786468%28v=ws.10%29.aspx Microsoft TechNet: Passwords must meet complexity requirements]. |
|||
|} |
|||
Other parameters frequently used with the <code>samba-tool domain provision</code> command: |
|||
$ smbclient //localhost/netlogon -UAdministrator%'p4$$word' -c 'ls' |
|||
* <code>--option="interfaces=lo eth0" --option="bind interfaces only=yes"</code>: If your server has multiple network interfaces, use these options to bind Samba to the specified interfaces. This enables the <code>samba-tool</code> command to register the correct LAN IP address in the directory during the join. |
|||
The output of the command should be similar to what is shown below: |
|||
{{Imbox |
|||
Domain=[SAMDOM] OS=[Unix] Server=[Samba 4.0.0] |
|||
| type = note |
|||
. D 0 Wed Sep 12 21:00:36 2012 |
|||
| text = do NOT use <code>NONE</code> as the DNS backend, it is not supported and will be removed in a future Samba version. |
|||
.. D 0 Wed Sep 12 21:02:28 2012 |
|||
}} |
|||
{{Imbox |
|||
== Step 4: Configure DNS == |
|||
| type = note |
|||
| text = If using Bind as the DNS backend, do NOT use <code>BIND9_FLATFILE</code>, it is not supported and will be removed in a future Samba version. |
|||
}} |
|||
{{Imbox |
|||
A working DNS setup is essential to the correct operation of |
|||
| type = important |
|||
Samba. Without the right DNS entries, Kerberos won't work, which in |
|||
| text = Once you have provisioned the first DC in an AD domain, do not provision any further DCs in the same domain, [[Joining_a_Samba_DC_to_an_Existing_Active_Directory|Join]] any further DCs. |
|||
turn means that many of the basic features of Samba won't work. |
|||
}} |
|||
It is worth spending some extra time to ensure your DNS setup is correct, as debugging problems caused by mis-configured DNS can take a |
|||
lot of time later on. |
|||
For additional information on the DNS backends and a decission aid, which backend fits best to your needs, see the [[DNS|DNS]] page. |
|||
== Provisioning Samba AD in Interactive Mode == |
|||
To provision a Samba AD interactively, run: |
|||
If you specified <tt>--dns-backend=SAMBA_INTERNAL</TT> or did not specify any backend at all when you provisioned, there is no further setup required for the DNS server. |
|||
After you have dns configured, you still need to configure your <tt>/etc/resolv.conf</tt> as shown in [[#Configure /etc/resolv.conf|Configure /etc/resolv.conf]] |
|||
# samba-tool domain provision --use-rfc2307 --interactive |
|||
If you want the internal DNS server to forward requests it isn't responsible for, then add the following to your smb.conf: |
|||
Realm [SAMDOM.EXAMPLE.COM]: SAMDOM.EXAMPLE.COM |
|||
dns forwarder = {IP-Address of the DNS you want to forward to} |
|||
Domain [SAMDOM]: SAMDOM |
|||
Server Role (dc, member, standalone) [dc]: dc |
|||
DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE) [SAMBA_INTERNAL]: SAMBA_INTERNAL |
|||
DNS forwarder IP address (write 'none' to disable forwarding) [10.99.0.1]: 8.8.8.8 |
|||
Administrator password: Passw0rd |
|||
Retype password: Passw0rd |
|||
Looking up IPv4 addresses |
|||
Looking up IPv6 addresses |
|||
No IPv6 address will be assigned |
|||
Setting up share.ldb |
|||
Setting up secrets.ldb |
|||
Setting up the registry |
|||
Setting up the privileges database |
|||
Setting up idmap db |
|||
Setting up SAM db |
|||
Setting up sam.ldb partitions and settings |
|||
Setting up sam.ldb rootDSE |
|||
Pre-loading the Samba 4 and AD schema |
|||
Adding DomainDN: DC=samdom,DC=example,DC=com |
|||
Adding configuration container |
|||
Setting up sam.ldb schema |
|||
Setting up sam.ldb configuration data |
|||
Setting up display specifiers |
|||
Modifying display specifiers |
|||
Adding users container |
|||
Modifying users container |
|||
Adding computers container |
|||
Modifying computers container |
|||
Setting up sam.ldb data |
|||
Setting up well known security principals |
|||
Setting up sam.ldb users and groups |
|||
Setting up self join |
|||
Adding DNS accounts |
|||
Creating CN=MicrosoftDNS,CN=System,DC=samdom,DC=example,DC=com |
|||
Creating DomainDnsZones and ForestDnsZones partitions |
|||
Populating DomainDnsZones and ForestDnsZones partitions |
|||
Setting up sam.ldb rootDSE marking as synchronized |
|||
Fixing provision GUIDs |
|||
A Kerberos configuration suitable for Samba 4 has been generated at /usr/local/samba/private/krb5.conf |
|||
Setting up fake yp server settings |
|||
Once the above files are installed, your Samba4 server will be ready to use |
|||
Server Role: active directory domain controller |
|||
Hostname: DC1 |
|||
NetBIOS Domain: SAMDOM |
|||
DNS Domain: samdom.example.com |
|||
DOMAIN SID: S-1-5-21-2614513918-2685075268-614796884 |
|||
{{Imbox |
|||
'''Warning:''' If you are running X windows on your machine, networkmanager could be spawning dnsmasq or if you are using another DNS server, check the logs for lines like: |
|||
| type = note |
|||
| text = The interactive provisioning mode supports passing further parameters to the <code>samba-tool domain provision</code> command. This enables you to modify parameters that are not part of the interactive setup. |
|||
}} |
|||
Failed to bind to 0.0.0.0:53 TCP - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED |
|||
If you need to disable this you can open <tt>/etc/NetworkManager/NetworkManager.conf</tt> in your favorite editor as root, and comment out the line <tt>dns=dnsmasq</tt>, then <tt>restart network-manager</tt> |
|||
== Provisioning Samba AD in Non-interactive Mode == |
|||
* More information about troubleshooting can be found on the [[Samba_troubleshooting_temp|Samba Troubleshooting]] page. |
|||
For example, to provision a Samba AD non-interactively with the following settings: |
|||
==== Bind as DNS backend ==== |
|||
* Server role: <code>dc</code> |
|||
* NIS extensions enabled |
|||
* Internal DNS back end |
|||
* Kerberos realm and AD DNS zone: <code>samdom.example.com</code> |
|||
* NetBIOS domain name: <code>SAMDOM</code> |
|||
* Domain administrator password: <code>Passw0rd</code> |
|||
# samba-tool domain provision --server-role=dc --use-rfc2307 --dns-backend=SAMBA_INTERNAL --realm=SAMDOM.EXAMPLE.COM --domain=SAMDOM --adminpass=Passw0rd |
|||
If you used any other --dns-backend= option in your provision line see the detailed [[Dns-backend_bind|Bind as DNS backend]] HowTo for additional setup instructions. There you will find many information how to setup and configure Bind in general and to work with Samba 4. |
|||
If the internal DNS currently maybe doesn't provide all features you require, you should also think about Bind as DNS backend. Is a good choice, if you e. g. already have or plan to have a complex DNS, beside the zones that should be administrated through samba. |
|||
=== Configure /etc/resolv.conf === |
|||
For all the local DNS lookups to resolve correctly, we need to modify the server's <tt>/etc/resolv.conf</tt> file. The following example should be sufficient to have DNS resolve properly: |
|||
domain samdom.example.com |
|||
nameserver 192.168.1.2 |
|||
= Setting up the AD DNS back end = |
|||
*Note: Remember to change the IP Address to your Samba server's IP Address |
|||
*Note: If your server is set up to receive its IP configuration via DHCP, the <tt>/etc/resolv.conf</tt> file might be automatically updated. Refer to your distribution's documentation on how to stop this behavior. |
|||
Skip this step if you provisioned the DC using the <code>SAMBA_INTERNAL</code> DNS back end. |
|||
=== Testing DNS === |
|||
* Set up the BIND DNS server and the <code>BIND9_DLZ</code> module. For details, see [[Setting_up_a_BIND_DNS_Server|Setting up a BIND DNS Server]]. |
|||
To test that DNS is working properly, run the following commands and compare the output to what is shown: |
|||
* Start the BIND DNS server. For example: |
|||
# systemctl start named |
|||
: For details how to start services, see you distribution's documentation. |
|||
= Configuring the DNS Resolver = |
|||
Domain members in an AD use DNS to locate services, such as LDAP and Kerberos. For that, they need to use a DNS server that is able to resolve the AD DNS zone. |
|||
On your DC, set the AD DNS domain in the <code>domain</code> and the IP of your DC in the <code>nameserver</code> parameter of the <code>/etc/resolv.conf</code> file. For example: |
|||
search samdom.example.com |
|||
nameserver 10.99.0.1 |
|||
= Create a reverse zone = |
|||
You can optionally add a reverse lookup zone. |
|||
# samba-tool dns zonecreate <Your-AD-DNS-Server-IP-or-hostname> 0.99.10.in-addr.arpa |
|||
Password for [administrator@SAMDOM.EXAMPLE.COM]: |
|||
Zone 0.99.10.in-addr.arpa created successfully |
|||
If you need more than one reverse zone (multiple subnets), just run the above command again but with the data for the other subnet. |
|||
The reverse zone is directly live without restarting Samba or BIND. |
|||
= Configuring Kerberos = |
|||
In an AD, Kerberos is used to authenticate users, machines, and services. |
|||
During the provisioning, Samba created a Kerberos configuration file for your DC. Copy this file to your operating system's Kerberos configuration. For example: |
|||
# cp /usr/local/samba/private/krb5.conf /etc/krb5.conf |
|||
{{Imbox |
|||
| type = important |
|||
| text = Do not create a symbolic link to the the generated <code>krb5.conf</code> file. In Samba 4.7 and later, the <code>/usr/local/samba/private/</code> directory is no longer accessible by other users than the <code>root</code> user. If the file is a symbolic link, other users are not able to read the file and, for example, dynamic DNS updates fail if you use the <code>BIND_DLZ</code> DNS back end. |
|||
}} |
|||
The pre-created Kerberos configuration uses DNS service (SRV) resource records to locate the KDC. |
|||
= Testing your Samba AD DC = |
|||
To start the <code>samba</code> service manually, enter: |
|||
# samba |
|||
Samba does not provide System V init scripts, <code>systemd</code>, <code>upstart</code>, or other services configuration files. |
|||
* If you installed Samba using packages, use the script or service configuration file included in the package to start Samba. |
|||
* If you built Samba, see [[Managing_the_Samba_AD_DC_Service|Managing the Samba AD DC Service]]. |
|||
== Verifying the File Server == |
|||
To list all shares provided by the DC: |
|||
$ smbclient -L localhost -U% |
|||
Domain=[SAMDOM] OS=[Unix] Server=[Samba x.y.z] |
|||
Sharename Type Comment |
|||
--------- ---- ------- |
|||
netlogon Disk |
|||
sysvol Disk |
|||
IPC$ IPC IPC Service (Samba x.y.z) |
|||
Domain=[SAMDOM] OS=[Unix] Server=[Samba x.y.z] |
|||
Server Comment |
|||
--------- ------- |
|||
Workgroup Master |
|||
--------- ------- |
|||
{{Imbox |
|||
| type = note |
|||
| text = The <code>netlogon</code> and <code>sysvol</code> shares were auto-created during the provisioning and must exist on a DC. |
|||
}} |
|||
To verify authentication, connect to the <code>netlogon</code> share using the domain administrator account: |
|||
$ smbclient //localhost/netlogon -UAdministrator -c 'ls' |
|||
Enter Administrator's password: |
|||
Domain=[SAMDOM] OS=[Unix] Server=[Samba x.y.z] |
|||
. D 0 Tue Nov 1 08:40:00 2016 |
|||
.. D 0 Tue Nov 1 08:40:00 2016 |
|||
49386 blocks of size 524288. 42093 blocks available |
|||
If one or more tests fail, see [[#Troubleshooting|Troubleshooting]]. |
|||
== Verifying DNS == |
|||
To verify that your AD DNS configuration works correctly, query some DNS records: |
|||
* The tcp-based <code>_ldap</code> SRV record in the domain: |
|||
$ host -t SRV _ldap._tcp.samdom.example.com. |
$ host -t SRV _ldap._tcp.samdom.example.com. |
||
_ldap._tcp.samdom.example.com has SRV record 0 100 389 |
_ldap._tcp.samdom.example.com has SRV record 0 100 389 dc1.samdom.example.com. |
||
* The udp-based <code>_kerberos</code> SRV resource record in the domain: |
|||
$ host -t SRV _kerberos._udp.samdom.example.com. |
$ host -t SRV _kerberos._udp.samdom.example.com. |
||
_kerberos._udp.samdom.example.com has SRV record 0 100 88 |
_kerberos._udp.samdom.example.com has SRV record 0 100 88 dc1.samdom.example.com. |
||
* The A record of the domain controller: |
|||
$ host -t A samba.samdom.example.com. |
|||
samba.samdom.example.com has address 10.0.0.1 |
|||
$ host -t A dc1.samdom.example.com. |
|||
The answers you get should be similar to the ones above (adjusted for your DNS domain name and hostname). If you get any errors, |
|||
dc1.samdom.example.com has address 10.99.0.1 |
|||
carefully check your system logs to locate the problem. |
|||
If one or more tests fail, see [[#Troubleshooting|Troubleshooting]]. |
|||
== Step 5: Configure Kerberos == |
|||
Kerberos configuration is handled by the <tt>krb5.conf</tt> file. This file is typically located in the <tt>/etc</tt> directory, please refer to your distribution documentation for the location of this file on your system. There is a sample file located at <tt>/usr/local/samba/share/setup/krb5.conf</tt> that is a suitable replacement for an existing file. This file is generated by provision and will look similar to the following: |
|||
[libdefaults] |
|||
default_realm = SAMDOM.EXAMPLE.COM |
|||
dns_lookup_realm = false |
|||
dns_lookup_kdc = true |
|||
== Verifying Kerberos == |
|||
*Note: If you have forgotten your realm, running <tt>samba-tool testparm --suppress-prompt | grep realm</tt> will let you know what you used. |
|||
* Request a Kerberos ticket for the domain administrator account: |
|||
=== Testing Kerberos === |
|||
$ kinit administrator |
|||
The simplest test is to use the <tt>kinit</tt> command as follows: |
|||
Password for administrator@SAMDOM.EXAMPLE.COM: |
|||
: {{Imbox |
|||
$ kinit administrator@SAMDOM.EXAMPLE.COM |
|||
| type = note |
|||
Password: |
|||
| text = The Kerberos realm is automatically appended, if you do not pass the principal in the <code>user@REALM</code> format to the <code>kinit</code> command.<br />Set Kerberos realms always in uppercase. |
|||
}} |
|||
* List the cached Kerberos tickets: |
|||
*Note: You must specify your domain realm <tt>SAMDOM.EXAMPLE.COM</tt> in '''uppercase letters''' |
|||
*Note: Depending on your distribution <tt>kinit</tt> may just return you to a prompt, however, some distributions may return something like '''Warning: Your password will expire in 41 days on Thu Mar 28 04:38:35 2013.''' |
|||
To verify that Kerberos is working, and that you received a ticket, run the following: |
|||
$ klist |
$ klist |
||
Ticket cache: FILE:/tmp/ |
Ticket cache: FILE:/tmp/krb5cc_0 |
||
Default principal: administrator@SAMDOM.EXAMPLE.COM |
Default principal: administrator@SAMDOM.EXAMPLE.COM |
||
Valid starting Expires Service principal |
Valid starting Expires Service principal |
||
01.11.2016 08:45:00 12.11.2016 18:45:00 krbtgt/SAMDOM.EXAMPLE.COM@SAMDOM.EXAMPLE.COM |
|||
renew until 02.11.2016 08:44:59 |
|||
If one or more tests fail, see [[#Troubleshooting|Troubleshooting]]. |
|||
= Configuring Time Synchronisation = |
|||
Kerberos requires a synchronised time on all domain members. For further details and how to set up the <code>ntpd</code> service, see [[Time_Synchronisation|Time Synchronisation]]. |
|||
If either <tt>kinit</tt> or <tt>klist</tt> do not exist on your system, refer to [[Samba_4_OS_Requirements]] on how to install the necessary packages. |
|||
You can also test Kerberos form a remote client, but you must first configure the client's <tt>krb5.conf</tt> and <tt>resolve.conf</tt> as shown previously. |
|||
= Using the Domain Controller as a File Server = |
|||
*Note: If you are using a client behind NAT then you have to add the following to the <tt>krb5.conf</tt> on the domain controller server: |
|||
Whilst the Samba AD DC is able to provide file shares, just like all other installation modes, the Samba team does not recommend using a DC as a file server for the following reasons: |
|||
[kdc] |
|||
check-ticket-addresses = false |
|||
* For anything but the smallest organisations, having more than one DC is a really good backup measure, and makes upgrades safer |
|||
*Note: If provision generated you a password and you forgot it or didn't get it saved in some way, you can use "samba-tool user setpassword administrator" as root to reset it. |
|||
* It encourages upgrades of the DC to also be upgrades of the host OS every year or two, because there isn't complex data to transition or other services involved. |
|||
* This means upgrades can be done by installing fresh, and replicating in the changes, which is better tested in Samba, gains new features and avoids a number of lingering data corruption risks. |
|||
* The DC and file-server have different points at which an organisation would wish to upgrade. The needs for new features on the DC and file server come at different times. Currently the AD DC is evolving rapidly to gain features, whereas the fileserver, after over 20 years, is quite rightly more conservative. |
|||
* mandatory smb signing is enforced on the DC. |
|||
== Configure NTP (Optional, but recommended) == |
|||
Active Directory requires an accurate time syncronisation. That's why it's highly recommended to run NTP or an other way to sycronize the time. The [[Configure_NTP|Configure NTP]] page shows the full NTP configuration process including SELinux policies. |
|||
If you do decide to use the Samba DC as a fileserver, please consider running a VM, on the DC, containing a separate Samba Unix domain member and use this instead. |
|||
== Setup and configure a file share (Optional) == |
|||
If you must use the Samba DC as a fileserver, you should be aware that the auto-enabled <code>acl_xattr</code> virtual file system (VFS) object enables you to only configure shares with Windows access control lists (ACL). Running shares with POSIX ACLs on a Samba DC is not supported and will not work. |
|||
See the [[Setup_and_configure_file_shares|Setup and configure file shares]] HowTo. |
|||
== Samba as a Print Server == |
|||
To provide network shares with the full capabilities of Samba, set up a Samba domain member with file shares. For details, see: |
|||
For a detailed description on that topic, see the [[Samba_as_a_print_server|Setup Samba as a Print Server]] HowTo. |
|||
* [[Setting_up_Samba_as_a_Domain_Member|Setting up Samba as a Domain Member]] |
|||
* [[Samba_File_Serving|Samba File Serving]] |
|||
= Configure a Windows Client to join our Samba Active Directory = |
|||
If you only have a small domain (small office, home network) and do not want to follow the Samba team's recommendation and use the DC additionally as a file server, configure Winbindd before you start setting up shares. For details, see [[Configuring_Winbindd_on_a_Samba_AD_DC|Configuring Winbindd on a Samba AD DC]]. |
|||
[[Configuring_a_windows_client_for_AD|Configuring a windows client to join our domain]] is useful when you need to start connecting windows clients. |
|||
= Samba AD management = |
|||
You can manage your Samba AD just like a windows AD using the windows tools by using the following link [[Samba_AD_management_from_windows|Samba AD Management from windows]] |
|||
You may also want to use the linux command line, so you can [[Adding_users_with_samba_tool|add users with samba-tool]] as well. |
|||
= Joining a Windows Domain Controller as an Additional DC in a Domain = |
|||
= Troubleshooting = |
|||
Once you have a Samba domain controller set up, you can choose to join |
|||
additional domain controllers to the domain, whether they be |
|||
additional Samba domain controllers, or additional Windows domain |
|||
controllers. |
|||
For further details, see [[Samba_AD_DC_Troubleshooting|Samba AD DC Troubleshooting]]. |
|||
If you wish to join an additional Samba domain controller to a domain, |
|||
then please see the [[Samba4/HOWTO/Join a domain as a DC|Joining a domain as a DC]] page. The instructions |
|||
on that page are the same for joining Samba to a Windows domain as |
|||
they are for joining Samba to an existing Samba domain. |
|||
If you wish to join a new Windows domain controller to a Samba domain, |
|||
then you should use the 'dcpromo' tool on the Windows machine. Please |
|||
see the normal instructions for installing dcpromo on Windows, with |
|||
the exception that you should not check the 'DNS server' option box |
|||
when it is offered. Right now you should either use Windows for DNS, |
|||
or use Samba and bind9 for DNS. Mixing the two can work, but it is an |
|||
advanced topic that is beyond the scope of this howto. |
|||
= Backup and Recovery of a Samba AD DC = |
|||
See the Samba [[Backup_and_Recovery|Backup and Recovery]] howto. |
|||
= Migrating an Existing Samba Domain to Samba = |
|||
= Further Samba-related Documentation = |
|||
It is very likely that you already have a running Samba3 domain on your network. The question is, how do you migrate that domain and all of its users and machines over to a new Samba 4 based domain without having to move every user profile and machine to the new domain? The answer is the [[Samba4/samba-tool/domain/classicupgrade/HOWTO|samba-tool domain classicupgrade]] function. |
|||
See [[User_Documentation|User Documentation]]. |
|||
= Connecting other services to your new/migrated Active Directory = |
|||
If you finished setting up or migrating to Samba 4, you maybe want to connect other services |
|||
to your new Active Directory. Have a look at the [[Authenticating_other_services_against_AD|Authenticating other services against AD]] page. |
|||
= Setup your firewall = |
|||
If you are setting up samba to work with your firewall, check out the [[Samba_port_usage|Samba port usage]] page. |
|||
= Report Your Success/Failure! = |
|||
---- |
|||
Samba, as a replicating domain controller, is still developing rapidly. |
|||
[[Category:Domain Control]] |
|||
We'd like to hear from users about their successes and |
|||
[[Category:Active Directory]] |
|||
failures. We would encourage you to report both your successes and failures |
|||
to the [mailto:samba-technical@lists.samba.org samba-technical] mailing list on http://lists.samba.org |
Revision as of 15:57, 17 August 2018
Introduction
Starting from version 4.0, Samba is able to run as an Active Directory (AD) domain controller (DC). If you are installing Samba in a production environment, it is recommended to run two or more DCs for failover reasons.
This documentation describes how to set up Samba as the first DC to build a new AD forest. Additionally, use this documentation if you are migrating a Samba NT4 domain to Samba AD. To join Samba as an additional DC to an existing AD forest, see Joining a Samba DC to an Existing Active Directory.
Samba as an AD DC only supports:
- the integrated LDAP server as AD back end. For details, see the frequently asked question (FAQ) Does Samba AD DCs Support OpenLDAP or Other LDAP Servers as Back End?
- the MIT and Heimdal Kerberos Key Distribution Center (KDC).
- Samba uses the MIT KDC provided by your operating system if you run Samba 4.7 or later and has been built using the
--with-system-mitkrb5
option. In other cases Samba uses the Heimdal KDC included in Samba. For further details about Samba using the MIT KDC, see Running a Samba AD DC with MIT Kerberos KDC.
Preparing the Installation
- Select a host name for your AD DC.
- Do not use NT4-only terms as host name, such as
PDC
orBDC
. These modes do not exist in an AD and cause confusion.
- Select a DNS domain for your AD forest. The name will also be used as the AD Kerberos realm.
Make sure that you provision the AD using a DNS domain that will not need to be changed. Samba does not support renaming the AD DNS zone and Kerberos realm. - For additional information, see Active Directory Naming FAQ.
- Use a static IP address on the DC.
- Disable tools, such as
resolvconf
, that automatically update your/etc/resolv.conf
DNS resolver configuration file. AD DCs and domain members must use an DNS server that is able to resolve the AD DNS zones.
- Verify that no Samba processes are running:
# ps ax | egrep "samba|smbd|nmbd|winbindd"
- If the output lists any
samba
,smbd
,nmbd
, orwinbindd
processes, shut down the processes.
- Verify that the
/etc/hosts
file on the DC correctly resolves the fully-qualified domain name (FQDN) and short host name to the LAN IP address of the DC. For example:
127.0.0.1 localhost localhost.localdomain 10.99.0.1 DC1.samdom.example.com DC1
- The host name and FQDN must not resolve to the
127.0.0.1
IP address or any other IP address than the one used on the LAN interface of the DC.
- If you previously ran a Samba installation on this host:
- Remove the existing
smb.conf
file. To list the path to the file:
- Remove the existing
# smbd -b | grep "CONFIGFILE" CONFIGFILE: /usr/local/samba/etc/samba/smb.conf
- Remove all Samba database files, such as
*.tdb
and*.ldb
files. To list the folders containing Samba databases:
- Remove all Samba database files, such as
# smbd -b | egrep "LOCKDIR|STATEDIR|CACHEDIR|PRIVATE_DIR" LOCKDIR: /usr/local/samba/var/lock/ STATEDIR: /usr/local/samba/var/locks/ CACHEDIR: /usr/local/samba/var/cache/ PRIVATE_DIR: /usr/local/samba/private/
- Starting with a clean environment helps to prevent confusion and ensures that no files from any previous Samba installation will be mixed with your new domain DC installation.
- Remove an existing
/etc/krb5.conf
file:
# rm /etc/krb5.conf
Installing Samba
For details, see Installing Samba.
Only install a maintained Samba version. For details, see Samba Release Planning. |
Provisioning a Samba Active Directory
The Samba AD provisioning process creates the AD databases and adds initial records, such as the domain administrator account and required DNS entries.
If you are migrating a Samba NT4 domain to AD, skip this step and run the Samba classic upgrade. For details, see Migrating a Samba NT4 Domain to Samba AD (Classic Upgrade).
The AD provisioning requires root permissions to create files and set permissions. |
The samba-tool domain provision
command provides several parameters to use with the interactive and non-interactive setup. For details, see:
# samba-tool domain provision --help
When provisioning a new AD, it is recommended to enable the NIS extensions by passing the --use-rfc2307 parameter to the samba-tool domain provision command. This enables you to store Unix attributes in AD, such as user IDs (UID), home directories paths, group IDs (GID). Enabling the NIS extensions has no disadvantages. However, enabling them in an existing domain requires manually extending the AD schema. For further details about Unix attributes in AD, see:
|
Parameter Explanation
Set the following parameters during the provisioning:
Interactive Mode Setting | Non-interactive Mode Parameter | Explanation |
---|---|---|
--use-rfc2307
|
--use-rfc2307
|
Enables the NIS extensions. |
Realm
|
--realm
|
Kerberos realm. This is also used as the AD DNS domain. For example: samdom.example.com .
|
Domain
|
--domain
|
NetBIOS domain name. It is recommended to use the first part of the AD DNS domain. For example: samdom .
|
Server Role
|
--server-role
|
Installs the domain controller DC role.
|
DNS backend
|
--dns-backend
|
Sets the DNS back end. The first DC in an AD must be installed using a DNS back end. Note that the BIND9_FLATFILE is not supported and will be removed in a future Samba version.
|
DNS forwarder IP address
|
not available | This setting is only available when using the SAMBA_INTERNAL DNS back end. For details, see Setting up a DNS Forwarder.
|
Administrator password
|
--adminpass
|
Sets the domain administrator password. If the password does not match the complexity requirements, the provisioning fails. For details, see Microsoft TechNet: Passwords must meet complexity requirements. |
Other parameters frequently used with the samba-tool domain provision
command:
--option="interfaces=lo eth0" --option="bind interfaces only=yes"
: If your server has multiple network interfaces, use these options to bind Samba to the specified interfaces. This enables thesamba-tool
command to register the correct LAN IP address in the directory during the join.
do NOT use NONE as the DNS backend, it is not supported and will be removed in a future Samba version. |
If using Bind as the DNS backend, do NOT use BIND9_FLATFILE , it is not supported and will be removed in a future Samba version. |
Once you have provisioned the first DC in an AD domain, do not provision any further DCs in the same domain, Join any further DCs. |
Provisioning Samba AD in Interactive Mode
To provision a Samba AD interactively, run:
# samba-tool domain provision --use-rfc2307 --interactive Realm [SAMDOM.EXAMPLE.COM]: SAMDOM.EXAMPLE.COM Domain [SAMDOM]: SAMDOM Server Role (dc, member, standalone) [dc]: dc DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE) [SAMBA_INTERNAL]: SAMBA_INTERNAL DNS forwarder IP address (write 'none' to disable forwarding) [10.99.0.1]: 8.8.8.8 Administrator password: Passw0rd Retype password: Passw0rd Looking up IPv4 addresses Looking up IPv6 addresses No IPv6 address will be assigned Setting up share.ldb Setting up secrets.ldb Setting up the registry Setting up the privileges database Setting up idmap db Setting up SAM db Setting up sam.ldb partitions and settings Setting up sam.ldb rootDSE Pre-loading the Samba 4 and AD schema Adding DomainDN: DC=samdom,DC=example,DC=com Adding configuration container Setting up sam.ldb schema Setting up sam.ldb configuration data Setting up display specifiers Modifying display specifiers Adding users container Modifying users container Adding computers container Modifying computers container Setting up sam.ldb data Setting up well known security principals Setting up sam.ldb users and groups Setting up self join Adding DNS accounts Creating CN=MicrosoftDNS,CN=System,DC=samdom,DC=example,DC=com Creating DomainDnsZones and ForestDnsZones partitions Populating DomainDnsZones and ForestDnsZones partitions Setting up sam.ldb rootDSE marking as synchronized Fixing provision GUIDs A Kerberos configuration suitable for Samba 4 has been generated at /usr/local/samba/private/krb5.conf Setting up fake yp server settings Once the above files are installed, your Samba4 server will be ready to use Server Role: active directory domain controller Hostname: DC1 NetBIOS Domain: SAMDOM DNS Domain: samdom.example.com DOMAIN SID: S-1-5-21-2614513918-2685075268-614796884
The interactive provisioning mode supports passing further parameters to the samba-tool domain provision command. This enables you to modify parameters that are not part of the interactive setup. |
Provisioning Samba AD in Non-interactive Mode
For example, to provision a Samba AD non-interactively with the following settings:
- Server role:
dc
- NIS extensions enabled
- Internal DNS back end
- Kerberos realm and AD DNS zone:
samdom.example.com
- NetBIOS domain name:
SAMDOM
- Domain administrator password:
Passw0rd
# samba-tool domain provision --server-role=dc --use-rfc2307 --dns-backend=SAMBA_INTERNAL --realm=SAMDOM.EXAMPLE.COM --domain=SAMDOM --adminpass=Passw0rd
Setting up the AD DNS back end
Skip this step if you provisioned the DC using the SAMBA_INTERNAL
DNS back end.
- Set up the BIND DNS server and the
BIND9_DLZ
module. For details, see Setting up a BIND DNS Server.
- Start the BIND DNS server. For example:
# systemctl start named
- For details how to start services, see you distribution's documentation.
Configuring the DNS Resolver
Domain members in an AD use DNS to locate services, such as LDAP and Kerberos. For that, they need to use a DNS server that is able to resolve the AD DNS zone.
On your DC, set the AD DNS domain in the domain
and the IP of your DC in the nameserver
parameter of the /etc/resolv.conf
file. For example:
search samdom.example.com nameserver 10.99.0.1
Create a reverse zone
You can optionally add a reverse lookup zone.
# samba-tool dns zonecreate <Your-AD-DNS-Server-IP-or-hostname> 0.99.10.in-addr.arpa Password for [administrator@SAMDOM.EXAMPLE.COM]: Zone 0.99.10.in-addr.arpa created successfully
If you need more than one reverse zone (multiple subnets), just run the above command again but with the data for the other subnet.
The reverse zone is directly live without restarting Samba or BIND.
Configuring Kerberos
In an AD, Kerberos is used to authenticate users, machines, and services.
During the provisioning, Samba created a Kerberos configuration file for your DC. Copy this file to your operating system's Kerberos configuration. For example:
# cp /usr/local/samba/private/krb5.conf /etc/krb5.conf
Do not create a symbolic link to the the generated krb5.conf file. In Samba 4.7 and later, the /usr/local/samba/private/ directory is no longer accessible by other users than the root user. If the file is a symbolic link, other users are not able to read the file and, for example, dynamic DNS updates fail if you use the BIND_DLZ DNS back end. |
The pre-created Kerberos configuration uses DNS service (SRV) resource records to locate the KDC.
Testing your Samba AD DC
To start the samba
service manually, enter:
# samba
Samba does not provide System V init scripts, systemd
, upstart
, or other services configuration files.
- If you installed Samba using packages, use the script or service configuration file included in the package to start Samba.
- If you built Samba, see Managing the Samba AD DC Service.
Verifying the File Server
To list all shares provided by the DC:
$ smbclient -L localhost -U% Domain=[SAMDOM] OS=[Unix] Server=[Samba x.y.z] Sharename Type Comment --------- ---- ------- netlogon Disk sysvol Disk IPC$ IPC IPC Service (Samba x.y.z) Domain=[SAMDOM] OS=[Unix] Server=[Samba x.y.z] Server Comment --------- ------- Workgroup Master --------- -------
The netlogon and sysvol shares were auto-created during the provisioning and must exist on a DC. |
To verify authentication, connect to the netlogon
share using the domain administrator account:
$ smbclient //localhost/netlogon -UAdministrator -c 'ls' Enter Administrator's password: Domain=[SAMDOM] OS=[Unix] Server=[Samba x.y.z] . D 0 Tue Nov 1 08:40:00 2016 .. D 0 Tue Nov 1 08:40:00 2016 49386 blocks of size 524288. 42093 blocks available
If one or more tests fail, see Troubleshooting.
Verifying DNS
To verify that your AD DNS configuration works correctly, query some DNS records:
- The tcp-based
_ldap
SRV record in the domain:
$ host -t SRV _ldap._tcp.samdom.example.com. _ldap._tcp.samdom.example.com has SRV record 0 100 389 dc1.samdom.example.com.
- The udp-based
_kerberos
SRV resource record in the domain:
$ host -t SRV _kerberos._udp.samdom.example.com. _kerberos._udp.samdom.example.com has SRV record 0 100 88 dc1.samdom.example.com.
- The A record of the domain controller:
$ host -t A dc1.samdom.example.com. dc1.samdom.example.com has address 10.99.0.1
If one or more tests fail, see Troubleshooting.
Verifying Kerberos
- Request a Kerberos ticket for the domain administrator account:
$ kinit administrator Password for administrator@SAMDOM.EXAMPLE.COM:
The Kerberos realm is automatically appended, if you do not pass the principal in the user@REALM
format to thekinit
command.
Set Kerberos realms always in uppercase.
- List the cached Kerberos tickets:
$ klist Ticket cache: FILE:/tmp/krb5cc_0 Default principal: administrator@SAMDOM.EXAMPLE.COM Valid starting Expires Service principal 01.11.2016 08:45:00 12.11.2016 18:45:00 krbtgt/SAMDOM.EXAMPLE.COM@SAMDOM.EXAMPLE.COM renew until 02.11.2016 08:44:59
If one or more tests fail, see Troubleshooting.
Configuring Time Synchronisation
Kerberos requires a synchronised time on all domain members. For further details and how to set up the ntpd
service, see Time Synchronisation.
Using the Domain Controller as a File Server
Whilst the Samba AD DC is able to provide file shares, just like all other installation modes, the Samba team does not recommend using a DC as a file server for the following reasons:
- For anything but the smallest organisations, having more than one DC is a really good backup measure, and makes upgrades safer
- It encourages upgrades of the DC to also be upgrades of the host OS every year or two, because there isn't complex data to transition or other services involved.
- This means upgrades can be done by installing fresh, and replicating in the changes, which is better tested in Samba, gains new features and avoids a number of lingering data corruption risks.
- The DC and file-server have different points at which an organisation would wish to upgrade. The needs for new features on the DC and file server come at different times. Currently the AD DC is evolving rapidly to gain features, whereas the fileserver, after over 20 years, is quite rightly more conservative.
- mandatory smb signing is enforced on the DC.
If you do decide to use the Samba DC as a fileserver, please consider running a VM, on the DC, containing a separate Samba Unix domain member and use this instead.
If you must use the Samba DC as a fileserver, you should be aware that the auto-enabled acl_xattr
virtual file system (VFS) object enables you to only configure shares with Windows access control lists (ACL). Running shares with POSIX ACLs on a Samba DC is not supported and will not work.
To provide network shares with the full capabilities of Samba, set up a Samba domain member with file shares. For details, see:
If you only have a small domain (small office, home network) and do not want to follow the Samba team's recommendation and use the DC additionally as a file server, configure Winbindd before you start setting up shares. For details, see Configuring Winbindd on a Samba AD DC.
Troubleshooting
For further details, see Samba AD DC Troubleshooting.
See User Documentation.