Networks
 Install Appletalk Support in a Novell Environment
Created for TECHNIC Network Builder

Reviewed: July 15, 1997
Revised: July 15, 1997
Introduction

Before You Begin - Define Parameters

Define Appletalk Segments

Define Appletalk Zones

Determine Frame Types

Install Appletalk on Novell 3.x Server

Install Appletalk on Novell 4.x Server

Edit autoexec.ncf Manually

Install Mac Client for Novell 4.x

Purpose

To describe the prerequisites for and installation of Appletalk software on a Novell server.

Introduction

To support Macintosh and related Apple devices in a Novell environment, you must install Appletalk services on your file server. Appletalk is a suite of upper layer protocols that can communicate over Localtalk, Ethernet, Token Ring and other types of data link layers. Physical and logical segments of the network must be defined in a Novell server for Apple devices to communicate across the Novell network. 

For Macintoshes to communicate in a Novell environment, the Novell server becomes an "Appletalk router." The Appletalk router is part of a group of Appletalk NLMs (Network Loadable Modules) that manage Appletalk communications. Each network must have at least one seed router which has information defining physical segments and zones. Non-seed routers obtain their information from other routers. 

Define Parameters

Before you begin, three parameters must be defined before installing Macintosh services on Novell 3.x or 4.x servers:

  1. Define Appletalk network (physical) segments.

    2.  
  2. Define Appletalk zones.

    3.  
  3. Determine which frame type(s) need to be bound to the adapters in the server.
1-Define Appletalk Network (Physical) Segments

On a seed router one number represents the internal network associated with the Appletalk router itself (Novell server). This number must be unique in every router, and may be defined by a single number. The diagram below shows an example of network numbers assigned to internal and physical network segments.

Appletalk zones and nets are defined in the autoex file server or through the inetcfg.nlm (Novell 4.x only).

There are two kinds of Appletalk networks; non-extended and extended. Non-extended networks are virtually obsolete (Ethertalk Phase 1, Localtalk or X.25). Extended networks are used for most LANs and WANs and allow cable ranges of one or more networks. Cable ranges are used to define physically contiguous networks. The numbers you assign an Appletalk network are arbitrary but must define a range. In general one number is assigned for approximately 50 workstations or nodes. For example, 100 nodes on one segment might be assigned a range of 200-201, 500 nodes might be assigned the range from 200-210, and if you only have 50 nodes you could assign 200-200. A general rule of thumb is to assign the minimum range that covers your workstations.

Note: You must assign a range; single numbers can be used only for non-extended networks and internal networks.

2-Define Appletalk Zones

While Appletalk networks are defined by physical segments, Appletalk zones are logical groupings of Appletalk resources. Defining Appletalk zones over physical networks allows resource sharing between segments.

Note: You must define at least one zone for Appletalk to work on your network.If you have only one physical segment, assign one zone. If you have more than one segment, you can assign one or more zones.

Figure 1 shows how physical networks and zones can relate to each other. Users in the admin zone can access resources in the staff zone even though they are on different physical segments. Users in the staff zone cannot access resources in the admin zone as configured. Appletalk recognizes the first zone in a zone statement as the default zone for that physical segment. In the example given in Figure 1, both physical segments could have been defined as one zone, thus giving all users on each segment access to all resources on the network.

3-Determine Frame Types to be Configured in the Server

The Data Link/Physical layer(s) connecting the Appletalk segments determine which frame types will be needed.

Netware also supports Appletalk over FDDI and ARCNET.

Procedure for Installing Appletalk Services on a Novell 3.x Server

Novell 3.x comes with a 5-user NLM for Macintosh support. If you plan to support more than 5 users, you must purchase additional software from Novell.

  1. At the File server Console, load INSTALL. Choose Product Options and press INSERT. You will be prompted for a source disk. Insert the disk NW_MAC into drive A: and press ENTER. to load the Macintosh NLM. NW_MAC now appears on your Product Options screen.

    2.  
  2. Press ENTER to see the editable Configuration Files Menu and select Startup.ncf. Add the following lines:
      3. load mac

      set minimum packet receive buffers=100

  3. Save changes.

    4.  
  4. From the configuration files' menu select Autoexec.ncf. Add lines defining your Appletalk parameters. In the example below, these lines would define the appletalk network in Figure 1.

      5. load appletlk net=1000 zone={"admin"}

      load ne2000 int=3 port=300 frame=ethernet_snap name=etalk

      bind appletlk etalk net=200-202 zone={"staff","admin"}

      load 3C5x9 int=11 port=360 frame=ethernet_snap name=etalk2

      bind appletlk etalk net=100-100 zone={"admin"}

      load AFP

      load ATPS :optional

The first line loads the Appletalk module and associates it with the Appletalk router (server). Net=1000, defines the internal Appletalk network.

The second-fifth lines bind the Appletalk protocol to different physical segments and to the correct frame types (server 1 in figure 1). In non-seed routers use the range net=0-0 (they get their information from the seed router). The zone statements define relationships for the seed router.

The sixth line loads Appletalk File Service and the seventh loads Appletalk Print Services.

Printing

Print Services are optional but are defined by the same statements in autoexec.ncf. In Figure 1, any printer that is physically on the admin net could be accessed by any workstations in the admin, faculty zone. To add print services at this point, add the line ATPS to your autoexec.ncf file.

Procedure for Installing Appletalk Services on a Novell 4.x Server

Appletalk support is built in for Novell 4.x servers and managed through an NLM named Applemac. For Appletalk support you must do the following:

  1. Install and configure Applemac.

    2.  
  2. Bind the Appletalk protocol to the appropriate frame types using one of these methods:
  3. Install the Macintosh NDS client on workstations (optional but recommended).
Before you begin, you must determine Appletalk physical networks, zones and frame types to be used.
  1. From the File Server Console type load install.

    2.  
  2. From the Product Options menu choose Product Options

    3.  
  3. Scroll through Other Installation Items to Install Netware for Macintosh.

    4.  
  4. Install Netware for Macintosh from Novell CD-ROM

    5.  
  5. You must choose Final Installation Options as shown below.

Final Installation Options

  1. When the installation utility is run, it automatically adds the following line to your startup.ncf file - load mac. This adds Macintosh name space to the sys volume by default. To add the mac name space to other volumes, you must specify them.

    2.  
  2. Type Y to load Macintosh file services from the autoexec.ncf and later transfer to inetcfg.

    3.  
  3. Type Y to load Macintosh Print Services if you want DOS machines to access your Macintosh printers.

    4.  
  4. Type Y to install the Macintosh client support files if you would like your Macintosh users to log into the server in NDS mode.

    5.  
  5. Press ENTER.

    6.  
  6. When you have finished the Applemac configuration the Appletalk Configuration Utility window appears.




  7. When you select the first option Configure Appletalk Stack, the inetfcg utility automatically pops up. This method is recommended for configuring the Appletalk protocols and bindings. If you have problems with inetcfg, exit at this point and manually edit your autoexec.ncf file with the example shown later in this document.




  8. Choose Protocols, then Enable Appletalk. A screen appears to define options for your internal net and zone.


    9. Note: If you do not set packet forwarding to Enabled you will not be able to use Macintosh services through your Novell server because your workstations will not see the server. 

  9. Once packet forwarding is enabled, options for defining physical networks and zones become available. Type of packet forwarding is phase 2 unless you have old systems using ethertalk phase 1 or localtalk.

    10.  
  10. Enable the Internal Network option. You will be prompted for a network number. Insert one number here, not a range.

    11.  
  11. Define at least one zone. Save this information and return to the previous screen.

    12.  
  12. Choose bindings. A screen appears with current bindings. Press INSERT and choose Appletalk. A list of adapters appears. You must bind Appletalk protocol to each adapter that connects to Macintosh workstations. When you choose an adapter a window appears with two choices: extended or non-extended network. Choose extended unless you have a localtalk network.

    13.  
  13. A window appears with options for configuring the network segment attached to that adapter. Change the default setting to Define here (seed).



    14.  

  14. Define a beginning and an end network number to define a range. Zones can be the same as your internal network or additional zones can be defined here.

    15.  
  15. Save changes and exit the program. Reboot the server for the changes to take effect.
Configure Options

To configure options for Appletalk File and Print Services, access the configuration option through load install, nw_mac or type load atconfig at the console prompt.

Edit autoexec.ncf File Manually

To edit your autoexec.ncf file manually, your file should look something like this.

    ; load and bind appletalk
      load appletlk net=1000 zone={"admin"} load ne2000 int=3 port=300 frame=ethernet_snap name=etalk

      bind appletlk etalk net=200-202 zone={"staff","admin"}

      load 3C5x9 int=11 port=360 frame=ethernet_snap name=etalk2

      bind appletlk etalk net=100-100 zone={"admin"}

      load AFP

      load ATPS :optional

Your startup.ncf file should have the following line:
    load mac

Installing Macintosh Client for Novell 4.x

If you chose this option during installation of Macintosh services on your network, you have the option to make installation disks. If you did not choose this option during installation, the files must be loaded from the Novell CD-ROM to a Macintosh volume on your server. When the correct files are available to your Macintosh from the server or a disk, simply run install to set up an NDS client for that workstation. A tree appears in the upper right hand corner of the Macintosh. Selecting this tree allows the user to log on to an NDS directory tree, but specific servers are selected by going to the chooser and selecting zone/server.


 

© 1997 Missouri Research and Education Network