AD or Windows sharing permissions?

[JediDan]

I'm using FreeNAS in a home network looking to add more client computers. I have functioning file shares via SMB but only if I set file permissions to a single specific user account. I've read various threads about setting up ACL file permissions from Windows but my last go at them got me thinking about the domain, or lack thereof, as opposed to user permissions as the possible source of my problems.

In the image below I see the domain "FREENAS", although I don't remember specifically configuring a domain anywhere in FreeNAS. When I log into Windows, by default it specifies the local computer as the domain, i.e. Local1\bob vs FREENAS\bob. I have created user accounts on FreeNAS for the handful of users as well as the user accounts existing on the client computers.

Question 1: Is this the root of my issues with file permissions? Specifically, the local user account Local1\bob doesn't exist on FreeNAS and vice versa so the file permissions and ownership don't match thus leading to accurate, though unintentional, permission errors?
Question 2: Assuming the answer to Question 1 is "yes", any recommendations and reading material on a good starting point for SOHO user accounts? LDAP? AD? Kerberos? How do you roll yours?

 

[anodos]

Windows uses SIDs, which in most cases are universally unique.
MY_ADMINS (S-1-5-21-3999357206-2668534740-3799046826-1004) -> MY_ADMINS
^^^ this is an example of a Windows SID.

Everything except for the last component uniquely identifies the domain to which the SID belongs:

Code:

truenas# net getlocalsid
SID for domain TRUENAS is: S-1-5-21-3999357206-2668534740-3799046826

There is typically no need for a home user to set up a directory service, and permissions should work without it.

 

[JediDan]

Thank you for the reply, however permissions continue to be an issue.
Here's an example trying to add a user to the security tab. The locations below only list FreeNAS as a source of names. I am unable to specify a user from the local system.