Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!usc!ucsd!ucbvax!VAX.FTP.COM!jbvb
From: jbvb@VAX.FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Is FTP SW's LANWatch good?
Message-ID: <9006281604.AA18709@vax.ftp.com>
Date: 28 Jun 90 16:04:30 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: jbvb@vax.ftp.com
Organization: The Internet
Lines: 20

"Debug sick segments" is a little ambiguous.

If your problem is broadcast storms, or "two hosts with the same IP
address", or "why do I get 'can't route' messages", or "my Foo can't
ftp to his Bar, but Telnet works fine" the absence of special
hardware won't hinder you.

If your problems are in the cabling or the interfaces themselves,
like "some pairs of nodes can't talk to each other, but other
pairings work fine", then we can tell you that the transmitted
packets are properly formed, or that there is a CRC error at time X -
you have to make the corellation that this is when 'such-and-such'
tries to send.  We don't detect jabber or the like.  A Sniffer or a
LANAlyzer or a SpiderMonitor can probably tell you more about this
sort of thing.  However, from what I see on the net, some people
prefer either a dedicated TDR (one guy insists on an analog display),
or the HP product (LAN Probe?) for hardware issues.

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901