mjhammel@Kepler.dell.com (Michael J. Hammel) (04/05/91)
I'm running both Netwatch and Netcure (aka the Beholder v0.30) to
monitor traffic on a test network. I've noticed that as long as I don't
start too much traffic (multiple instances of an NFS-based network test
on various systems) both monitors keep up just fine. As soon as the
traffic gets heavy both packages seem to stop seeing packets. The
monitors are still running because the clock displays are running and I
can get help or change windows, etc, in Netcure and get help, quit, etc,
from Netwatch. This leads me to believe the packet drivers stop passing
packets up to the monitors for some reason. Eventually Netwatch will
start seeing packets again, then stop again, then start, and so on.
Netcure has done this too, but not nearly as often (only once that I've seen).
Has anyone seen similar behaviour from these packages or from other
packages using the packet drivers? I'm using the WD8003EB driver under
Netwatch and the 3C503 packet driver for Netcure (both drivers are
version 7.0). Netwatch is running on a Dell System 210 with 4M (a 286
10MHz system) and Netcure is on a 386 20MHz system with 8M. No other
drivers of any kind are loaded.
Michael J. Hammel | mjhammel@{Kepler|socrates|feynman}.dell.com
Dell Computer Corp. | {73377.3467|76424.3024}@compuserve.com
#include <disclaim/std> | zzham@ttuvm1.bitnet
"We choose to do this not because it is easy but because it is hard." J.F.K.