Previous Page: Loading NCS  Next Page: Verifying the Automated Configuration

Loading ARAS

AppleTalk Remote Access Service (ARAS) enables Macintosh* users to dial in to the LAN from remote locations using a modem. Further configuration is required to provide other capabilities, including the following:

Loading ARAS consists of the following tasks:

  1. Loading AppleTalk

    Load AppleTalk to configure your server as an AppleTalk router. If your server is already configured to route AppleTalk packets, refer to Step 2: Specifying Load Parameters for ARAS.

  2. Specifying parameters to load ARAS

Step 1: Loading AppleTalk

AppleTalk is loaded on the remote access server to route AppleTalk packets between the AppleTalk network and the remote Macintosh computers. This does not enable remote Macintosh computers to log in to the remote access server. If you want the users to be able to log in to the remote access server, you must load AppleTalk Filing Protocol (AFP), which is part of NetWare for Macintosh.

Use the Routing and Protocols option of NIASCFG to load AppleTalk and configure your server as an AppleTalk router. When you configure the server as an AppleTalk router using NIASCFG, the appropriate LOAD and BIND commands are added to the INITSYS.NCF and NETINFO.CFG files in the SYS:ETC subdirectory.


Novell Directory Services Considerations

If your remote users are logging in to the Novell Directory Services (NDS) software, you must load the MacIPX gateway on the remote access server and the remote client must load the MacIPX control panel on the workstation. If your NetWare server has bindery emulation turned on, then the server can accept non-NDS logins.

Use NIASCFG to load the MacIPX gateway on the server.


Step 2: Specifying Load Parameters for ARAS

To specify the LOAD parameters for ARAS, complete the following steps:

  1. Select a frame type.

    ARAS supports the following frame types:

    • Ethernet_SNAP
    • Ethernet_II

    The default is Ethernet_SNAP.

    If you have already loaded AppleTalk, select a frame type that is identical to that loaded with the LAN driver for the AppleTalk LAN. Refer to your AUTOEXEC.NCF file for more information. Typically, Ethernet_SNAP is selected for EtherTalk* 2.0 networks, and Ethernet_II is selected for EtherTalk 1.0 networks.

    IMPORTANT:  ARAS allows only a single frame type (Ethernet_SNAP or Ethernet_II) to be loaded at one time.

  2. Enter network numbers and AppleTalk zone names.

    Configure the following parameters for binding the ARAS driver to AppleTalk:

    1. Enter the starting range of the network number.

      The starting range of the network number must be an integer between 1 and 65,279.

    2. Enter the ending range of the network number.

      The ending range of the network number must be an integer between 1 and 65,279.

      NOTE:  The difference between the two integers must be between 0 and 10. The network range, however, must be unique on the LAN. Each group of ports on the server running ARAS is considered to be a network.

    3. Enter AppleTalk zone names.

      A valid zone name is a string of up to 32 characters that can include hyphens (-), underscores (_), and spaces ( ). You can specify one or more zone names separated by commas, for example, Novell Engr, Novell Mktg. If any Macintosh on the LAN is a resource for the remote Macintosh calling in, specify the zone name to which the Macintosh on the LAN belongs. In a NetWare environment, you can enter LOAD ATCON at the NetWare console prompt to find existing AppleTalk zone names.

  3. Press Esc and respond Yes when prompted to save your changes.

    You are asked if you want to restart the service at this time.

  4. Select Yes and press Enter to restart ARAS.

    Restarting the service causes any users currently using the service to be disconnected.



  Previous Page: Loading NCS  Next Page: Verifying the Automated Configuration