This article has been archived. It is offered "as is" and will no longer be updated.
When you try to connect to network shares that are hosted on a Microsoft Windows 2000-based server, one or more of the following symptoms occur:
The following event appears in the system log on the client computer:
Event ID: 3013 Event Type: Error Event Source: MrxSmb / Rdr Description: The redirector has timed out a request to ComputerName.
You receive an error message that is similar to one of the following messages when you try to connect to a shared resource:
System error 53. The network path was not found.
System error 64. The specified network name is no longer available.
You are intermittently disconnected from network resources, and you cannot reconnect to the network resources on the file server. However, you can ping the server, and you can use a Terminal Services session to connect to the server.
If multiple users try to access Microsoft Office documents on the server, the "File is locked for editing" message does not always appear when the second user opens the file.
A network trace indicates a 30-second to 40-second delay between an SMB Service client command and a response from the file server.
When you view the system event log in Event Viewer on the Windows 2000-based server, you see that the following event has been logged close to the time when a client was not able to connect to a network share:
Event ID: 2022 Source: Srv Description: Server was unable to find a free connection NumberOfTimes times in the last NumberOfSeconds seconds.
If the Windows 2000-based server that is affected is part of a cluster, the server may also report an Event ID 4, an Event ID 1055, and an Event ID 4322, in addition to Event ID 2022 in the system event log.
This problem may occur if server service connections cannot allocate sessions. In this scenario, the problem occurs when the thread that is responsible for allocating and for cleaning up sessions is blocked by a device driver during the cleanup routine.
The hotfix that is described in the "Resolution" section of this article corrects the problem in the case where server service connections cannot allocate sessions. However, there are other potential causes for an Event 2022 to be logged.
For additional information about troubleshooting this problem, click the following article number to view the article in the Microsoft Knowledge Base:
822219 You experience slow file server performance and delays occur when you work with files that are located on a file server
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
No prerequisites are required.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ------------------------------------------------------- 19-May-2003 18:42 5.0.2195.6745 238,032 Srv.sys 19-May-2003 18:42 5.0.2195.6697 83,728 Srvsvc.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New naming schema for Microsoft Windows hotfix packages