ActiveDirectory client retry after initial failure

[PanagiotisK]

Hello,

Right now we have a deployment of FreeNAS 8.3 which is configured as an ActiveDirectory client. If the AD domain controller is not online, FreeNAS will fail to read the user information. If the AD is brought online, the AD client on FreeNAS doesn't try to reconnect and read the user information. That requires having brought AD domain controller online in prior to FreeNAS.

We are planning on migrating the AD domain controller to a Virtual Machine of which the image will be served by a new FreeNAS (9.3) installation. Therefore, we fall into an interdepedency where AD domain controller requires the image from FreeNAS and FreeNAS requires AD domain controller to be online in order to connect to as an AD client.

My question is: in the latest version of FreeNAS, does the AD client try to reconnect to the AD domain controller in case of an initial failure?

Thank you in advance.

 

[dlavigne]

Did you find an answer to this? I don't know the answer, only that a lot has changed Samba-wise between 8.3 and 9.3.

 

[PanagiotisK]

Didn't have the chance yet as I'm having issues with adding the FreeNAS systme to Active Directory. When I'll have some news I'll post them.

 

[PanagiotisK]

An update on this after having added the FreeNAS 9.3 system to the domain.

If the Domain Controller is not available at boot time, as expected it fails to detected it. It tries a few times during the booting process and it keeps failing. In order to by pass great latency, the system has been configured with static IP. After bringing the DC back online, the FreeNAS system doesn't keep trying to look for the DC, ending without the required user/group information. I had to run manually the /etc/directoryservice/ActiveDirectory/ctl script in order to bind to the DC. Apart from adding a cronjob, is there another way of handling this?

 

[Dotty]

I'm running 9.10.1-U4 and Im also looking for a solution to this issue.