samba - Feb 2019 - how to configure smb.conf after installing samba-dc.x86_64 0:4.8.3-4.el7 centos7 (trusted: samba@lists.samba.org)

Hi, installed samba-dc.x86_64 on a new VM. There used to be a great web
based tool to configure smb.conf or smb4.conf which used to be (in
FreeBSD Systems) /usr/local/sbin/swat

In a CentOS system, other than using plain vim how does one configure
smb.conf?

Thanks!

On Tue, 19 Feb 2019 13:44:42 -0500
"samba.x.eliezer613--- via samba" <samba at lists.samba.org>
wrote:
> Hi, installed samba-dc.x86_64 on a new VM. There used to be a great
> web based tool to configure smb.conf or smb4.conf which used to be (in
> FreeBSD Systems) /usr/local/sbin/swat
This was removed quite some time ago and it never worked a Samba DC.
> 
> In a CentOS system, other than using plain vim how does one configure
> smb.conf?
nano ?
Or if you are going to set up a Samba AD DC, then you don't, the
provision creates one for you.

It might help if you told us what sort of Samba server you want to set
up.

Rowland

On Tue, 19 Feb 2019 18:40:03 -0500
samba.x.eliezer613 at spamgourmet.com wrote:
> Hi Rowland, actually just trying to learn AD. Have a 'regular'
samba
> server running here for years. In as much as a smb.conf it seems to
> have one :
> 
> [global]
>         dns forwarder = 192.168.25.253
>         netbios name = DC1
>         realm = DC1.INTERNAL
>         server role = active directory domain controller
>         workgroup = REDACTED
> 
> [netlogon]
>         path = /var/lib/samba/sysvol/dc1.internal/scripts
>         read only = No
> 
> [sysvol]
>         path = /var/lib/samba/sysvol
>         read only = No
> 
> Since this is a AD/DC I presume there should not be browseable shares
> like [homes] or [data]
It is recommended to only use a DC for authentication.
> 
> The following was run on the AD/DC...
> 
> # smbclient -L dc1 -N
> Connection to dc1 failed (Error NT_STATUS_CONNECTION_REFUSED)
> 
> I don't think samba is really running..
> 
> # service samba restart
> 
> # journalctl -xe
> 
> [2019/02/19 18:37:26.212234,  0]
> ../source4/smbd/server.c:466(binary_smbd_main)
> Feb 19 18:37:26 dc1.internal samba[1033]:   samba version 4.8.3
> started. Feb 19 18:37:26 dc1.internal samba[1033]:   Copyright Andrew
> Tridgell and the Samba Team 1992-2018
> Feb 19 18:37:26 dc1.internal systemd[1]: PID file /run/samba/samba.pid
> not readable (yet?) after start.
> Feb 19 18:37:26 dc1.internal samba[1034]: [2019/02/19
> 18:37:26.404987, 0] ../source4/smbd/server.c:638(binary_smbd_main)
> Feb 19 18:37:26 dc1.internal samba[1034]:   binary_smbd_main: samba:
> using 'standard' process model
> Feb 19 18:37:26 dc1.internal samba[1034]: [2019/02/19
> 18:37:26.405753,
> 0] ../source4/smbd/service.c:112(server_service_startup) Feb 19
> 18:37:26 dc1.internal samba[1034]:   server_service_startup: Failed
> to start service 'rpc' - NT_STATUS_INVALID_SYSTEM_SERVICE Feb 19
> 18:37:26 dc1.internal samba[1034]: [2019/02/19 18:37:26.406035,
> 0] ../lib/util/become_daemon.c:124(exit_daemon) Feb 19 18:37:26
> dc1.internal samba[1034]:   exit_daemon: STATUS=daemon failed to
> start: Samba failed to start services, error code -107 Feb 19
> 18:37:26 dc1.internal systemd[1]: samba.service never wrote its PID
> file. Failing. Feb 19 18:37:26 dc1.internal systemd[1]: Failed to
> start Samba AD Daemon. -- Subject: Unit samba.service has failed
> -- Defined-By: systemd
> 
> Thanks!
> 
Seeing as this is running on Centos, where did you get the Samba
packages from ?
I ask this because the standard Centos packages cannot be used to
provision a domain.

Does /run/samba exist ?

Rowland

On Wed, 20 Feb 2019 09:19:27 -0500
samba.x.eliezer613 at spamgourmet.com wrote:
> Hi Rowland, no samba is not running on the VM. I will yum remove
> samba* and build from tarball and see what happens.
>
Better still, use another distro, the red-hat distros will never allow
provisioning of a Samba AD DC. Building Samba to update soon gets
tiring.

Rowland