Unable to get new build on my domain

jahesus

Cadet
Joined
Mar 23, 2023
Messages
3
First I was told it was unable to reach the domain controllers. Pinging the domain revealed that it was pinging an old IP address from a dc that wasnt up any more. That server was demoted, and removed from the domain, and dns long ago. No idea where it came from. Couldnt find it.

Solution: I built a new domain controller at that IP address and it got me into a new error.


New error:

Attempt to connect to netlogon share failed with error: [ENOTCONN] (6, 'WBC_ERR_WINBIND_NOT_AVAILABLE: wbcInterfaceDetails failed', '../../nsswitch/py_wbclient.c:1680').​

2023-03-24 05:23:40 (US/Central)



This is a new install of TrueNas Scale.
Both domain controllers, and true nas are on central time zone.
TrueNAS NTP set as the primary dc.
Primary Name Server is set as the Pimary DC.

AMD FX(tm)-8150 Eight-Core Processor
16GB Ram
6x14TB WD RedPRO - not built into anything other than a single pool yet.

Logs attached.
 

Attachments

  • debug-Vanir-20230324145703.tgz
    803.5 KB · Views: 62

jahesus

Cadet
Joined
Mar 23, 2023
Messages
3
I completely reinstalled everything.
ONLY NTP Server is the Primary DC:
1679713407892.png


Error When Adding To Domain:
1679713456040.png


Ive rebooted both the DC, the truenas, and the ntp service on the nas each independently. Ive also tried adding the same time server the primary dc is synching to time.windows.com, as a secondary and still the same error about time. Even when I manually set the time on the nas to match the dc I get the same error
 

Attachments

  • debug-Vanir-20230324222256.tgz
    275.6 KB · Views: 59
Top