Details
-
Type:
Bug
-
Status: Engineering Closed (View Workflow)
-
Priority:
Low
-
Resolution: User Configuration Error
-
Affects Version/s: None
-
Fix Version/s: N/A
-
Component/s: Directory Services
-
Labels:None
Description
We noticed in the 11.3 and 11.3-U1 updates (did not have this problem in 11.2U-7) that the ability to specify a domain controller was removed. This has caused an interesting problem on our network in that whenever a connection is lossed to the primary domain controller, the FreeNAS system will look to our secondary domain controller. There is no way at this point to make the FreeNAS look at the primary domain controller again even if it is available. We have to shutdown the seconday domain controller and reboot the FreeNAS device. Once it has connection to the primary we can boot the secondary domain controller. Note that if we leave the secondary running and just reboot the FreeNAS device it will go directly to the secondary domain controller even though the primary is available.