Path: utzoo!attcan!uunet!samsung!usc!elroy.jpl.nasa.gov!ames!dftsrv!palantir.gsfc.nasa.gov!rdominy From: rdominy@palantir.gsfc.nasa.gov (Robert Dominy) Newsgroups: comp.sys.mac.programmer Subject: Re: EtherTalk Question Message-ID: <831@dftsrv.gsfc.nasa.gov> Date: 8 Feb 90 20:09:20 GMT References: <19790@bellcore.bellcore.com> Sender: news@dftsrv.gsfc.nasa.gov Organization: NASA Goddard Space Flight Center Lines: 39 In article <19790@bellcore.bellcore.com> sdh@flash.bellcore.com (Stephen D Hawley) writes: > I have a front end interface to a mainframe that currently communicates > via the serial port. My superiors have asked if I could possibly speed up > the communications by using ethernet. Fine. I have an Apple EtherTalk > installed (Using V 1.0 since 2.0 doesn't work with our internet), and can > access all the nice dandy laser printers on our network. > > This is not what I want. Since I'm on an ethernet with billions and > billions of other machines (most of which are suns, decstations, and the like) Just being attached to an Ethernet doesn't mean anything. You have to understand what protocols the machines you want to connect to are using. Once you've done this there are a number of commercial and free products available to "speak" the protocol and do the functions you want. The only software that comes with the EtherTalk card is the driver for the AppleTalk (EtherTalk) protocol. > So. How do I do this? NCSA telnet does not work, so this is clearly of no > help in terms of looking for source. For example NSCA Telnet does TCP/IP, terminal emulation, and file transfer. If your computers use TCP/IP (and most UNIX workstations do) then NCSA Telnet WILL work for you (you do have to set up some Telnet parameters, but this is in the Telnet manual). > As a minor flame, I am rather disturbed by the almost complete lack of any > kind of technical information in the manual for the card. Call me Technical documentation IS available. However, for the vast majority of users who just want to print to their LaserWriter, such documentation is hardly needed. I suppose you're in the camp that expects Apple to provide the Inside Macintosh & electrical schematics with every Mac! ------------------------------- Robert Dominy NASA Goddard Space Flight Center