Home / Solution / Slow Network Shared Folder Refresh on Windows Server

Slow Network Shared Folder Refresh on Windows Server

Users of certainly one of my buyer continuously complain that newly created recordsdata don’t seem instantly on the community shared folder on Windows Server 2008 R2, however with an extended delay, even when they refresh the share folder contents by urgent F5. Regardless of whether or not a consumer opens the community share utilizing the UNC path or it’s linked as a community mapped drive, new recordsdata and folders after they’ve been copied or created seem solely in 1-2 minutes, not instantly. However, in the event you specify the total identify of the file utilizing its UNC path (lon-file-srv1publicnew_file.docx), it’s going to open, although is not going to be seen within the File Explorer.

Thus, at some moments the listing of recordsdata and folders in the identical community shared folder gained’t match if considered on two totally different computer systems. It must be famous that consumer computer systems are operating Windows 7 because the desktop OS.

Slow shared folder refresh on windows server

The matter is that caching started for use in SMB v2.x for Windows 2008 / Vista (see the ) to cut back visitors and the variety of SMB requests between an SMB consumer and server, and to supply fast entry to community shared recordsdata and folders (it’s fairly efficient when accessing the community shares utilizing a gradual channel or an untenable channel). Thus, Microsoft Redirector element on consumer computer systems makes use of a neighborhood cache containing community share metadata. By default the cache is cleared each 10 seconds.

If you face an issue when new recordsdata are gradual to indicate up in a community shared folder, you may disable metadata caching for SMB v2 on the shoppers.

Tip. Please, notice that computer systems operating Windows eight or Windows 10 are utilizing SMB v2 consumer to entry community shares on Windows Server 2008 R2, although they assist a more recent model of the protocol – SMB v3. To discover the SMB protocol model a consumer is utilizing to work together with a SMB server, run the next PowerShell command:


Get-SmbConnection - get smb version (dialect) used to access share

There are three registry parameters that handle community shares cache settings on the SMB consumer. Microsoft states that the default values of those keys present the perfect efficiency for many environments. The parameters of SMB2 cache settings are positioned within the registry key HKLMSystemCurrentControlSetServicesLanmanWorkstationParameters.

  1. DirectoryCacheLifetime is the lifetime of the shared folder metadata cache (10 seconds by default);
  2. FileNotFoundCacheLifetime is “File not discovered” response cache (5 seconds);
  3. FileInfoCacheLifetime is the time of protecting the cache with the file information (10 seconds).

Thus, the default lifetime of the SMBv2 cache within the community shared folder is 10 seconds. When a consumer updates the contents of the shared folder, the results of the final replace is saved on a consumer for 10 seconds. When accessing this share, all apps are attempting to make use of this cache first.

If you see that new recordsdata should not displayed instantly within the community share, examine the worth of DirectoryCacheLifetime registry key and change it with the smaller worth (or disable it fully).

To disable caching of the SMB folders, create a DWORD parameter with the identify DirectoryCacheLifetime in HKLMSystemCurrentControlSetServicesLanmanWorkstationParameters and alter its worth to zero. Then restart your pc. In the identical approach, you may change the values of FileInfoCacheLifetime and FileNotFoundCacheLifetime parameters to zero.

DirectoryCacheLifetime - smbv2 shared folder cache setting

After that every one adjustments within the community shared folder shall be instantly displayed on a consumer (the contents of the folder is refreshed every time it’s accessed and the native cache will not be used).

Check Also

Fixing Windows Update and DISM Error 0x80073712 on Windows Server 2016/Windows 1…

I confronted an error code 0x80073712 when making an attempt to put in safety updates …

Leave a Reply

Your email address will not be published. Required fields are marked *