Hi everyone,
I've created some flexshares, but users can't actually access them. They map just fine, but when you go to open the folder Windows spits out an error related to permissions. Unix permissions on the flexshare shares folders appear correct, and the user I'm testing with is in the group associated with the flexshare I'm using to test. If I enable third party access on the share (Read) the test user gains read access to the test share.
I've noticed that the groups created in ClearOS don't actually appear in /etc/group. Is this an issue?

The whole thing looks like the test user isn't in the group to access the test share.

This is a domain-joined PC running Windows 10 1809, and I've made the registry changes as noted in here (including changing the {MyWindowsDomainName} with my own domain, without the brackets): https://www.clearos.com/resources/documentation/clearos/content:en_us:kb_adding_workstation_to_a_domain

Any tips?

edit: I determined what the issue is. While the permissions were properly set in ClearOS, it runs as a Proxmox VM with access shared storage. The storage houses the home folders and the flexshare shares. The shared storage is mounted via NFS from a storage VM. Apparently the permissions weren't correctly set there.

It's all a bit odd, as the users were able to access their U: drives just fine.