Re: [Samba] Samba 4 Client Directory Contents Refresh
- Date: Fri, 19 Jan 2018 00:22:09 +0100
- From: Marc Muehlfeld via samba <samba@xxxxxxxxxxxxxxx>
- Subject: Re: [Samba] Samba 4 Client Directory Contents Refresh
Am 18.01.2018 um 20:43 schrieb rcone via samba:
> 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).
Simply create a reg file with these 3 settings and import them once as
local administrator on each machine. If there are to many clients in
your network, you should really consider a central solution for
deploying settings, such as Group Policies on Samba AD.
> 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.
As I said, this behavior is expected and part of the SMB2 protocol. You
will see the same if you run Windows Sever 2008 or later, which also use
SMB2 or a never protocol version.
RHEL5 contained Samba 3.0.33, which is EOL since 2009. This Samba
version only supported SMB1. That's why your clients did not show this
behavior. If you use a recent Samba version, all SMB versions are
enabled by default.
What you can (but really should not!) do is to set in [global]:
> server max protocol = NT1
This forces the server to provide only SMB1. However, you really don't
want to do this! I guarantee that you will run into other problems in
future. E. g. MS disabled SMB1 in Windows 10 1709 and maybe a future
update will do the same on Win 7 / 8.1. Additionally, newer SMB versions
provide a lot of improvements.
If you want to disable the caching behavior, disable it on the client
(via reg file or using a central deployment) and do not force clients to
use legacy SMB1 only.
To unsubscribe from this list go to the following URL and read the