Building NEW TrueNAS box - want to utilize my AD/DS Domain

[bearhntr]

Hello Everyone....newbie here.

I am looking (hopefully) to move away from XigmaNAS to TrueNAS - but have some questions before I do. I am hoping that I can get some guidance.

My environment is 95% Windows (Server 2019 or 2016) and Windows 10 laptops and computers (one Windows 7). I have a brand new Server_2019 Domain Controller - which handles AD DS / DNS / DHCP and LDAP (not setup yet).

I have an old box which is currently (specs below) - that I will be used for TrueNAS.

Platform: x64-embedded on Intel(R) Atom(TM) CPU D2701 @ 2.13GHz
System: I-O DATA HDL-Z Series
BIOS: Phoenix Technologies Ltd. Version: IODATA - Z2WxC PR11 11/15/2013
RAM: 8GB DDR3 1600 MHz
OS: XigmaNAS 12.2.0.4 - Ornithopter (FreeBSD 12.2-RELEASE-p7)

I would like to make sure that I can setup shares which I can use for storing files to the NAS and for my servers to use for BACKUPs. (much like mapping a drive) - but I would like to have AD users have access to these shares.

My questions are as follows:

1) Is this possible with TrueNAS?

2) What is needed for setting this up? I have a group in AD for BACKUP_USERS and NAS_USERS (as well as individual users).

3) Does TrueNAS - support IPv6? I have setup my home domain with DHCPv6 and DNSv6 and this is working for almost every device in my home (assigning IPs and PTR records).

Much Thanks,
Curtis

 

[c77dk]

Don't see why it shouldn't be possible - have a TrueNAS server running as backend storage for some servers in AD environment.
I just followed the docs and made some changes to make it use uid/gid from AD (migrating from old system using this)
Regarding IPv6 - no problems at all

 

[bearhntr]

Don't see why it shouldn't be possible - have a TrueNAS server running as backend storage for some servers in AD environment.
I just followed the docs and made some changes to make it use uid/gid from AD (migrating from old system using this)
Regarding IPv6 - no problems at all

Thank you for the reply - now just to find the 'proper' documentation.

 

[c77dk]

Thank you for the reply - now just to find the 'proper' documentation.

The docs The only thing I believe I had to do extra was to make sure the netbios name in Samba was correct (had renamed the server). It was on a 12.0, so not so current information anymore.

 

[bearhntr]

Don't see why it shouldn't be possible - have a TrueNAS server running as backend storage for some servers in AD environment.
I just followed the docs and made some changes to make it use uid/gid from AD (migrating from old system using this)
Regarding IPv6 - no problems at all

UPDATE -- Removed XigmaNAS from that box - installed TrueNAS-12.0-U5.1

So far it seems to be working. I have static IPv4 set and IPv6 set to Auto-Configure...got address from that (even though not in my 2601:c9:200:a73::/64 setup. Will have to figure that one out. I got a Link-Local address of fe80::3676::/64 type address.

Setup pool_1 with the 2 drives as a mirror - now I am guessing that I need to setup SMB shares so that I can map a drive. I see TRUENAS in Windows Networking - but nothing to map.

Then I get to play with setting up AD DS and LDAP in TrueNAS.

Thanks Again,
Curtis

 

[bearhntr]

OK - Question???

Does TrueNAS not setup a PTR record in my DNS? I can ping it with no problems - both the IPv4 and the Link-Local address -- but no name resolution at all.

 

[bearhntr]

UPDATE:

I added a PTR record - at it appears that FreeBSD or something else does not auto-register to the DNS.

I was able to setup the ActiveDirectory and get the Backups account working to TrueNAS and my backups are running (so far 3 of them have been successful). -- Thanks everyone.

Now I get to open a new query in the IPv6 area. LOL

Curtis