Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!CCNUCD.DENVER.COLORADO.EDU!PKLAMMER%cudnvr
From: PKLAMMER%cudnvr@CCNUCD.DENVER.COLORADO.EDU (Pete Klammer 303/556-3915)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Is FTP SW's LANWatch good?
Message-ID: <9006280028.AA19125@ccnucd.Denver.Colorado.EDU>
Date: 28 Jun 90 00:25:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 14

We have an opportunity to procure a LAN analyzer.  We budgeted
$15,000, but now there is pressure to divert some of this amount to
more visible direct user benefits...  So now we're trying to strike a
compromise on a portable '386sx, with LANWatch from FTP Software.
Please comment if you have some relevant experience: would an old
luggable 8088 or 8086-based machine be adequate or is the 386sx very
beneficial?  Is this software/ethercard/PC system going to help us
debug sick ether segments or should we hold out (or wait) for the
high-priced dedicated hardware solution.  Thanks for the help.

/** --poko	"Please note the new ZIP+4; old addressing MAY be forwarded."
Pete Klammer (303)556-3915 FAX(303)556-4822 |pklammer@pikes.denver.colorado.edu
CU-Denver Computing Services Campus Box 169 |bitnet: PKLAMMER@CUDENVER
1200 Larimer St NC2506 Denver CO 80217-3364 |uu:!boulder!pikes!pklammer     **/