XigmaNAS

Primary DC and NAS4FREE are installed on different servers.

After power interruption can both start up with different speeds.
Therefore, it may happen that NAS4FREE was started earlier, but still no AD available.
After boot, NAS4FREE never checked (again), whether an access to the AD is possible or not. In above-mentioned case, it´s not possible.
Only after a manual restart of Samba (where the service win bind starts too) can again take place authentication against the AD.

Is there any solution for this ?

--------------------------------------
Version NAS4Free 9.3.0.2 (1771)

simple fix of the top of my head.

write a scripts thats pings the dc.
if available done.
if not ping till available then restart samba

install script as postinit script

would slightly change that :

if available restart samba
if not ping till available then restart samba

//still remains risk in that ping!=server booted&ready.

or replace ping with a connect attempt on the samba port

hmm.. are you sure that the Active Directory Domain Services are NOT started after the network services during boot ?
In this scenario ping will work, Samba would restarted (but could´t connect to not yet started AD Services) and the script will stop.

May be it´s a better way to evaluate/check the output of "wbinfo -u" /"…-w" or other parameter ?