On Windows servers, each connection uses the identity of a unique user to connect to another server by using an SMB (Server Message Block) connection. A connection is used when you open a remote file share in Windows Explorer or via a net use command.
For each connection, there are a number of work items or work contexts used. By default, this limit is set low, and when storing IIS content or configurations on a remote file server, you may run out quickly. This causes the error "The network BIOS command limit has been reached." There may be other errors, such as an ASP.NET or ASP 500 error.
There are registry keys that control how many commands and work items are permitted. On the file server, two registry keys control the number of connections and work items that are allowed.
When using a remote file server for content or configuration files, you must set the registry keys on both the file server if it is running Windows 2003 or lower, and the Web server.
Note: If you are running Windows Server® 2008 on both the Web server and the file server, these registry changes are unnecessary. If they are set, Windows Server 2008 will ignore them.
To configure the registry key on the file server (Windows Server 2003)
- From the command prompt, run regedt32 to open the Registry Editor.
- Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters.
- If it does not exist, create a DWORD "MaxMpxCt" and set the value to 800 hexadecimal. This specifies a value of 2,048 decimal.
- If it does not exist, create a DWORD "MaxWorkItems" and set the value to 2000 hexadecimal. This specifies a value of 8,192 decimal, or 4x the MaxMptCt.
- Reboot the machine.
For information on the length limitation of the pathname of the share (\\server\share) see http://msdn2.microsoft.com/en-us/library/cc246567.aspx
For instructions to configure the Web Server SMB registry keys see: http://www.iis.net/learn/web-hosting/web-server-for-shared-hosting/smb-commands-registry-keys_198