Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!midway!mimsy!mojo!disney!ra.src.umd.edu!jaya
From: jaya@ra.src.umd.edu (Jaya Kanal)
Newsgroups: comp.protocols.appletalk
Subject: MacTCP, Appletalk, and Fastpath 3s
Message-ID: <1990Oct12.134447.29673@ra.src.umd.edu>
Date: 12 Oct 90 13:44:47 GMT
Sender: news@ra.src.umd.edu (The News System)
Organization: Systems Research Center, University of Maryland
Lines: 26

Organization: Systems Research Center, U of MD

Any MacTCP experts out there:

We have recently started using MacTCP and products that use it (Telnet for 
MacTCP, etc.) on some of our Macintoshes.  We have had success with the 
Macs that have an ethernet connection, but no success with the Appletalked 
ones.  We think the problem may be due to our use of (old) fastpath 3s, 
because the 3s do not support ddp-ip routing, I believe.  I got a speedy 
answer from Shiva when I wrote to them about the problem (thanks), and 
they thought that the etalkgw software had some of the ddp-ip capabilities 
that are built into the fastpath 4.  We are using etalkgw, but we are 
having no luck.

In short, many installations must be using MacTCP successfully with 
Appletalked Macs, and I am wondering if anyone knows what might be causing 
our problems.  Basically, our Appletalked Macs are not able to establish a 
connect to our unix hosts when MacTCP is installed (we think we installed 
it correctly).  fyi, "regular" Telnet works fine with these machines.

Any info/advice would be appreciated, thanks.  Please respond to the e-mail address listed below.

**********************************
Jaya Kanal, Systems Research Center
University of Maryland College Park
jaya@ra.src.umd.edu