[Samba] Maximum number of LANMAN Work Items and concurrent
connections from IIS 6.0 to Samba
S. J. van Harmelen
sander.vanharmelen at isp.solcon.nl
Sat Jul 1 18:29:59 GMT 2006
Hey there Jeremy,
Thanks for giving me a hand!! Attached is a trace that was running while
I requested IIS for a site (off course the content of the site resides
on the Samba server).
The error "Failed to start monitoring changes to \\server
\websitedirectory... because the network BIOS command limit has been
reached" is generated because ASP.NET wants to monitor the website
directories for file changes using a FileSystemWatcher.
When just a few sites are running, the error doesn't seem to appear. But
when some more sites are requested the error suddenly appears! So this
really look like some kind of limit. The default limit MS is using is
50, but I already changed this to 5000.
There are around 10 sites using ASP.NET, but ASP.NET sets up a
FileSystemWatcher for every subdirectory of every site... So I don't
know exactly what the current limit is...
I hope you (or someone else) can find anything in the trace. If not, I
can also try to make a debug log with debug level 10.
On vr, 2006-06-30 at 09:23 -0700, Jeremy Allison wrote:
> On Thu, Jun 29, 2006 at 05:45:24PM +0200, S. J. van Harmelen wrote:
> > Hey there folks!!
> > I have a question about the maximum number of LANMAN Work Items and
> > concurrent connections from IIS 6.0 to Samba.
> > We have a server for shared windows webhosting running Windows 2003 with
> > IIS 6.0 (with ASP.NET 2.0) connecting to debian 3.1 with Samba 3.0.22
> > (functioning as a fileserver).
> > At this moment there are about 250 sites running on this server. Now
> > when we make a request to site x (which is using ASP.NET 2.0) we get the
> > following error:
> > "Failed to start monitoring changes to \\server\websitedirectory...
> > because the network BIOS command limit has been reached"
> > Now I know there is a registry setting in Windows 2003 that controls
> > these values, but I can't seem to find how to configure this in Samba.
> > As far as I understand, Samba by default is configured for unlimited
> > connections. So what am I missing?
> Yes, there are no hardcoded limits in Samba. Can you post an ethereal
> trace of the connection failure ? Or a smbd debug level 10 log so we
> can work out what might be going on ?
More information about the samba