![]() Usage: Backups, Personal files, and MultiMedia. Storage: 28 TB : 1 x 12 TB, 2 x 8 TB in a single pool of single vdevs. Intel Core i3-4330 (Specified as a 4130, but who am I to complain about a free upgrade?) Intel C226 server chipset (5 x SATA, Gb NIC, USB3, ECC) Service ix-pre-samba start # create config (and group mapping) with known SID Net groupmap cleanup # this should blow away all mappings Perhaps I'd best wait to see if anything in the debug files stands out to one of you FreeNAS experts before stopping / restarting the samba service? If so then how are they going to change mappings on the Windows machines though?Īnything else I should know before running these lines? These I assume are run from the FreeNAS GUI shell screen. The commands below ( from ) are said to perhaps fix this issue. It does have the full control permissions so that is not the problem but that the Windows group "EVERYONE" has lost some rights to this new "unknown" is the issue I am assuming! ![]() ![]() The UNIX wheel group is straight from FreeNAS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |