When you perform a large amount of network file transfers to a server (enough to cause a reasonable amount of disk stress on the server), one or more instances of the following error message may be displayed in the client event logs: As a result of these redirector timeouts, write operations to the server may be unsuccessful.

Back to the top

Redirector timeout error messages are generic errors that simply indicate that the server was not responding to the client before the redirector timeout period. Although there are many causes of redirector timeout errors, this error message can occur because of a cache manager problem on the server if the following conditions are met:

•	There are an extremely large amount of network file transfers occurring on the server.
•	The server is configured with more than 128 MB of memory.
•	Disk throughput is constrained for some reason (RAID 5).

This cache problem is encountered when you write large files to disk on a computer that has a large amount of memory. In these conditions, if the available bandwidth to the disk is less than what is required by the lazy writer to completely write what it wants in one cycle, the writer may end up holding a lock on file resources for very long periods of time. The server message block (SMB) that initiated the write operation takes too long to complete the operation and the client redirector finally times out.

So far this problem has only been reproduced when you use Windows NT 4.0 clients to connect to a server running Windows 2000. This problem is mostly observed when the server is using either software or hardware RAID that slows down disk throughput such as RAID 5 (striping with parity).

Back to the top

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: Note This is a server-side fix and the service pack should be applied to the servername server referred to in the 3013 error message to address this problem.

Back to the top

Microsoft has confirmed that this is a problem in Windows 2000. This problem was first corrected in Windows 2000 Service Pack 1.

Back to the top

For additional information about other possible causes of 3013 error messages, click the article number below to view the article in the Microsoft Knowledge Base:

Back to the top