4-2 CHAPTER 4: TROUBLESHOOTING
IP Networks
1 Check to be sure you have your third-party TCP/IP stack installed
correctly. You should be able to ping a known host such as a router or
existing workstation.
2 Be sure the AccessBuilder and the TABM workstation are on the same
subnet. If the AccessBuilder and your TABM workstation are not on the
same subnet, you will need to assign a common SNMP community
name to the AccessBuilder and set up your workstation as the SNMP
community management station (see the TABM on-line help for
further information).
3 Verify that the AccessBuilder has been assigned an IP address. If the
BootP request issued by the new AccessBuilder when it was initially
powered on was not “heard” by TABM, you may need to power-cycle
the new AccessBuilder. Be sure TABM is running before the new
AccessBuilders are brought on-line.
If an AccessBuilder has been discovered (appears on the All Servers list),
but will not communicate when selected, one of the following may
have occurred:
1 The AccessBuilder may have been powered off. Power it on and allow
one to two minutes for the BootP process to complete.
2 The Ethernet connection may have become disconnected or defective.
3 Someone else may have reset the AccessBuilder or altered its
configuration or SNMP community name via a telnet connection.
IPX Networks
1 Check to be sure you have your Novell Windows NetWare client
software installed correctly. You should be able to attach to server on
the network.
2 Check your cabling and connections. Be sure your Ethernet connections
are correct and secure.
3 Make sure there is a NetWare server on the network to which the
AccessBuilder is attached. The AccessBuilder will automatically learn its
address from the NetWare server.
4 Be sure you have assigned a common SNMP community name to the
AccessBuilder and your workstation. The default community name is
abconfig.
ab4kbook Page 2 Thursday, March 27, 1997 11:51 AM
