home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Current Shareware 1994 January
/
SHAR194.ISO
/
networks
/
nrdiag.zip
/
NRDIAG.DOC
next >
Wrap
Text File
|
1993-08-27
|
5KB
|
99 lines
Using the NRDIAG Diagnostics Utility
--------------------------------------
(C) Copyright 1993 Artisoft, Inc.
(Edition 1)
ABOUT NRDIAG
============
NRDIAG is the NodeRunner Micro Channel diagnostic program. This
utility is also included as part of the NRSETUP program as the option
titled "NodeRunner Diagnostics." With NRDIAG, you can check for
problems with your adapter or network connections. NRDIAG tests network
communications at the hardware level (adapters, cables, T-connectors,
etc.). This allows you to isolate the hardware from the software for
more precise network diagnostics.
Run NRDIAG after installing the adapter in the computer, but BEFORE
running the network software.
NOTE: Make sure no NodeRunner adapter drivers are loaded into memory
when you run NRDIAG. If you are using DOS V5.0, you can do this
by typing MEM/C at the DOS prompt and viewing the list of
programs loaded. If the NodeRunner driver is running, exit any
applications, power down your PC, restart the PC and do not let
the NodeRunner drivers run from your startup batch file.
1. When you are sure that the network drivers are not running, insert
your NodeRunner adapter diskette into a disk drive on your computer.
2. For NodeRunner ISA adapters, type NRSETUP from the drive letter in
which you installed the NodeRunner SI adapter diskette and then choose
NodeRunner Diagnostics from the menu that appears. For NodeRunner
Micro Channel adapters, type NRDIAG. For example:
B:NRSETUP (For NodeRunner ISA adapters)
B:NRDIAG (For NodeRunner Microchannel adapters)
3. At the prompt, type in a name for the computer you are testing. The
name must be unique on the network. If you are testing many
computers, keep a list of each computer's name for future reference.
4. Repeat steps 1 - 3 on all computers to be tested in your network. Be
certain to give each computer a unique name.
5. When NRDIAG is running on all of the computers whose adapters and
connections you want to test, make the following checks:
o Be certain that all of the computers you are testing show up in
the window on the right side of NRDIAG's screen with the name
you assigned them in step 3. If a computer is running NRDIAG
but its name does not appear in this window, check all adapter
and cable connections for that computer. Also check the cables
going to and from that computer.
o Check the following fields in the NodeRunner Statistics window
on each computer you are testing:
Good Transmits: The number of successful transmissions
by this adapter.
Good Receives: The number of data packets successfully
received. A low number in this field
usually indicates bad cables or
connections.
Collisions: These occur when two or more computers
attempt to access the network
simultaneously. Generally you will see
some collisions during regular network
use, but an unusually high number of
collisions can indicate cable problems.
Transmit errors: The number of unsuccessful transmissions. A
high number in this field usually
indicates a faulty cable or adapter.
Receive errors: The number of unsuccessful receives. A
high number in this field usually
indicates a faulty cable or adapter.
Buffer overruns: The number of times the computer's buffers
have been exhausted. A high number in
this field usually indicates especially
heavy network traffic from a source other
than NRDIAG.
Compare the figures in the NodeRunner Statistics window on each
computer you are testing. If any of the fields on a computer show a
significantly different value than is displayed on the other
computers in the network, there may be a problem with the adapter,
the cable or their connections at that computer.
Note: If one of your computers displays values in the NodeRunner
Statistics window that are approximately twice as high as the
values on other computers in the network, it is possible that
you have given two computers the same name. Be certain that
each computer has a unique name before assuming that there is a
problem with the hardware.
o The Diagnostic Results window gives you a report of all the
diagnostic tests performed on your adapter.