Azure Hybrid & Cloud Migration Blog

Article by: Zahir Hussain Shah | MVP Exchange Server, CISSP

Recently, we ran into a situation, where we figured out that our Windows Server 2008 SP2 based File Server is behaving quite slow, and Windows XP plus Windows 7 users are complaining like hell about its performance for opening, coping and editing files on the File Server over the Network link, so we started identifying the root-cause of the problem, and we saw in the resource monitor that the network usage is seems quite high, but there was nothing we did something for the Network itself, but rather we got to know about the KB, which fixes our problem for the File Server slow response over the network.

Problem:
Windows Server 2008 File Server slow response for copying, editing, and uploading files over the network.

Cause:
This issue occurs because of the file control block (FCB) resource being locked unexpectedly before the client sends the CreateFile and QueryInformation requests to the server. Therefore, the client cannot handle the Oplock break notification request that is returned by the server. This behavior causes Windows redirector to temporarily stop responding.

Resolution:
Install this KB on the file server and the clients to fix this slow response over the network copying and editing of the files on the Windows Server 2008 File Server.

To know more about the KB, open the KB link from here.

Cheers!