Article ID: 926646 - View products that this article applies to.
This article discusses a problem that occurs when network users access files on a computer that is running Microsoft Windows XP Professional when the computer is being used as a file server.
By default, there is a restriction that prohibits more than 10 concurrent server message block (SMB) commands in the Windows XP Professional Server service. This restriction also applies to other Windows client computer operating systems. For example, an SMB command occurs when a call is made to open a file. Most SMB commands are processed immediately. For example, the file open command is processed immediately. Therefore, a maximum of 10 concurrent commands is typically not a problem.
However, there are some SMB commands that are named "long-term SMB requests." These long-term SMB requests remain open until they are answered. Typically, after an answer is received, another command of the same type is sent immediately.
Additionally, a long-term SMB request is a change notification. For example, if you open Windows Explorer, and then you click a specific folder on the network, a change notification is sent to the computer that hosts the folder. This occurs whenever something changes in this folder. Then, a change notification is sent back to the client computer so that Windows Explorer can update the window and display the new file. If a computer that is running Windows XP Professional hosts the folder, only 10 SMB commands can be used at the same time. All other requests are not answered. You may also receive an error message when the other requests try to open files over the network.
This problem occurs because of an intentional limitation in the Windows XP Professional Server service. Windows XP Professional is designed as a client computer operating system. Therefore, Windows XP Professional is not optimized for server tasks.
Hotfix informationTo resolve this problem, a hotfix is available that enables you to configure the number of concurrent SMB commands by using the MaxMpxCt registry value. This hotfix enables you to configure the MaxMpxCt value to a maximum of 255. For more information, see the "Registry information" section and the "More Information" section.
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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
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, contact 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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
PrerequisitesYou must install Windows XP Professional Service Pack 2 (SP2) to install this hotfix.
Restart requirementsYou must restart the Server service after you apply this hotfix. If you are prompted, restart the computer after you install the hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
Registry informationImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
To enable this hotfix, follow these steps:
File informationThe English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The actual value of maximum concurrent SMB commands is determined by the minimum of 2 values. These values are the MaxMpxCt value on the server side and the MaxCmds registry value on the client computer. By default, the MaxCmds value is set to 50 in Windows XP Professional. You cannot set this value to more than 65,535.
On the Windows XP computer that is acting as the server, the MaxMpxCt value, the MaxWorkItems value, and the Size value are located in the following registry subkey:
On the Windows XP computer that is acting as the client computer, the MaxCmds value is located in the following registry subkey:
You must set the following registry values on the Windows XP Professional-based computer that is acting as the file server. By doing this, you give the necessary resources to the Server service.
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 926646 - Last Review: October 8, 2011 - Revision: 4.0