Hello. I just wanted to confirm if this was standard functionality of FreeNAS (11.2-U5).
I'm using this server for SAMBA, so the groupmap that gets shared to windows is especially important.
I have all permissions on the shared dataset set in Windows mode.
When I create a new group in the WebUI, I can confirm that the groupmap gets created.
I run "net groupmap list" and I get the following:
New_Group (S-1-5-21-39404713-2665992434-2905834964-1155) -> New_Group
When I add more groups through the WebUI, I get more, of course:
New_Group (S-1-5-21-39404713-2665992434-2905834964-1155) -> New_Group
New_Group2 (S-1-5-21-39404713-2665992434-2905834964-1152) -> New_Group2
Now here is the strange part. If I change the group name "New_Group" to "Different_Group" in the WebUI, this is what happens:
New_Group (S-1-5-21-39404713-2665992434-2905834964-1155) -> Different_Group
New_Group2 (S-1-5-21-39404713-2665992434-2905834964-1152) -> New_Group2
If I delete the group, I would expect the SID entry to be deleted too, but that does not happen.
New_Group (S-1-5-21-39404713-2665992434-2905834964-1155) -> 1001
New_Group2 (S-1-5-21-39404713-2665992434-2905834964-1152) -> New_Group2
The solution to this problem is for me to erase the old entries before adding a new group with the same GID using the following:
net groupmap delete ntgroup='SIDVALUE'
I also have a similar issue with my users as well.
I check the list using this command: "pdbedit -Lv"
I erase the old non-existing old users using this command: "pdbedit -x -u 'username'"
I have to be very careful with user and group name creations. If I make a mistake, I need to manually clean up using the CLI to make sure the SID is correct.
Is there something I did wrong to make this situation happen, or is this the standard way FreeNas is supposed to work?
I've completly wiped both the user and groupmaps, and deleted all added users and groups to see if starting from scratch would help, but no alas.
If anyone has any insights, that would be great!
Thanks so much.
I'm using this server for SAMBA, so the groupmap that gets shared to windows is especially important.
I have all permissions on the shared dataset set in Windows mode.
When I create a new group in the WebUI, I can confirm that the groupmap gets created.
I run "net groupmap list" and I get the following:
New_Group (S-1-5-21-39404713-2665992434-2905834964-1155) -> New_Group
When I add more groups through the WebUI, I get more, of course:
New_Group (S-1-5-21-39404713-2665992434-2905834964-1155) -> New_Group
New_Group2 (S-1-5-21-39404713-2665992434-2905834964-1152) -> New_Group2
Now here is the strange part. If I change the group name "New_Group" to "Different_Group" in the WebUI, this is what happens:
New_Group (S-1-5-21-39404713-2665992434-2905834964-1155) -> Different_Group
New_Group2 (S-1-5-21-39404713-2665992434-2905834964-1152) -> New_Group2
If I delete the group, I would expect the SID entry to be deleted too, but that does not happen.
New_Group (S-1-5-21-39404713-2665992434-2905834964-1155) -> 1001
New_Group2 (S-1-5-21-39404713-2665992434-2905834964-1152) -> New_Group2
The solution to this problem is for me to erase the old entries before adding a new group with the same GID using the following:
net groupmap delete ntgroup='SIDVALUE'
I also have a similar issue with my users as well.
I check the list using this command: "pdbedit -Lv"
I erase the old non-existing old users using this command: "pdbedit -x -u 'username'"
I have to be very careful with user and group name creations. If I make a mistake, I need to manually clean up using the CLI to make sure the SID is correct.
Is there something I did wrong to make this situation happen, or is this the standard way FreeNas is supposed to work?
I've completly wiped both the user and groupmaps, and deleted all added users and groups to see if starting from scratch would help, but no alas.
If anyone has any insights, that would be great!
Thanks so much.
