Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!bionet!apple!usc!ginosko!uunet!crdgw1!sagittarius!dixon
From: dixon@sagittarius.crd.ge.com (walt dixon)
Newsgroups: comp.sys.mac
Subject: Re: MacTCP
Message-ID: <1994@crdgw1.crd.ge.com>
Date: 30 Aug 89 01:42:53 GMT
References: <698@eplrx7.UUCP>
Sender: news@crdgw1.crd.ge.com
Reply-To: dixon@sagittarius.crd.ge.com (walt dixon)
Organization: General Electric Corp. R&D, Schenectady, NY
Lines: 30

In article <698@eplrx7.UUCP> leipold@eplrx7.UUCP (Walt Leipold) writes:
>I got a beta copy of MacX (Apple's X Windows implementation for the
>Mac OS) a couple of weeks ago, along with MacTCP.  As expected, it
>doesn't work "out of the box" on our system (LocalTalk, Kinetics
>gateway, and EtherNet).  To check out the network hardware, I tried
>NCSA's TelNet -- it ran flawlessly.  Then I tried the MacTCP version
>of TelNet, thinking I'd sneak up on the problem -- it didn't work.
>So my problem seems to be with MacTCP rather than with MacX.
>
>Does anybody out there have any experience with MacTCP?  Is it
>something simple I'm doing wrong?  

I have observed similar symptoms.  We are using LocalTalk for the link
level,  gatewayed to an ethernet backbone through a Kinetics Fastpath 4
gateway.  The ethernet backbone and localtalk are on different ip subnets.
(We are running KStar Version 7 with split addressing).  The Kinetics
box advertises itself as a gateway giving its ethernet side ip address.
MacTCP only talks to gateways in its own ip subnet.  Its not really clear
whether this is a kinetics or apple problem.  I have talked to someone
in the MacTCP development group at apple.  He was very helpful and was
responsible for diagnosing this problem.  I don't know if it has been
solved yet.

Walt Dixon		{internet:	dixon@crd.ge.com	}
			{us mail:	ge crd			}
			{		po box 8		}
			{		schenectady,  ny 12345	}
			{phone:		518-387-5798		}

Walt Dixon dixon@crd.ge.com