Our company has been growing in the last few years and requires us to upgrade our systems a bit. We are on a local domain, we will call it mydomain.local, and use Windows Server 2012 R2 currently as our domain controller. One of the projects I was put onto was to remove all file shares from our domain controller and put them on a file server so our domain controller can do only that. So my solution was to use a Linux based system to store our files. one of our hired IT guns suggested I go with FreeNAS as an OS for this file server. So I took his advice and here we are.
Just Installed the latest version of FreeNAS on the new server build. The DNS Hostname for the new server is "filesvr" Everything installed great, and I can see it on the network. I can login to the web GUI fine. Seems to be a very robust operating system. When I first logged into the web GUI it had me go through a wizard for setup. One of the wizard steps was to create a list of shares for SMB. Which I did, the three shares are "public", "engineering" & "accounting". We also run a mixture of Windows 7 Pro and Windows 10 Pro Work Stations. All of these workstations have been slowly updated to Windows 10 Pro which is the majority of machines now. When I goto a Windows file explorer session, and put this in the address path, "\\filesvr", I get the three shares that I created. This is where I'm having an issue when I click on the share, it comes up with a Windows Security Dialog which asks's me to enter credentials to: filesvr. I use the Windows domain Administrator login with password, no good. I then try the root login and password from filesvr and no good. I must have missed the part where we bind the Windows Active directory to the shares so We can use the Windows authenticated Users. Does anyone know where those settings are or how I'm to configure windows or FreeNAS to use Windows Authenticated users instead of creating all new users for the shares?