I was hoping someone may be able to help me out here. I'm still trying out unRAID and am in the process of learning AD, so forgive me if this is some rookie mistake.

 

I have joined my unRAID box to a AD domain I have running in a VM on another machine. When I first did it, it was working well. Making a new share would assign it to the 'administrator' user in the 'domain users' group. I'd be able to go in and modify the permissions via RDP from the Windows Server and set permissions that way for various AD users/groups. Recently, however, I was working with setting the permissions of the samba shares I have published with unRAID and noticed that I now have 3 additional deny settings on all of my shares that I cannot get rid of. I try to remove them, and upon hitting apply they return. I am also prompted with a warning about how the permissions are incorrectly ordered when opening the security dialog on any shared folder. Here is a recently created samba share that automatically added the S-*-* records.

 

 

Now the 2 of the SID entries match the UID and GID for the 'administrator' on the unRAID box. I still haven't figure out where the other one is coming from though.

 

So my question is this. What is causing these entries to automatically be put in there in the first place? And is there anything I can do to disable & remove them?

I've also got this.

 

After upgrade to 6.3 unraid no longer joined to domain.

 

Having rejoined all my permissions seem to be borked.

 

Bit concerned at having to manually fix them all.

 

 

Found this answer which explains the values. So in my screenshot, the 'S-1-5-88-1-726139393' value is the UID of the share owner 'Administrator', 'S-1-5-88-2-726139380' is the GID of the share group 'Domain Users', and the 'S-1-5-88-3-16895' is a representation of the share's permissions in decimal form, in this case 0777.

 

It's not really denying permission, as the access variable is None, but annoying nonetheless.

 

Also, I do not have an issue joining the domain on 6.3.1. Left and rejoined as a test last night and that worked out fine.