home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware 1 2 the Maxx
/
sw_1.zip
/
sw_1
/
LAN
/
PCRTE223.ZIP
/
trouble.doc
< prev
next >
Wrap
Text File
|
1992-01-17
|
5KB
|
102 lines
IN CASE OF TROUBLE
Here is a list of common problems and their solutions as well as some
very useful debugging techniques. Using these techniques should enable you
to find most problems. Please let me know if this guide is insufficient.
In general there are three sources of good information for debugging PCroute
they are.
PCROUTE.LOG - This file is created and written to when PCroute
first starts up. PCroute writes out all its
configuration data to insure that is it what you
think it is, and to make sure the hardware is
working properly.
Logging host - Once PCroute boots up, it sends diagnostic information
to the logging host. This is useful for debugging
dynamic problems.
3rd Party - Much information can be gained by using PING
(either to or though the router) traceroute (if you
have it) and examine the routing tables (for
RIP problems).
----------------------------------------------------------------------------
PROBLEM: Can't PING PCroute from either local net (PCroute seems dead).
The first thing to check is the PCROUTE.LOG file on the floppy.
PCROUTE.LOG does not exist
Make sure the floppy is not write protected.
Make sure the floppy is bootable and that PCroute
is run in the autoexec file.
If necessary install a monitor and check the boot sequence
If PCROUTE.LOG says the configuration file is corrupt, you must
rerun config.exe. If that does not work make sure you are
using the config.exe that came with the version of PCroute that
you are running. If that does not work, delete PCROUTE.CFG
and rerun config.exe from scratch.
Check the ethernet addresses in the PCROUTE.LOG file. If any
are FFFFFFFFF, that means the card does not have the I/O
address set properly, and the software cannot find the card.
Check that the IP addresses in PCROUTE.LOG are correct. Remember
for the precompiled PCroute.exe interface 1 is the card with
I/O address 280H, and interface 2 is the card with I/O
address 2A0H. Make sure they are not mixed up.
Check the ethernet card to make sure it is set for the correct
type of ethernet (THIN or THICK)
Check the cabling to the ethernet.
----------------------------------------------------------------------------
PROBLEM: The network comes to a halt when PCroute is brought up
This symptom indicates a broadcast storm. This is caused not by
PCroute but by some other (OLD) IP host. Try turning off directed
broadcasts on all interfaces of PCroute (Bit 3 of the interface flags)
This usually stops the problem, but the real solution is to update
all old networking software.
----------------------------------------------------------------------------
PROBLEM: PCroute can be pinged, but no messages are received by the
logging host.
Check PCROUTE.LOG to make sure that the logging host IP address is
correct.
Try Pinging PCroute from the logging host, if you cannot there is
a routing problem (see below). If possible, choose a logging
host that is on a local network.
Maybe you simply filtered out all of the messages, so that PCroute
SHOULD send nothing. Good production settings for the filter
parameters are (mask 0, priority 7), for debugging you should
use (mask 0, priority 8) and if you set it to (mask 0 priority 9)
PCroute will send 'I'M ALIVE' messages every minute.
Make sure that the /etc/syslog.conf file is set up properly it should
be listening for logging messages from facility 'local0' and
priority 'debug' (everything).
----------------------------------------------------------------------------
PROBLEM: PCroute can be pinged from a local net, but not a remote net.
This is either a a routing problem or a subnetting problem, to
test if it is a subnet problem, ping a host OUTSIDE your subnet
from a host that must route through PCroute to get there. In the
example, pinging any host that does NOT begin with 129.105 from
a host on net A will do the job. If this ping succeeds, the subnetting
mask is wrong and needs to be changed.
If it is a routing problem, try inserting a static route, it that solves
the problem, make sure that the other gateways are broadcasting
RIP properly.