We have two PP-200/128MB NT4 machines.  The ADSM server is running
fine, TCP/IP, ADSM Version 3 server and client.  A fileserver running
a ADSM V3 client seems to stop fileserving when the backup client
is pumping data out the pipe.  It's a 100Mb pipe (NT seems not to be
able to drive much traffic over it, anyway using TCP/IP, though) but
it's getting 500KB+ for most of the transfer.

When fileserving stops, clients on the domain freeze when accessing
the fileserver, kill ADSM and the problem goes away.

Is NT so primitive that it can't scratch and chew gum at the
same time?

Is ADSM on NT such a hog that it takes over a machine even though all
the related resource allocation dials have been screwed down tight?

I've read the the NT TCP/IP stack is one of the suckiest implementations
of TCP/IP on earth, does this mean we are doomed until micro$oft decides
to do something about this?

Our UNIX client(s) do not seem to have this problem, nor does the
ADSM server running on NT seem to have any performance problems.  It's
just the ADSM NT client that has the problem.
-------------------------------------------------------------------
Mitch Sako                            Phone:     650.508.6761
Mitch Sako                            Phone:     650.508.6761
Cellnet Data Systems                  FAX:       650.508.6700
125 Shoreway Road                     Pager:     408.989.3365
San Carlos, CA 94070                  E-Mail:    mitch AT cellnet DOT com
                                      Personal:  msako AT netcom DOT com