![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
NetSight Sentry: Troubleshooting Notes from Tech Support
Contents:
SYSTEM REQUIREMENTS
NetSight Sentry / Professional requires a DOS-based dedicated PC. The
PC must have at least a i386DX processor with 2MB RAM. For best
performance, a 486DX with 8MB RAM is recommended. Here is a sample
CONFIG.SYS and AUTOEXEC.BAT that will yield approximately 620K free
conventional memory:
CONFIG.SYS
DEVICE=C:\DOS\HIMEM.SYS
DOS=HIGH
FILES=20
BUFFERS=20
AUTOEXEC.BAT
@echo off
PROMPT $p$g
SET PATH=C:\DOS
SET TEMP=C:\DOS
CD \NETSIGHT
MENU.EXE
"CAN'T INITIALIZE ADAPTER"
This error usually means that you have a hardware conflict or, more
likely, that you have a "cluttered" CONFIG.SYS and/or AUTOEXEC.BAT.
Typically, files like SMARTDRV, SHARE, or IPX/NETX are being loaded.
None of these will enhance the performance of NetSight, and can only
cause potential conflict. See the sample CONFIG.SYS and AUTOEXEC.BAT.
"UNABLE TO INITIALIZE ADAPTER" OR "CAN'T INITIALIZE PCL2A AT CX000"
The error message in NetSight "Unable to initialize adapter" or "Can't
initialize PCL2A at Cx000" can be caused by a bad board, but is usually
caused by a cluttered CONFIG.SYS or AUTOEXEC.BAT.
Note: EMM386.EXE or SMARTDRV.EXE will almost always cause this error.
Solution:
Clean out your CONFIG.SYS and AUTOEXEC.BAT files, remove any unnecessary
cards (except video and I/O), and reboot. See the sample CONFIG.SYS and
AUTOEXEC.BAT.
"UNABLE TO DOWNLOAD EAGLECAF.OUT"
This error indicates insufficient memory. NetSight Professional
requires about 575K of free base memory.
Solution:
Remove unnecessary TSRs, use MEM/C to verify that your "largest
executable program size" is at least 575K, and reboot.
"UNABLE TO START RECEPTION" OR "LOBE MEDIA TEST; FUNCTION FAILURE"
Symptom:
"Unable to Start Reception" or "Lobe Media Test; Function Failure"
Description:
On a Tokenring, this error usually indicates a hardware problem. Most
often, the cable is not securely attached to the NIC.
Solution:
Verify that the cable is securely attached to the card. Try replacing
the cable with a known good cable. If you are using the RJ45 port, try
using a media filter to go through the DB9 port instead. You can also
try a different port on your Tokenring MAU.
THE NETSIGHT PC CANNOT SEE TRAFFIC ON OTHER SEGMENTS
Symptom:
The NetSIght PC cannot see traffic on other segments.
Description:
The NetSight product is a passive device. In other words, it can
monitor only traffic that physically exists on the wire it's connected
to. All this really means is that NetSight is "segment-based."
Solution:
If you need to monitor multiple segments, you can either buy one copy
for each segment or simply move the NetSight PC from segment to segment,
as needed.
PROTOCOLS SUPPORTED
NetSight Professional supports the following protocols: NetWare
(IPX/SPX), LANMan (NetBIOS), TCP/IP, AppleTalk, DECnet, OSI, SNA, XNS
and Banyan VINES protocols.
Trademark information