系统运维

I had exactly the same issue but with Samba 4 exports and Windows 7 clients. It is definitely client side error. After some thorough troubleshooting, I simply added the registry key and it worked like a charm after hitting the F5 button once.

晋安网站制作公司哪家好，找创新互联公司！从网页设计、网站建设、微信开发、APP开发、成都响应式网站建设公司等网站项目制作，到程序开发，运营维护。创新互联公司自2013年起到现在10年的时间，我们拥有了丰富的建站经验和运维经验，来保证我们的工作的顺利进行。专注于网站建设就选创新互联公司。

Only had to add this registry key:

DirectoryCacheLifetime[DWORD] = 0

HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\Lanmanworkstation\\Parameters

The values mentioned in this article seem to be invalid, as these registry values no longer exist. I believe that the default expiry time for the cache is 10 minutes rather than 10 seconds. http://technet.microsoft.com/en-us/library/ff686200%28v=ws.10%29.aspx

UPDATE(20/04/2015)

If you are interested in applying this on server side without the need to configure the clients you must add the following line in the [global] section within smb.conf:

server max protocol = SMB2_02

This will limit the server down to protocol SMB2 rather than the default SMB3 which comes with Samba 4 but it compromises the transfer speed. I believe that protocol SMB2_02 is an early version of SMB2 which doesn\'t support caching, so it should work in this case.

However I noticed that a few clients were still experiencing caching issues and had to manually change registry as described above.

Unfortunately there isn\'t much documentation about the various SMB protocol versions. Here is what the man page for smb.conf says about this:

新闻标题：共享文件更新延迟
新闻来源：http://lszwz.com/article/chdpcp.html