I’ve managed to get TrueNAS connected to Active Directory and created a share that I can access from an AD account on a Windows client just fine. However when I try to mount the share on Ubuntu Server 24.04 I keep getting permission/logon failure.

In my fstab entry I’ve tried every combo I can think of.

domain=domain,user=user,password=pass domain=domain.local,user=user,password=pass user=domain\user,password=pass user=domain.local\user,password=pass

I’ve also tried a separate credentials file with every one of those combinations as well as versions 2.1 and 3.0. I’ve got no problem mounting shares from the Windows server without even specifying the domain.

At this point I’m pretty sure I’m missing a setting on TrueNAS but no idea what. Any ideas?

  • @zhill29OP
    1•15 days ago

    I’m assuming the domain=ip should be the IP address of the AD server right? That’s what I entered and still no luck. Same permission denied error as my past attempts.

    • @[email protected]
      1•14 days ago

      Well not so much the adress of the AD server.

      It should be the domain name of your domain that you have created.

      As in [email protected]

      The part behind the @ is the domain the user is registered to and even though the AD server might be named prod-ad-001 the text should be the domain you are trying to auth towards and the share you are accessing to should obvioisly have a connection the the AD to forward the credentials and ask if Auth is positive.

      • @zhill29OP
        1•14 days ago

        I understand that, I’ve tried both domain=CompanyWork and domain=CompanyWork.internal in my cred file and directly in fstab both result in the permission error when mounting the TrueNAS share but work just fine when mounting a share provided by Windows Server.

        • @[email protected]
          1•12 days ago

          Just for the sake of testing maybe try it with a oneliner:

          sudo mount -t cifs -o user=testuser,domain=testdomain //192.168.1.100/share /mnt

          Either way using the logs is the best way to check for discepancies. Also check in on the logs on the fileserver. Though idk what to advice to trace the logon stuff and trace whats making it fail.

          Just for the case that you dont know where to look in windows: eventviewer is the place to go. Which predifined filter though - simply google that.

          Wishing ya the best of luck mate!