467,118 Members | 1,012 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,118 developers. It's quick & easy.

"network BIOS command limit has been reached" error AFTER applying fixes

Hello,

we have this situation.

web farm, several server 2003 machines, and several win2K, SP 4
machines

all machines access files on a Network appliance using CIFS

I am testing a ASP.NET 2.0 project that is residing on the share. I
noticed a random error I was getting on win2K machines

Parser Error Message: An error occurred loading a configuration file:
Failed to start monitoring changes to '\\xxx\yyy because the network
BIOS command limit has been reached. For more information on this
error, please refer to Microsoft knowledge base article 810886.
Hosting on a UNC share is not supported for the Windows XP Platform

I found the microsoft articles realting to this. I noticed and
executed the following:

- my win2K machines had a release late enough to contain all hot
fixes refered to in KB 271148. I verified all DLLs refered in this KB,
and our version is newer

- I added this key to all win2K machines
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\lanmanworkstation
\parameters\MaxCmds = 800 hex-

- rebooted the machines

still I am getting these sporadic errors, again only on the win2K
machines. can anyone help ?

Apr 5 '07 #1
  • viewed: 14998
Share:
1 Reply
On Apr 6, 12:16 am, "yoram.aya...@structuredweb.com"
<yoram.aya...@structuredweb.comwrote:
Hello,

we have this situation.

web farm, several server 2003 machines, and several win2K, SP 4
machines

all machines access files on a Network appliance using CIFS

I am testing a ASP.NET 2.0 project that is residing on the share. I
noticed a random error I was getting on win2K machines

Parser Error Message: An error occurred loading a configuration file:
Failed to start monitoring changes to '\\xxx\yyy because the network
BIOS command limit has been reached. For more information on this
error, please refer to Microsoft knowledge base article 810886.
Hosting on a UNC share is not supported for the Windows XP Platform

I found the microsoft articles realting to this. I noticed and
executed the following:

- my win2K machines had a release late enough to contain all hot
fixes refered to in KB 271148. I verified all DLLs refered in this KB,
and our version is newer

- I added this key to all win2K machines
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\lanmanworkstation
\parameters\MaxCmds = 800 hex-

- rebooted the machines

still I am getting these sporadic errors, again only on the win2K
machines. can anyone help ?
Look at this KB article
http://support.microsoft.com/kb/810886

It required changes in Services\lanmanworkstation and Services
\lanmanserver keys.

Note: The MaxCmds and MaxMpxCt registry entries are REG_DWORD decimal
entries. If they do not exist on your computer, you can create them as
new REG_DWORD values. The range of values for these registry entries
is between 0 and 65535. But be aware of the pitfalls with a maximum
value

http://weblogs.asp.net/hosterposter/...er-errors.aspx

Hope it helps

Apr 6 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

5 posts views Thread by Jeremy | last post: by
2 posts views Thread by John Baker | last post: by
14 posts views Thread by David W. Fenton | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.