FreeNAS with Active Directory generated users

Hello, I've tried to set up FreeNAS(9.3 - with the latest update) to share a directory so Windows 8.1 users on the network can access it. The entire network is Windows based and the server providing the AD configuration is Server 2008 R2 Enterprise.

Now I've managed to create local freeNAS users and have users connect with the previously mentioned nas created accounts, it works, but I've run into some issues when trying to go the AD route.

  1. Had an issue with the network interface, first it didn't want to work with a set ipv4 address(it would work a short while then it would stop, needing a reconfigure for it to work again).
  2. Tried DHCP, again, it worked but only for a while. I didn't apply the latest update, was running on the stock 9.3 download from the freeNAS page. After the update it seems to work well.
  3. DNS seemed to be quite finicky, luckily I had 3 on the network so I managed to get it to work.
  4. CIFS and AD gave me some headaches aswell()
    I've set AD with the domain(company.companyname.com) and my AD-created account that I use to connect to Lync, Outlook and the rest and I've set the permissions(yes, my domain pops up in the user/group owner boxes and I have my user as owner and I've tried both DOMAIN\domain users aswell as a group specifically created for testing the nas box)
    For CIFS I've set the following: NetBIOS: freenas, Workgroup: first I had 'WORKGROUP' as it was default then I switched to company.companyname(left out the .com as it seemingly didn't allow me to connect to the share).

When I try to connect to the share via Windows it simply does not let me.
Any ideas? I'd appreciate any feedback.
Thanks

Have you tried setting up an iSCSI target on FreeNAS, mounting that on your windows server and sharing that through your windows server? It adds a little overhead but not much. Then it's basically a virtual drive on your windows server that you have full ntfs control over. Just like if it were local attached storage.

1 Like

Oh lord, that looks so much easier. Haven't tried it yet as I'm not at the office during the weekend but I might give it a go via virtual machines at home. Wasn't aware that this functionality was built into FreeNAS, thanks.
Since iSCSI just makes a drive and gives it to the Windows user to do with it what he wants can this be done without having to deal with AD? I'd like to know if I can simply set a machine with freeNAS, mount the target iSCSI drive on a Windows 8 rig and have the users do with it what they will. Is that palpable?, and if so, how?

Cheers

If you don't mount the iSCSI drive on a server system and you use an 8.1 pro system, you will have that same 20 user connection limit that you were dealing with before. If you mount the iSCSI drive on a windows server machine, you will have a connection far greater than what the NAS box can even handle.

So once you mount the iSCSI drive to your windows server, you can create a folder on that drive on your windows server. Right click on that folder and pick share. All ntfs and active directory permissions will apply and you will be the only person who secretly knows freenas is actually serving up the data in the background.

If you don't have a windows server to set this up on, you will want to dig deeper into the freenas active directory features. You might be thinking , "Oh how about I just create an iSCSI target on freenas and then setup the iSCSI initiators on all of my client machines to connect to the same iSCSI target!" Sorry, it doesn't really work that way until you get into clustering.

Here is a good youtube video describing exactly what I am talking about.

1 Like

While digging on the subject this guide popped in and I'll stick to the iSCSI mounted on Windows Server method I'll give it a go tomorrow and come back with a reply on how things worked, thanks for the help.

Yeah, worked like a charm. Perfect solution for this case, thanks.

Glad to help!