Hi,

I am currently evaluating the WatchDirectory software and have quite a few tasks set up to make sure this software will do what we need to do before buying a couple of pro licenses.

I have WatchDirectory setup with 17 tasks all monitoring folders on a networked computer.  I currently have 10 of them running and they seem to be working just fine.  However, when I go to start another one, it gives me the below error message and immediately closes.

DMD - Can not monitor directory \\Networked Directory path CD: Error Code: 56
Description: The network BIOS command limit has been reached.

This happens seemingly independent of the order I open them in, so it appears I simply have too many connections open to the networked computer or something.  Is my assesment correct?  Is there a way around this?

Thanks for any help,
Chad

Thanks for the response.  I checked out the article you linked to, but the registry keys mentioned in it do not exist on the three computers (including our Server2003 machine) that we have here, so I couldn't get anything useful out of it.

Do you know of a set max number of connections that Watch Directory can have to a networked computer, or does it change from situation to situation?  I currently have some tasks running with the "fast" monitor method and others using "default" simply because I don't really know the difference and when I wasn't allowed to run any more with fast monitoring, it did seem to allow some with default.

I guess my possible solutions are as follows:

- Put WD on the local computer with the directories to be monitored instead of monitoring over the network.
- Or try to combine tasks so I have fewer tasks running overall.
- Or try running all tasks on default monitoring.

Any other suggestions?

Thanks again,
Chad

I'm actually just trying to use WD to do stuff that Sorenson Squeeze is supposed to do for me.  Because of some odd Squeeze bugs, I'm having to use WD to sort video files into different watch folders for Squeeze to encode.  Then I'm using WD to ftp the output to my Windows Server 2003.

The reason I've kept WD on another computer is because Squeeze is processor intensive and I didn't want anything to interfere with it.  But now that I've run into this problem with connections and WD, I may have to move WD over to the same computer.

While typing this, I've just thought of a simple way to combine a bunch of the tasks I have into one by using the Sort task.  I'll go and try that and see how it works.