Re: The network BIOS command limit has been reached
- From: "Bernard Cheah [MVP]" <qbernard@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 21 Dec 2006 15:08:39 +0800
Wow, that's a lot of sessions. I have not encounter this before :)
I would suggest you connect Microsoft PSS if this is urgent, for me I think
a) I think yes, because it needs to be aware of that the remote data is
connected, etc
b) No idea. but my question is how do you setup your ftp to your NAS?
obviously 2k+ sessions is way to high. do you have one virtual directory or
many? I was thinking even if your vendor able to fix it, but I was
wondering why such a high number ?
c) Get Microsoft :)
--
Regards,
Bernard Cheah
http://www.iis.net/
http://www.iis-resources.com/
http://msmvps.com/blogs/bernard/
"Scott" <Scott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:237BE520-0F89-4ED2-BD51-74D4BCD115AC@xxxxxxxxxxxxxxxx
I am experiencing this problem:
http://support.microsoft.com/kb/221790
We have two load-balanced web servers using a NAS unit to store web site
files. Recently I have seen numerous indications in both the event log and
in
the "status" column of IIS ftp node logs that "The network BIOS command
limit
has been reached". The bigger problem that occurs is that I am getting "A
process serving application pool 'xxxx' failed to respond to a ping (Event
ID
1010 in Event viewer). This app pool contains approx 1300 sites and when
the
Event 1010 occurs, none of these sites are available.
A few days ago the problem got so bad that these servers turned into
virtual
vegetables. Not only was ftp not available but the servers were unable to
serve web requests. After booting in safe mode and starting services one
at
a time,w e found that ftp was the problem. As soon as we disabled the
service, IIS would server requests thought he Web Publishing service
without
a hitch. Since then, we have kept ftp off and not experienced any issues.
A
couple of hours ago we turned ftp back on one of these servers and the
same
problem. IIS has appeared to hang at times. the server is running very
sluggish, and I can see the "The network BIOS command limit has been
reached"
in IIS in the ftp sites node.
There are roughly 2100 ftp accounts and upon calling my NAS vendor, it
seems
that our NAS provides 2048 sessions per client. This explains the problem
I
am having, but here is where I need some further info...
When IIS (actually the FTP service) starts, it tries to map to the UNC
path
on the NAS associated the ftp account (BTW, we are using virtual
directories
in the FTP node). Each of these occupies a "session"
indefinitely. When the 2,048 available session limit is reached on our
NAS,
the remaining ftp accounts cannot establish a session and we see the
"network
Bios command.......". Therefore, not only can it not map to all of the UNC
paths, but the Web Publishing Service suffers and eventually hangs thus
prompting the Event 1010 errors (app pool cannot ping the app pool).
Based
on the MS kb article at the top of this posting, it is suggested to modify
the registry on the file server.
Unfortunately, our NAS is not a Microsoft product and is running CFS and I
am awaiting a return call from our NAS vendor to see if this can be
increased
to a number much higher than the 2,048.
Obviously, the best solution is to up the max number of client connections
per/client, but assuming this is not possible, is there anything that can
be
done from the Windows side?
So, here are my questions...
1. Does or does/not the ftp service establish a "session" with the NAS
(network share that the ftp accounts are located on)? Every event I have
seen
says a loud YES and it seems to be the most viable explanation at this
point.
At the same time, I can't understand why the architecture requires a
constant
session to the remote storage unit/file server.
2. Is there any way (via a registry setting or IIS setting) that the FTP
service relinquishes the session so the NAS does not keep an open session?
3. Any other suggestions for workarounds?
.
- Prev by Date: Re: how to list all files found on a web site
- Next by Date: Re: IIS Security Vulnerability
- Previous by thread: Concurrent Logins
- Next by thread: Re: FTP on a different port
- Index(es):
Relevant Pages
|
