Xref: utzoo comp.dcom.lans:7610 comp.protocols.tcp-ip:15450
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!haven!mimsy!oasys!relay.nswc.navy.mil!relay.nswc.navy.mil!snorthc
From: snorthc@relay.nswc.navy.mil (Stephen Northcutt)
Newsgroups: comp.dcom.lans,comp.protocols.tcp-ip
Subject: Re: Looking for comments on network analyzers
Message-ID: <1991Mar29.142947.2180@relay.nswc.navy.mil>
Date: 29 Mar 91 14:29:47 GMT
References: <5336.27f1d691@cpva.saic.com>
Sender: news@relay.nswc.navy.mil (0000-Admin(0000))
Reply-To: snorthc@relay.nswc.navy.mil (Stephen Northcutt)
Organization: Naval Surface Warfare Center
Lines: 22

Mark Jenkins, SAIC  writes:
>We have been evaluating network analyzers.  The list has been narrowed to the
>Network General Sniffer, Micro Technologies LANager, and the Novell LANalyzer.
>Our prime protocol requirements are TCP/IP, DECnet, and Appletalk, with
Novell,
>NFS,  and OSI to follow at some point in the future. 

We have two of the three you listed, HPs and several others you didn't.
They all work.  For what its worth I kinda like FTP SW's LANWatch product,
because it is so convienient, many times, I happen to be on the
same subnet as the problem, so all I have to do is turn on my PC.
The price is also a factor in LANWatches favor.

In conjuction with a piece of simtel-ware called robo-key, we have
been able to use lan watch to collect data on far flung subnets,
then use ftp sw's rcp/rsh to beam the data up to a unix system for
awk processing; works pretty durn well.
===================================================================
Stephen Northcutt (snorthc@relay.nswc.navy.mil)     News Admin
Work: (703) 663-7745                                High Speed Nets 
Home: (703) 371-4184                                Local GOSIP guru 
Paper Mail: Code E41, NSWC, Dahlgren VA 22448       Parallel Research