Trevor,
        A couple of things to check...

1) For an Ethernet environment, set the MTU to 1500 on both the ADSM
client and server.  An MTU of 4000 would work well in other environments
(Token Ring,  possibly FDDI) but not so in the Ethernet world as the
maximum packet size is 1500 bytes.

2) Upgrade to a newest version of the TCPIP on the Netware client....
there are a lot of problems with dropped connections in the older
versions of the TCPIP NLM.

3) Turn off compression, especially if it's an older server (386, 486,
or even an older Pentium).

4) DSM.OPT - Check you TCPIP Buffer and Window sizes on the client, the
defaults have changed at different PTF levels.

5) DSM.OPT - Try specifying the TXNBYTELIMIT for something other than
the default - 25600 is the max but I'd start a little lower (8192,
16384, etc.)

6) On the ADSM server, check the TXNGROUPMAX parameter in the
DSMSERV.OPT file.. this works in conjunction with the TXNBYTELIMIT
parameter on the client.

Tim Pittson
tpittson AT himail.hcc DOT com
>----------
>From:  Trevor Foley[SMTP:Trevor.Foley AT BANKERSTRUST.COM DOT AU]
>Sent:  Thursday, April 03, 1997 1:57 AM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Novell performance and TCP/IP problems
>
>Trevor Foley
>03/04/97 16:57
>From:
>On:
>
>Hi,
>
>I've got a feeling that this has been discussed before, but I couldn't find
>any entries going back through the list for 4 months or so.
>
>We are starting to implement ADSM for our Novell servers. To date we
>haven't had a lot of success. First, some information about our
>environment.
>
>   Server is 2.1.5.12 running on AIX 4.1.4
>   Communcations is entirely TCP/IP
>   The network (for the Novell servers) is 10mbit ethernet
>   Client version is 2.1.0.6
>
>We have two problems:
>
>   We our getting extremely poor performance, in the order of 200mb/hour.
>   As a comparison, we are getting in excess of 1gb/hour from some NT
>   servers (admittedly faster CPU, disks, etc.). We have checked the things
>   mentioned in the Performance Tuning Guide. The only thing that we have
>   changed as a result of that was the TCP/IP MTU size (from 512 to 4000).
>   The MTU was already set in excess of 4000 on the Novell servers. The
>   volumes on these servers have 10-20 thousand files.
>   We are getting a number of TCP/IP failures as show below:
>
>27-03-1997 03:43:45  TcpFlush: Error 60 sending data on Tcp/Ip socket
>39358524.
>27-03-1997 03:43:45  sessSendVerb: Error sending Verb, rc: -50
>27-03-1997 03:43:45  TcpFlush: Error 32 sending data on Tcp/Ip socket
>39358524.
>27-03-1997 03:43:45  TcpFlush: Error 4 sending data on Tcp/Ip socket
>4294967295.
>27-03-1997 03:43:45  sessSendVerb: Error sending Verb, rc: -50
>27-03-1997 03:43:46  ANS4017E Session rejected: TCP/IP connection failure
>27-03-1997 03:43:46  ANS4847E Scheduled event 'BACKUP' failed.  Return code
> = 1.
>
>Any clues?
>
>
>Trevor
>