[Samba] AD DC Corrupt recycle bin in redirected folders

[Philippe LeCavalier]

On Wed, Jan 18, 2017 at 10:43 AM Philippe LeCavalier <
support at plecavalier.com> wrote:

> Hi everyone,
>
> First off, I really don't know what to provide so please just ask what is
> needed. Here's what I think is relevant starting with a brief description:
>
> I have samba4 as AD DC for windows 10 clients. Roaming profiles are on a
> share on the DC and are working perfectly. However, redirected folder, also
> residing on the DC are not working as expected. I have yet to put my finger
> on exactly how this is occurring but at some random time, usually a few
> days, the user suddenly gets a warning that each recycle bin on /her/his
> redirected folders is corrupt.
>
> I manage the permissions on a Win7 station in the local LAN. When I login
> to that station and check the permissions and ownership it appears fine to
> me. However, if I check off the 'replace permissions and ownership...'
> checkbox to re-apply (without changing anything) and have the user log
> off/on everything returns to normal. A few days go by and the same issue
> re-appears.
>
> This is a pretty fresh setup. I install the AD DC on a brand new system,
> created all the users from scratch and copied their docs over. (and set
> permissions accordingly including a replace on subfolders for perms and
> owner). Windows stations are also brand new and have the most recent MS
> updates.
>
> Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64
> GNU/Linux
>
>  samba                                 4.2.10+dfsg-0+deb8u3  amd64
>
> redirected folders are: documents, favorites, desktop, cookies and start
> menu applied via GPO as per wiki. (permissions initially set as per wiki as
> well)
>
> I know it's not advised to host shared files on the DC but was thinking
> since they're not shares accessed by anyone else but the owner it would be
> suitable to host them on the DC. I can host them on a separate samba
> machine if that will resolve this (or make things simpler and at least help
> in resolving this).
>
> The only thing catching my eye in the logs is this:
>  open_internal_pipe: Could not connect to lsarpc pipe:
> NT_STATUS_UNSUCCESSFUL
> [2016/12/07 12:24:28.522364,  0]
> ../source3/winbindd/winbindd_cm.c:1670(wb_open_internal_pipe)
>   open_internal_pipe: Could not connect to dssetup pipe:
> NT_STATUS_UNSUCCESSFUL
>
> Like I said if there's something I can provide that's more relevant please
> just ask.
> --
> Regards,
> Phil
>

Anyone?
-- 
Regards,
Phil