From: Ben Schmidt <bschmidt@bnr.ca (Ben Schmidt)>
Subject: Re: MacTCP & ARA ?
X-Xxdate: Fri, 14 Aug 92 23:52:30 GMT
Organization: Bell-Northern Research
X-Useragent: Nuntius v1.1.1d7
Date: Fri, 14 Aug 1992 22:52:32 GMT

Subject: MacTCP & ARA ?
From: Jamey Maze, jnm@tdum.CTD.ORNL.GOV
Date: Fri, 7 Aug 1992 21:02:26 GMT
In article <1992Aug7.210226.25241@ornl.gov> Jamey Maze,
jnm@tdum.CTD.ORNL.GOV writes:
>I setup an ARA test with one PowerBook dialing into another. This first
>PB had no network connections; the second was connected to a LocalTalk,
>which was connected to the company internet via a Fastpath. AppleTalk
>stuff worked lovely! So I proceeded to try MacTCP. I manually configured
>an IP address known to the Fastpath in the remote PB, selected Remote
>Only from the Network Control Panel, selected Remote from MacTCP (not
>necessarily in that order), and tried making some connections. The
>problem was when I tried to make a connection and the target host tried
>arp'ing for my hardware address, no one responded. So next, I changed
>the IP address of my remote PB to match that of the PB to which I was
>dialing into. Now the arp's are being answered, but connections were
>still timing out. Can someone tell me how this is supposed to work?
>Ideally, each remote Mac should have its own IP address rather than
>having to set it up to match that of the ARA server (don't you think?).
>
>Thanks!
>
>--
>Jamey Maze                 | Computing & Telecommunications Division
>Oak Ridge National Lab     | Advanced Technology Group
>P.O. Box 2008, MS-6238     | Internet: jnm@ornl.gov 
>Oak Ridge, TN 37831-6238   | 615/574-6355, FAX 615/574-9646 
>
>"The defense of individual rights has reached such extremes as to 
> make society as a whole defenseless against certain individuals.
> It is time, in the West, to defend not so much human rights as
> human obligations." - Aleksandr Solzhenitsyn

Subject: Re: MacTCP & ARA ?
From: Barry Kort, barry@chezmoto.ai.mit.edu
Date: 10 Aug 92 22:02:29 GMT
In article <BARRY.92Aug10180229@chezmoto.ai.mit.edu> Barry Kort,
barry@chezmoto.ai.mit.edu writes:
>If you plan to use MacTCP via ARA, then do not also install MacTCP
>on the machine acting as the ARA Server.  Perhaps in a future
>release it will be possible for both the ARA Server and its ARA
>Clients to run MacTCP, but at present only one of them can be using
>MacTCP.

Huh!? 

Jamey's scenario works fine - with one minor caution. Use "Server"
mode acquisition of IP addresses on the Remote Mac's MacTCP.
(And of course ensure that the FastPath is configured to hand out
at least some of the IP addresses it's administering dynamically.)
Save yourself some aggrevation and don't bother trying to get a static
IP address to work on an ARAP-Remoted Mac.

Once the remote Mac establishes an ARAP connection, open your favourite
MacTCP-based app on the remote Mac. This will cause the Remote Mac's
MacTCP to do an NBP LkUp for IPGATEWAY, find the FastPath, and obtain
a dynamic IP address as per the MacIP protocol.

Whether the answering Mac has MacTCP installed or not is irrelevant.
 
--
Ben Schmidt,P.Eng   Network Applications, Bell-Northern Research
bschmidt@bnr.ca   FAX:613-763-3283  /* My opinions, not BNR's */