Installing the Software

You can install the Novell Native File Access Protocols software as part of the NetWare 6 installation, or later as a separate process.

Installing the Software during Server Installation

Novell Native File Access Protocols are part of the NetWare 6 server installation program. Instructions are located in the NetWare 6 Overview and Installation Guide.

If you did not install the Native File Access Protocols software during the NetWare 6 server installation, you can install it by following the procedures in the next section.

Installing the Software after Server Installation

Novell Native File Access Protocols can be installed after installing a NetWare 6 server using NetWare Deployment Manager or the Graphical Server Console screen. Each method provides an easy-to-follow installation program that guides you through the required steps.

Accessing and Starting the Installation Program from the NetWare Server Console

1. Obtain the NetWare 6 Operating System CD.

2. Ensure your NetWare 6 server meets the prerequisites described in NetWare Server Prerequisites.

3. Ensure your Administrator Workstation meets the prerequisites described in Administrator Workstation Prerequisites.

4. At the NetWare 6 server console, enter STARTX to launch the graphical server console.

5. Click Novell > Install.

6. At the Installed Products screen, click Add.

7. Enter the path to the NetWare 6 Operating System CD and select the PRODUCT.NI file.

   The installation program begins.

Accessing and Starting the Installation Program from the NetWare Deployment Manager

1. Obtain the NetWare 6 Operating System CD.

2. Ensure your NetWare 6 server meets the prerequisites described in NetWare Server Prerequisites.

3. Ensure your Administrator Workstation meets the prerequisites described in Administrator Workstation Prerequisites.

4. At the Administrator Workstation, log in to the destination server that will run the Novell Native File Access Protocols software.

5. Insert the NetWare 6 Operating System CD.

6. Run NetWare Deployment Manager (NWDEPLOY.EXE) located on the root of the NetWare 6 Operating System CD.

7. Click Post-Installation Tasks > Install NetWare 6 Products.

   HINT:  If you are prompted to log in again while running NetWare Deployment Manager, you can enter the IP address of the server by clicking Details.

   
   

8. At the Product Selection screen, check the Novell Native File Access Protocols check box.

9. Click Next.

   The installation program begins.

Installing the Software

1. At the Components screen, select the Native File Access components you want to install and then click Next.

   • If you choose to install the Native File Access for Macintosh (AFP*) component, the software will be installed transparently during the NetWare installation process. No further interaction is required for the Native File Access for Macintosh software installation. You can skip to Step 8.

     For information on configuring Native File Access for Macintosh services and managing Mac users, see Working with Macintosh Computers.

   • If you choose to install the Native File Access for Windows (CIFS) component, continue with Step 2.

     For information on configuring Native File Access for Windows services and managing Windows users, see Working with Windows Computers.

   • For detailed information on installing and configuring the Native File Access for UNIX component, see Working with UNIX Machines.

2. Click Next.

3. At the Server Properties screen, configure the following server settings and then click Next.

   • Server Name: Enter a unique name for the NetWare server running CIFS that will appear in Network Neighborhood when users browse the network. The server name cannot be longer than 15 characters and must be different from the actual NetWare server name.

     The default Server Name is the NetWare server name with an added underscore (_) and a W. For example, a NetWare server named SERVER1 defaults to SERVER1_W.

   • Server Comment (Optional): Enter a comment for the server. The text in the Server Comment field displays when viewing details of the server from a Windows workstation.

   • Enable Unicode: Specify whether to enable Unicode character support. When checked, this option enables Unicode characters that are used in double-byte languages.

     To support Unicode, an additional file named UNINOMAP.TXT must be created and saved in the SYS:\ETC directory. When the UNICODE parameter is set to On, the UNINOMAP.TXT file is used to resolve Unicode-to-ASCII "no-map" problems.

     To specify "no-map" cases in the UNINOMAP.TXT file, enter the first Unicode value to watch for and then the second value representing the ASCII replacement code. For example:

     0178 98

     20AC CC

     Save the values in the UNINOMAP.TXT file. If an unmappable character is encountered, the system uses the ASCII substitution character specified in the file.

4. At the Authentication screen, select one of the following authentication methods and then click Next.

   • Local: Select if your Windows users will authenticate using NDS.

     With Local authentication, the NetWare server running Novell Native File Access Pack software performs the user authentication when clients are a member of a workgroup. With local authentication, the username and password on NetWare must match the username and password used to log in to the Windows workstation.

     If you select Local as your authentication method, fill in the following fields:

     • Workgroup Name: Enter the name of the domain or workgroup that the NetWare server will belong to. In this case, workgroup and domain are interchangeable terms.

     • WINS Address: Enter the IP address of the WINS server to be used to locate the primary domain controller (PDC), if the PDC and server running Novell Native File Access Pack software are on different subnets.

       Windows Internet Naming Service (WINS), part of the Microsoft Windows NT and 2000 Servers, manages the association of workstation names and locations with Internet Protocol (IP) addresses. WINS automatically creates and maintains a computer name and corresponding IP address mapping entry in a table. When a computer is moved to another geographic location, the subnet part of the IP address is likely to change. Using WINS, the new subnet information will be updated automatically in the WINS table.

   • Domain: Select if your Windows users will authenticate using a Microsoft Networking Domain.

     It is important to remember that a simple password is not required when using domain authentication. Because the password is kept on the Windows domain controller, it is not possible to use the Windows native Change Password feature to change the password. Instead, you must use the Windows domain management utilities. To work properly, the username and password on the domain controller must match the username and password used to log in to the Windows workstation.

     If you select Domain as your authentication method, fill in the following fields:

     • PDC Is on the Same Subnet as This Server: Select this option if the primary domain controller (PDC) is on the same subnet as the NetWare server.

     • Specify PDC Using DNS or WINS: Select this option to use DNS or WINS to specify the primary domain controller (PDC).

     • PDC Name: A PDC server name and static IP address are needed if the PDC is on a different subnet. This field should be used only when there is a valid reason for overriding WINS or DNS.

     • PDC Address: The address of the PDC must be static; otherwise, if the PDC reboots and the address changes, the server running Novell Native File Access Pack software will not be able to contact the PDC.

5. At the IP Addresses screen, specify the IP addresses on the server that you want to be attached to the CIFS protocol, or keep the default selection to Enable CIFS on All Addresses (recommended), and then click Next.

6. At the Share Point Setup screen, specify additional NetWare volumes or folders that you want to appear as share points in Network Neighborhood, or keep the default selection to Share all Mounted Volumes, and then click Next.

   Any volume or directory on the server can be specified as a shared point and made accessible via the Network Neighborhood. If no share points are specified, then all mounted volumes are displayed in Network Neighborhood.

   If you want to specify a share point, click New, fill in the following fields, and click Submit.

   • Directory: Enter the path to the server volume or directory which will be the root of the sharepoint. Beginning at the volume name, the full path must be specified and it must end with a backslash (\). For example:

     VOL1:GRAPHICS\

   • Share Name: Enter the name by which the sharepoint will be displayed to Windows computers. For example, if you enter "Lots of Pics" as the share name associated with VOL1\GRAPHICS, then Windows workstations browsing the network will see "Lots of Pics" instead of "VOL1\GRAPHICS."

   • Connections: Enter the number of connections that will be allowed to access the sharepoint. Or, check Unlimited to allow an unlimited number of connections.

   • Comment: Enter a description for the sharepoint that appears in Network Neighborhood.

7. At the Context Setup screen, specify the NDS contexts for your Windows (CIFS) users who need access to this NetWare server and then click Add.

   NDS contexts added here are saved in a list in the CIFS context search file (SYS:\ETC\CIFSCTXS.CFG). When the Windows user enters a username, the Novell Native File Access Pack software searches through each context in the list until it finds the correct User object.

   For example, if you had users with full NDS distinguished names such as Robert.sales.acme, Maria.graphics.marketing.acme, Sophia.graphics.marketing, and Ivan.marketing.acme, then you would enter the following contexts:

   sales.acme

   graphics.marketing.acme

   marketing.acme

   NOTE:  If User objects with the same name exist in different contexts, each user object attempts authentication in order until one succeeds with the corresponding password.

   The CIFSCTXS.CFG context search file can be edited manually after installation. For more information, see Specifying Contexts in the Context Search File.

8. Check the Summary screen and then click Finish.

   The installation program copies the required files to your server.

9. Restart the server by entering the following command at the server console:

   RESTART SERVER