System information

Troubleshooting AppleTalk 9-207
ARA: ARA Client Unable to Connect to ARA Server
Note On other media, routes with no zone set are the result of other problems, such as ZIP storms.
See the sections “AppleTalk: Zones Missing from Chooser” and “AppleTalk: Network Services
Intermittently Unavailable” in this chapter for more information.
Table 9-17 outlines the problem that might cause this symptom and describes solutions to that
problem.
Table 9-17 FDDITalk: No Zone Associated with Routes
ARA: ARA Client Unable to Connect to ARA Server
Symptom: An ARA client (such as a Macintosh) attempts to connect to an ARA server (such as a
Cisco access server) and cannot initiate a remote session. The user might be able to connect briefly,
but the connection is immediately terminated.
Table 9-18 outlines the problems that might cause this symptom and describes solutions to those
problems.
Table 9-18 ARA: ARA Client Unable to Connect to ARA Server
Possible Problems Solution
FDDITalk version
mismatch
If any routers in the internetwork are using software releases prior to Cisco IOS Release
10.0, there is a possibility of a FDDITalk version mismatch. Make sure that all routers on the
ring are using either pre-FDDITalk or FDDITalk and not be a combination of the two.
Following are the FDDITalk implementations for each software release:
• In software releases prior to 9.0(2), routers can use only pre-FDDITalk.
• In software releases prior to Cisco IOS Release 10.0, routers use the Apple
implementation of FDDITalk by default.
However, if a pre-FDDITalk router exists on the FDDI network, routers fall back to
pre-FDDITalk. A router can be forced to use FDDITalk with the no appletalk
pre-fdditalk interface configuration command.
• In Cisco IOS Release 10.0 and later, the default is to use the Apple implementation of
FDDITalk.
However, you can force a router to use pre-FDDITalk with the appletalk pre-fdditalk
interface configuration command.