https://bugs.freenas.org/issues/6323
The issue I have looks very similar to this one on the bug tracker but rather than pollute that I thought i'd post here first as i'm not 100% it is the same problem.
The freenas install/config on my main general nas box is quite old having been upgraded from early on in v8, although I possibly started from scratch with 8.3.
Groups that were created on the initial config do not resolve in windows I just get account unknown and the SID shown, if I create a new user/group or assign one that was creating more recently (circa 12 months ago but I can't be exact) then it will work and resolve in windows. These groups are added as extra v4 acls on the files/folders in the dataset, with root/wheel as the unix owning user/group, these do resolve.
"net groupmap list" is empty which i'm not sure whether this is a) correct behaviour and b) anything to do with this problem.
The only thing I do notice is the SID that is returned for the account unknown entry the last 4 numbers seem to reflect the unix gid number which for the assigned group is 1001 but the SID entry has 1003 as the last 4 numbers.
Anyone experienced this before or know of anything I can look at to try and resolve it? Google hasn't helped me at this point but i'm still trying.
The issue I have looks very similar to this one on the bug tracker but rather than pollute that I thought i'd post here first as i'm not 100% it is the same problem.
The freenas install/config on my main general nas box is quite old having been upgraded from early on in v8, although I possibly started from scratch with 8.3.
Groups that were created on the initial config do not resolve in windows I just get account unknown and the SID shown, if I create a new user/group or assign one that was creating more recently (circa 12 months ago but I can't be exact) then it will work and resolve in windows. These groups are added as extra v4 acls on the files/folders in the dataset, with root/wheel as the unix owning user/group, these do resolve.
"net groupmap list" is empty which i'm not sure whether this is a) correct behaviour and b) anything to do with this problem.
The only thing I do notice is the SID that is returned for the account unknown entry the last 4 numbers seem to reflect the unix gid number which for the assigned group is 1001 but the SID entry has 1003 as the last 4 numbers.
Anyone experienced this before or know of anything I can look at to try and resolve it? Google hasn't helped me at this point but i'm still trying.