Brett,

Thanks for the suggestion.  However, this Mac's TCP/IP stack is
communicating via TokenRing (16 Mbs) adapter.

Are you the "Brett in client dev" referred to in PMR 25666,302 (which I've
opened for this problem)?

Also, because this is our only TCP/IP application, we'd like to try to
exercise the IP stack using something besides ADSM.  I'm hoping we can
develop a test using FTP.  Do you have any suggestions for an FTP test
which would simulate the way that ADSM works?  Would multiple FTP GETs or
PUTs be a good simulation; I might even be able to come up with a single
large file which could be transmitted to/from the workstation.  Any
suggestions?


To:       ADSM-L @ VM.MARIST.EDU
cc:        (bcc: Dennis Schaffer)
From:     walkerbl @ VNET.IBM.COM
Date:     06/08/97 08:25:38 PM MST
Subject:  Re: Adsm Macintosh Client Backup Failures




You said that ADSM is their only TCP/IP application, that everything else
is AppleTalk.  You might want to double check that TCP/IP is running over
the Ethernet or TokenRing, and not AppleTalk(MacIP).  In general, AppleTalk
is a very slow protocol, and it possible this could be a problem.

Go to the TCPIP Control Panel.  At the top of the Control Panel, there
should be a pull down menu with the label "Connect via:".  This should say
either "Ethernet" or "Token Ring".  If it says "AppleTalk(MacIP)" then try
using straight Ethernet.

Just a thought...

Brett
ADSM Development


o----------------------------------------------------------o
Brett Walker                  ADSM Development, IBM
walkerbl AT vnet.ibm DOT com
--------------------------------------------------------
"That's just my opinion; I could be wrong."
"That's just my opinion; I could be wrong."
      --- Dennis Miller