[107] in Back_Bay_LISA
Re: Lanalyzers, network diagnostic tools
daemon@ATHENA.MIT.EDU (Tom Fitzgerald)
Thu Dec 3 18:27:51 1992
From: Tom Fitzgerald <fitz@wang.com>
To: asonnenb@sentry.foxboro.com (Alan Sonnenberg)
Date: Thu, 3 Dec 92 17:47:39 EST
Cc: bblisa@inset.com
In-Reply-To: <9212032143.AA04229@iasun>; from "Alan Sonnenberg" at Dec 3, 92 4:43 pm
> Do any of you have any favorite protocol analyzers??
>
> I have seen the "sniffer" (thought it was costly), I have BRIEFLY
> seen Metrix which runs on a Sparc portable.
The sniffer is definitely expensive, but it's worth it. I haven't used
the HP, but I'd recommend the sniffer over the LANalyzer or ftp's LANWatch.
The two things I'd wish for in the sniffer are 1) ping and outgoing telnet
options, and 2) an external switch or software switch to select between the
thinnet and AUI connectors.
Does anyone use the sniffer's expert-system stuff? It seemed like a great
idea when we heard about it, but I hardly ever use it. By the time you
learn enough about the protocols to understand the expert-system
diagnostics, you already know how to see the problem in the packet stream.
--
Tom Fitzgerald Wang Labs fitz@wang.com "I went to the universe today;
1-508-967-5278 Lowell MA, USA It was closed...."
--
Mail for the `bblisa' list goes to `bblisa@inset.com'.
ONLY mailing list requests go to `bblisa-request@inset.com'!
bblisa administration messages go to `bblisa-admin@inset.com'.
