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)
This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
After reboot no connection to AD
-
Knappe
- experienced User

- Posts: 76
- Joined: 08 May 2015 08:46
- Status: Offline
- b0ssman
- Forum Moderator

- Posts: 2438
- Joined: 14 Feb 2013 08:34
- Location: Munich, Germany
- Status: Offline
Re: After reboot no connection to AD
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
write a scripts thats pings the dc.
if available done.
if not ping till available then restart samba
install script as postinit script
Nas4Free 11.1.0.4.4517. Supermicro X10SLL-F, 16gb ECC, i3 4130, IBM M1015 with IT firmware. 4x 3tb WD Red, 4x 2TB Samsung F4, both GEOM AES 256 encrypted.
-
noclaf
- experienced User

- Posts: 116
- Joined: 08 Dec 2013 12:37
- Status: Offline
Re: After reboot no connection to AD
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.
if available restart samba
if not ping till available then restart samba
//still remains risk in that ping!=server booted&ready.
- b0ssman
- Forum Moderator

- Posts: 2438
- Joined: 14 Feb 2013 08:34
- Location: Munich, Germany
- Status: Offline
Re: After reboot no connection to AD
or replace ping with a connect attempt on the samba port
Nas4Free 11.1.0.4.4517. Supermicro X10SLL-F, 16gb ECC, i3 4130, IBM M1015 with IT firmware. 4x 3tb WD Red, 4x 2TB Samsung F4, both GEOM AES 256 encrypted.
-
Knappe
- experienced User

- Posts: 76
- Joined: 08 May 2015 08:46
- Status: Offline
Re: After reboot no connection to AD
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 ?
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 ?