We have a fix for that in 5.3D14. The value is set via the cifs.max_mpx option, which has a maximum of 255, same as NT.
Mark Muhlestein -- mmm@netapp.com
-----Original Message----- From: Graham C. Knight [mailto:grahamk@ast.lmco.com] Sent: Wednesday, June 16, 1999 3:12 PM To: toasters@mathworks.com Subject: CIFS and the MaxMpxCt parameter
We have a windows NT terminal server that servers out up to 60 Windows NT sessions at a time. The Windows NT people are complaining because after a certain amount of connections to our filer they start getting errors that look like this:
"\filername is not accessible. The remote procedure call failed and did not execute."
So, they opened a call with Microsoft, and after 3 or 4 days of wrangling Microsoft has told them that the MaxMpxCt needs to be increased on the file server. Well, i can find no reference to this anywhere in NetApp's documentation, so i'm figuring that this is a Windows NT server thing and that it has nothing to do with a filer. But i don't know for sure, or if there is something else i can set that does the same type of thing.
Here's the blurb from M$. Any ideas?
Cause: During negotiation of the SMB dialect, the MaxMpxCt parameter (NT server registry, option in NetApp filer?) is passed to the client's (Terminal Server's) redirector where the limit of outstanding network requests is enforced. Explorer makes extensive use of directory notifications, resulting in a number of NTNotifyDirectoryChange SMBs being sent to the server (NetApp filer). This SMB request is classified as a long term request and is received by the server but not sent back until a change occurs. When several clients connect to the Terminal Server, the number of outstanding commands against the server can exceed the default maximum of 50. If this situation arises, other SMB requests will wait in the redirector until previous requests complete, timeout, or are cancelled.
Resolution: Increase the MaxMpxCt parameter on the remote server to allow more simultaneous SMB connections.
Thanks, Graham