[Samba] Winbind not able to start

[Andrey Repin]

Greetings, Timo Altun!

> Fyi, the smb.conf on AD (got a bit of a strange naming convention for
> workgroup/realm, but this way windows machines do not notice the change
> from NT4 domain to AD):

They do notice. And if you try to roll back migration, you'll see that
machines that once logged in to AD no longer able to login to old domain.
The only part that visible changes is the default suffix, and in default
Windows configuration, it is changed automatically once the system joins AD
for the first time.

> # Global parameters
> [global]
> workgroup = MAYWEG.NET

Said the above, your configuration only works, because you do not have older
systems in your network, that do not understand periods in workgroup names.
In all other cases, you could have left the workgroup as it once was.

> realm = INTRANET.MAYWEG.NET
> netbios name = SERVER06
> interfaces = lo, eth0
> bind interfaces only = Yes
> server role = active directory domain controller
> server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbind,
> ntp_signd, kcc, dnsupdate
> idmap_ldb:use rfc2307 = yes

> [netlogon]
> path = /var/lib/samba/sysvol/intranet.mayweg.net/scripts
> read only = No

> [sysvol]
> path = /var/lib/samba/sysvol
> read only = No


-- 
With best regards,
Andrey Repin
Saturday, April 11, 2015 18:49:42

Sorry for my terrible english...