home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.appletalk
- Path: sparky!uunet!sun-barr!cs.utexas.edu!sdd.hp.com!mips!newsun!cranch
- From: cranch@novell.com (Christopher Ranch)
- Subject: Re: Appletalk Echo Protocol
- Message-ID: <1992Jul21.164928.10374@novell.com>
- Followup-To: comp.protocols.appletalk
- Sender: cranch@novell.com
- Nntp-Posting-Host: na.novell.com
- Organization: Novell Inc., San Jose, Califonia
- References: <01GMLK54DP0G99E685@MARICOPA.EDU>
- Date: Tue, 21 Jul 1992 16:49:28 GMT
- Lines: 32
-
- In article <01GMLK54DP0G99E685@MARICOPA.EDU> KLAASS@PC.BITNET (Steve Klaass) writes:
- >We are trying to put together a series of network routines on a Mac network
- > [...]
- >After considering a few approaches to "pinging" machines to identify whether
- > [...]
- >BUT....
- >
- >After spending the last week poring through everything I could find on the
- >AppleTalk Echo Protocol (I'm a little slow at these things), it seems as if
- >there should be a standard INIT or other resident implementation of EP
- > [...]
-
- Echo is built directly into the Mac's AppleTalk stack. Just
- throw a packet at it from the database machine (your net/your node/
- your socket [>$80]/DDP type=$06[AEP]) to the Mac (Mac's net/Mac's
- node/soecket=$06[Echoer socket]/DDP type=$06[AEP]. You will get
- it thrown back at you.
-
- If you are going to do any statistical analysis of AppleTalk address
- consistency/changes over time, I'd be very interested in seeing it.
-
- >Thanks in advance for any direction,
- >Steve Klaass
- >Network Services
- >Glendale Community College
-
-
- ---
- Chris Ranch
- Internetworking Products Division
- Novell, Inc. San Jose, CA
- (408)473-8667 cranch@novell.com
-