>Here's what looks like a basic description of the product from the XP Help:

Whew... quite a story. I think they do tend to make things more complicated. I've seen priority schemes like this back in VAX days, and back then they had stuff which was smart enough to function properly regardless of the relative speeds of the components. And I thought they have the best guys from the VAX team working on NT for years now. Well, those are probably rich enough by now, and sit somewhere far enough from the decision chain.

If I get in touch with my user's network guy, I'll surely mention this to him, and advise him to shut the beast out, we seem to be better off without it. If it sounds like a kludge in the advertisement (i.e. "Enhancements and Behavior" text), I'd better not even try to imagine how it works under the hood.

If, of course, this is what caused the error.