

		  	  IN CASE OF TROUBLE

    Essentially there are two classes of errors that can occur in
when setting up PCroute.  In the first class, PCroute seems to boot
properly, but does not respond to 'pings' from a host connected to
a LOCAL network.  If this is the case first make sure of the following

---------------------------------------------------------------------------

If PCroute does NOT respond to pings on either of the local networks.

	1) The WD8003 boards have base I/O address of 280H (interface 1) 
	   and 2A0 (interface 2)

	2) Each interface is connected to the proper network (it is very 
	   easy to get them backwards) and the cabling to each network is
	   well connected.

	3) Make sure that the ethernet boards are jumpered for the 
	   correct type of Ethernet (Thin or Thick)
	4) The IP address of each interface (set with config) is correct.

If all of these quick checks does not turn up an obvious error there is
a program called pctst on the pcroute disk that may help locate the problem.
To use pctst, however, the pcrouter PC must have a monitor and keyboard.  
To use pctst simply invoke it instead of pcroute.  Pctst will then print
out the configuration data that pcroute would have used.  In addition
pctst will print out the Ethernet address of each interface board.  Finally
pcroute will print out the first 32 bytes of any broadcast packet that it 
receives from the network.  After you have invoked pctst 

	1) Check that the configuration data that pctst prints (in hex)
	   is correct.  If not use config to correct it.

	2) Check that the ethernet addresses are 'reasonable' (they should
	   probably begin with 00 00 C0).  If not, this means that that
	   particular ethernet board is either bad or does not have its
	   I/O base address adjusted properly.  Recheck the I/O base address.

	3) If you did not find an error in step 1 or 2, while pctst is
	   running log on to a host on the local network and try TELNETing
	   to a non-existent host on the LOCAL network.  This will generate
	   broadcasts on the local network which pctst should print.  If
	   not either the board is bad, it is not configured for the 
	   correct type of network (thin or thick ethernet) or network
	   cabling is loose.

	4) repeat procedure 3 on the other side of the router to test the
 	   other network board.

---------------------------------------------------------------------------

If PCroute does respond to pings on both of the local networks, but 
does not route properly.

	This is almost certainly a routing problem.  Use config to
	verify that the routes for PCroute are correct.  Also make
	sure that the hosts on each of the local networks have the
	proper routes installed.  (remember that not only does the 
	pinging host have to know to route through PCroute, but also
	the pinged hosts has to know how to route back).
