TrueNAS 13.0.U6.7 Attempt to connect to netlogon share failed with error: [EFAULT] failed to call wbcPingDc: Domain is not trusted or cannot be found

TrueNAS General
,
1

I have updated my TrueNAS Enterprise from 13.0.U6.2 straight to 13.0.U6.7. I also saved the TrueNas configuration prior to starting the update, as described in Updating Updating CORE | TrueNAS Documentation Hub

Prior to updating my TrueNAS I was able to connect to it by mapping a network drive via Windows Explore without any issues. Since the update I cannot map to it with Windows Explorer or PowerShell. When I try, I am prompted to enter in my username and password but receive the below error.

The specified network password is not correct.

This should not be happening, as I should be able to login with my Sys Admin account. Which is controlled by active directory and is working just fine on other servers. I am able to ping the TrueNAS and login to the management console and TrueNAS SuperMicro.

When I login to the TrueNAS management console and go to the alert’s icon in the top right. I have the following two warnings.

Attempt to connect to netlogon share failed with error: [EFAULT] failed to call wbcPingDc: Domain is not trusted or cannot be found…

Domain validation failed with error: [EFAULT] Time offset from Active Directory domain exceeds maximum permitted value. This may indicate an NTP Misconfiguration.

When I go to System > NTP Servers I see both of my DCs are listed along with three freebsd.ntp.pool.org.

Directory Services > Active Directory appears to be configured correctly. I have tried to rebuild directory service cache, but this did not seem to help.

Sharing > Windows Shares (SMB) is enabled and has my dataset listed.

Services for SMB are also running.

I think the issue could be either issues with NTP configs or issues with its Active Directory service account on the TrueNAS side, but I am not really sure. I am unfamiliar with TrueNAS Enterprise or any TrueNAS for that matter and BSD / Linux, so any help please be specific with what I need to do and include commands.

Any help is greatly appreciated and thank you in advance.

2

Hey @GalytheNally

Quick question - since you’re running TrueNAS Enterprise, have you contacted our Support team directly to file a ticket?

The specified network password is not correct.

SMB can sometimes present this error incorrectly when an old/incompatible protocol is being used. What version of Windows and SMB are you attempting to map the folder with? Microsoft has put in a few patches recently that changed SMB version and auth behavior, so it’s worth checking to see if any of these could be responsible for the problem; but if your domain validation/NTP is incorrect, that is the more likely issue if it’s refusing to handle the ticketing due to time drift or desync.

3

Thank you for replying to my post @HoneyBadger.

I have not reached out to IXsystems support desk because our support license has expired, and we are not in a position to renew it.

From the client (Windows 11) side I have SMB version 2 and 3 enabled. TrueNAS shows me version 4.15.13 when I run smbd -V from the shell. When I go to Sharing > Windows Shares (SMB) > Edit > Advanced Options the check box for Enable SMB2/3 Durable Handles is check.

I don’t think it’s a SMB issue. Prior to running the update, I made sure I was able to map to the TrueNAS. Once the update was finished, I was no longer able to map to the TrueNAS. No Windows updates were applied during the TrueNAS update.

4

What is interesting is when I go to

Sharing > Windows Shares (SMB) > Edit Filesystem ACL

all of the group names and usernames are replaced with their SIDs. Hopefully this will help shine some light on what is going on.

5

I am trying some of the troubleshooting steps used in [Problems getting ntpd to work](https://Problems getting ntpd to work). Here is what I found.

ntpq -p
shows my domain controllers which are also our NTP server. It also shows the following:
remote, refid, st t when poll reach delay offset jitter
ntp.server.name1, .INIT. 16 u -1024 0 0.000 0.000 0.000
ntp.server.name2, .INIT. 16 u -1024 0 0.000 0.000 0.000

cat /var/db/ntp/ntpd.drift
shows 0.000

cat /etc/ntp.conf
shows
#server 0.feebsd.pool.ntp.org Iburst maxpoll 10 minpoll 6
#server 1.feebsd.pool.ntp.org Iburst maxpoll 10 minpoll 6
#server 2.feebsd.pool.ntp.org Iburst maxpoll 10 minpoll 6
server my.ntp.server.name1 Iburst maxpoll 10 minpoll 6
server my.ntp.server.name2 Iburst maxpoll 10 minpoll 6
#restrict default ignore
restrict -6 default ignore
restrict 127.0.0.1
restrict -6 ::1
restrict 127.127.1.0
#restrict 0.feebsd.pool.ntp.org nomodify notrap nopeer noquery
#restrict 1.feebsd.pool.ntp.org nomodify notrap nopeer noquery
#restrict 2.feebsd.pool.ntp.org nomodify notrap nopeer noquery
server my.ntp.server.name1 nomodify notrap nopeer noquery
server my.ntp.server.name2 nomodify notrap nopeer noquery