Configuring Your PC Router as an AppleTalk End Node

The Novell Internet Access Server 4.1 routing software allows you to turn off, or disable, AppleTalk routing on a dedicated router or NetWare file server. A NetWare system with AppleTalk routing disabled operates as an AppleTalk end node. If you are using AppleTalk for NetWare only to support applications on a LAN, and you already have another AppleTalk router that provides connectivity to other networks, an end node configuration has the following characteristics:

• An end node does not periodically broadcast routing table maintenance protocol packets. More network bandwidth can be used for data rather than for routing traffic.
• An end node does not require any network number or zone configuration. It assumes the network number and zone from the network to which the AppleTalk interface is connected.

For AppleTalk to support file and print services, NetWare for Macintosh should be installed before Novell Internet Access Server 4.1.

Features such as filtering, WAN support, AURP, and internal network support are available only if AppleTalk for NetWare is configured as a router.

How to Configure Your PC Router as an AppleTalk End Node

To turn off AppleTalk routing and configure AppleTalk as an end node, complete the following steps:

1. Load NIASCFG, then select the following parameter path:

   Select Configure NIAS > Protocols and Routing

2. Configure the LAN board.

   For information about configuring boards, refer to Setting Up in the Boards documentation.

3. Select the following parameter path:

   Select Protocols > AppleTalk > Packet Forwarding > Disabled

   When packet forwarding is disabled, the system does not route AppleTalk packets from one network to another.

   NOTE:  Because all previous AppleTalk bindings will be deleted after changing Packet Forwarding to Disabled , make sure AppleTalk is bound to a network interface. When you configure AppleTalk as an end node, you can bind AppleTalk to only one LAN interface. If you want the application services to be registered in a zone other than the default zone, in the binding menu enter the name of the zone in which you want the services to be registered.