Installation guide

5-5
AppleTalk Access Problems
• Access server could not acquire addresses in the network range. If this occurs, the
access server sets the Last Error field in the SHOW APPLETALK STATUS display as
follows:
Attempt to acquire an AppleTalk address for cache failed
Refer to the section Verify AppleTalk Address Is Within the Network Range for reasons
why this can occur.
Verify Access Server Is Visible on the Network
When AppleTalk is enabled, the access server attempts to register its Name (specified by
Name in SHOW SERVER CHARACTERISTICS display) using the Name Binding
Protocol (NBP). This registration occurs when the access server boots or when an
AppleTalk router comes up on a network where no router was previously available (for
example, all routers went down and then came back up). If the access server Name is in
use on the network, the access server falls back to registering its default Name, which is
LAT_"ethernet address". The access server sets the Last Error Field in the SHOW
APPLETALK STATUS display as follows:
Duplicate AppleTalk server name on network - trying
LAT_ethernet
If the access server finds a duplicate name while registering its default name, it leaves its
name registered anyway and displays the following message in the Last Error Field on the
SHOW APPLETALK STATUS display:
Registering duplicate AppleTalk server name on network
Verify Attached Host Software
To create connections, the attached hosts must be running AppleTalk over PPP (ATCP).
Verify this on the attached host.
Verify PPP and ATCP Are Enabled
To determine if PPP is enabled on the access server port, enter the following command.
Substitute the port number for 1:
Local> SHOW PORT 1
If Enabled, PPP is displayed in the list under Enabled Characteristics. For more
information on configuring and managing PPP ports, refer to the Network Access Software
Management Guide.