Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!rutgers!njin!khnphwzhn.njin.net!rapatel From: rapatel@khnphwzhn.njin.net ( Rakesh Patel) Newsgroups: comp.protocols.appletalk Subject: Re: CAP.Etalk Message-ID: Date: 17 Aug 90 18:50:11 GMT References: Organization: Rutgers Univ., New Brunswick, N.J. Lines: 19 Woops, I hadn't read your message carefully. No, the cap.etalk distribution does not talk both IPtalk and Ethertalk simultaneously. The cap.etalk distribution only uses EtherTalk by being "bridged" through UAB. If you have Ethertalk enabled on the Gatorbox, you will be able to see that network using atlook by sepcifying the appropriate zone name. The Gatorbox will be bridging the IPTalk and Ethertalk. If you have the Sun running CAP on the same ethernet as the Macintoshes and Gatorbox, you can run the cap.etalk distribution and use UAB to have it use Ethertalk. Then the Macintoshes can communicate directly with the CAP services. If you enable Ethertalk support on the Gatorbox, then it will bridge the localtalk devices/services to the Ethertalk devices/services (Macs on Ethernet and Ethertalk version of CAP). See the other followup message I sent on information about the problem you have running it. I also mentioned in the other message that the Rutgers cap/cap.etalk distributions will be replaced with on Rutgers cap distribution that will allow configuration for either Ethertalk or IPtalk (not both simultaneously). Rakesh Patel.