locked
Files Delay in Showing in Network Share RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    2
    Sign in to vote

    So here is my issue.  I have users running Win 7 and Win XP saving files to a Windows 2008 SP2 file server.  We have been having sporatic issues with files taking 10-15 mins to show in the shares.  While the file is "missing", if you would go directly to the file server via RDP or server console, the file is physically there.  Now, through testing i have found that just a simple refresh of the screen doesn't work.  Browsing to the share via UNC or mapped folder doesn't matter.  The only way to get the file to appear earlier is if from the computer where the file is "missing" you create a new file, or folder, and then refresh the folder, then the file appears.  I have also checked via the command prompt, while the file is "missing" from explorer, it is missing from the comand prompt too.  My end users have been telling me about this for about a month and until tonight, after i have spent about 3 hours troubleshooting, i thought it was end user error.  From what i can tell, this is an actuall issue with the file sever.  See if perform this same procedure, but use a network share on a different server, the files never go "missing".  Its only when you save to our Windows 2008 SP2 file server, and it doesn't matter what share you save it to, or what user you look at the server with.  I have even been able to replicate this issue with a domain admin account.  I am at witts end here, any help would be appreciated.

    Thursday, February 9, 2012 2:11 AM

Answers

  • Question
    Sign in to vote
    8
    Sign in to vote

    Okay, problem fixed with the help of MS support.  It is an SMB2.0 issue it appears.  But disabling it, isn't the right call.  You need to add some registry keys to force SMB2.0 to refresh the screen quicker.  Here are the keys:

    *as always, edit the registry at your own risk*


    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation\Parameters



    1.Directory cache, by setting "DirectoryCacheLifetime" to ZERO.


    2.File Not Found cache, by setting "FileNotFoundCacheLifetime" to ZERO.


    3.File information cache, by setting "FileInfoCacheLifetime" to ZERO.

    After adding these entries, reboot the machine and try again.  I did this to any client machine that was having issues viewing the network share.  I didn't do this to the File server itself.

    Hope this can help anyone else that runs into this very obscure issue.

    • Marked as answer by ZDundore Thursday, February 9, 2012 9:22 PM
    Thursday, February 9, 2012 9:22 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    I know this is a very strange issue.  I will be contacting MS support today to see if they can help.
    Thursday, February 9, 2012 1:44 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Here a very simmilar case to yours, also without solution:

    http://community.spiceworks.com/topic/156064-network-share-files-take-a-long-time-to-appear-for-others

    Hints:

    Besides this, nothing came to mind. The problem is with 7 and XP clients?

    If you find this post Helpful, please Vote as Helpful. If this post solved your problem, please mark it as an Answer.

    Thank you,

    F. Schubert
    System Administrator

    MCP | Microsoft Certified Professional
    MCTS 70-640 | Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    MCTS 70-642 | Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Thursday, February 9, 2012 1:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Its just with Windows 7 Clients and Windows 2008 servers.  As an interesting side note, i too have Vipre antivirus running on these problematic Machines.  I will start by uninstalling the AV from these machines and testing from there.
    Thursday, February 9, 2012 3:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This is very interesting, I suggest the same as you both share a common possible root cause. Please share the results.

    Thank you,

    F. Schubert
    System Administrator

    MCP | Microsoft Certified Professional
    MCTS 70-640 | Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    MCTS 70-642 | Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Thursday, February 9, 2012 6:57 PM
  • Question
    Sign in to vote
    8
    Sign in to vote

    Okay, problem fixed with the help of MS support.  It is an SMB2.0 issue it appears.  But disabling it, isn't the right call.  You need to add some registry keys to force SMB2.0 to refresh the screen quicker.  Here are the keys:

    *as always, edit the registry at your own risk*


    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation\Parameters



    1.Directory cache, by setting "DirectoryCacheLifetime" to ZERO.


    2.File Not Found cache, by setting "FileNotFoundCacheLifetime" to ZERO.


    3.File information cache, by setting "FileInfoCacheLifetime" to ZERO.

    After adding these entries, reboot the machine and try again.  I did this to any client machine that was having issues viewing the network share.  I didn't do this to the File server itself.

    Hope this can help anyone else that runs into this very obscure issue.

    • Marked as answer by ZDundore Thursday, February 9, 2012 9:22 PM
    Thursday, February 9, 2012 9:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi ZDundore! Thanks for your help!

    Can you give more details?

    I mean, wich kind of keys ? Dword 32? Qword 64? Sting? Binary? It´s the same for 32 or 64 bits? Professional or Ultimate Windows 7? Service Pack?

    Those keys that you add, are provided by some at MS Helpdesk? or are made by you?

    Thanks again!

    Axel

    Tuesday, July 7, 2015 3:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This link explains the DWord registry entries in question.

    https://technet.microsoft.com/en-us/library/ff686200%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

    Since it affects performance, I'm setting them to 1 before trying 0.

    Thursday, January 14, 2016 12:55 PM