[Samba] Samba 4 Client Directory Contents Refresh

Miguel Medalha
Thu, 18 Jan 2018 20:29:07 -0000

Looks like you didn't really understand Marc's answer.

This depends on settings on the Windows client. On the server side, this is not
a question of changing behaviour, it's a question of Samba 4 supporting a
new feature, SMBv2.

I suppose that the only thing you can do on the server side is setting max
protocol to SMBv1, which is really bad for performance and for security. People
have been disabling SMBv1 everywhere.

On 18 Jan 2018 19:43, rcone via samba <samba at lists.samba.org>
wrote:
>
> Thank you for the reply.
>
> I would prefer a RHEL 7 Samba 4 directive to address this.  Like a global
directive.
>
> We have a good amount of Windows workstations of different version
involved, I do not want to have to change them all.  We do not use AD (large
workgroup).  I have only tested with Windows 7 (my workstation).
>
> My concern is merely a difference in behavior between RHEL 5 (Samba 3), and
RHEL 7 (Samba 7).  We are migrating from RHEL 5 to RHEL 7, I simply do not want
any behavior changes, and really, there should not be.
>
> If anyone out there can assist on this further, that would be great.
>
> Rick
>
> -----Original Message-----
> From: Marc Muehlfeld [mailto:mmuehlfeld at samba.org]
> Sent: Thursday, January 18, 2018 11:28 AM
> To: rcone <rcone at securepaymentsystems.com>; 'Samba (samba at
lists.samba.org)' <samba at lists.samba.org>
> Subject: Re: [Samba] Samba 4 Client Directory Contents Refresh
>
> Hello Rick,
>
> Am 17.01.2018 um 20:20 schrieb rcone via samba:
> > Starting to use Samba 4 on RHEL 7.  I noticed that new files do not
> > get refreshed automatically for display in a Windows directory listing
> > on Samba 4, and requires a manual refresh in Windows for them to>
> appear.  This behavior appears to be different from RHEL 5 (Samba 3),
> > where new files appear automatically.  Is there a new global directive
> > in Samba 4 for an automatic directory content refresh?
>
> This is a client setting and caused by SMB2 client redirector caching.
> For details, see:
>
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-7/ff686200(v=ws.10)
>
> Set all three registry keys mentioned in the MS doc to "0" and
reboot.
>
> I'm sure there is a GPO for this as well.
>
> Regards,
> Marc
>
>
> PS: The reason because this did not happen on servers running on Samba 3
was that SMB2 was not enabled by default before Samba 4.x.
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba