Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Thanks for using the TrueNAS Community Edition issue tracker! TrueNAS Enterprise users receive direct support for their reports from our support portal.

Cannot join Active Directory in Truenas Core 12.0 U2

Description

I did a fresh install of truenas 12.0 U1 (because that's what I had previously downloaded) immediately upgraded to U2 and cannot join active directory. The only other setting I set was the Timezone. When doing so, I receive the following error:

[EFAULT] activedirectory_update: Failed to validate domain configuration: [EFAULT] Netlogon connection to [vpuprdc01.bapm.com] failed with error: An invalid parameter was passed to a service or function.

Debug attached to this ticket.

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Show:

Andrew Walker February 19, 2021 at 5:19 PM

Verified that fix in https://ixsystems.atlassian.net/browse/NAS-109434#icft=NAS-109434 resolved this user's issue through remote session. Will close this ticket out. Progress of code changes can be followed in associated ticket.

Andrew Walker February 18, 2021 at 7:36 PM

Confirmed with another user via remote session that a WIP fix for this issue is sufficient. Will confirm with original user who reported this issue, and close out ticket if fix is good.

Andrew Walker February 18, 2021 at 1:58 PM

We can arrange details via email. My email address is awalker@ixsystems.com.

Andrew Walker February 18, 2021 at 1:58 PM

, can we schedule a teamviewer session so that I can investigate? I don't see this issue in the lab.

Petr February 14, 2021 at 1:43 PM

I have had a 12.0-U.1.1 which I upgraded to 12.0-U2.

Then I wanted to join AD and I received same errors:

— [EFAULT] activedirectory_update: Failed to validate domain configuration: [EFAULT] Netlogon connection to [dc01.xxx.local] failed with error: An invalid parameter was passed to a service or function.

Then I downgraded to 12.0-U.1.1 and I was immediately Able to join the same domain. No problem. Status now shows as Healhy.

I am still on 12.0-U.1.1 in case someone needs me to do some tests or send some logs. As it is a secondary but production server, I do not want to play with it up and down, but I am ready to run the upgrade when I am asked to do so by some developer and perhaps even try to leave the domain and join again if it it is considered helpful for the bug chase. 

Done

Details

Assignee

Reporter

Labels

Impact

Medium

Components

Fix versions

Affects versions

Priority

More fields

Katalon Platform

Created February 12, 2021 at 5:10 PM
Updated July 1, 2022 at 5:13 PM
Resolved February 19, 2021 at 5:19 PM

Flag notifications