Documentation Conventions
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. Also, a trademark symbol (, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a thirdparty trademark.
Novell Native File Access Protocols Installation and Administration Guide

Overview

Novell Native File Access Protocols lets Macintosh, Windows, and UNIX workstations access and store files on NetWare servers without having to install any additional softwaresuch as the Novell ClientTM. The software is installed only on the NetWare server and provides "out of the box" network access. Just connect the network cable, start the computer, and you have access to servers on your network. No client software installation. No client configuration. No problem. Novell Native File Access Pack software enables the NetWare server to use the same protocol (referred to as native) as the client workstation to copy, delete, move, save, and open files. Windows workstations perform these tasks using the native Common Internet File System (CIFS) protocol, Macintosh workstations use the native Apple* Filing Protocol (AFP), and UNIX computers use the Network File System (NFS) protocol.
NetWare Server CIFS AFP NFS IP CIFS AFP NFS

Windows

Enabling native protocols on a NetWare server means that users can access files on the network, map network drives, and create shortcuts to NetWare servers using the native methods available in their specific operating system. Windows users can use their familiar Network Neighborhood (or My Network Places). Macintosh users can use Chooser or the Go menu to access network files and even create aliases. Because the NetWare server is running native protocols, users can copy, delete, move, save, and open network filesjust like they would if they were working locally.

Network Neighborhood

Chooser
By consolidating user management through Novell Directory Services (NDS), Native File Access Protocols simplifies overall network administration. All users who need access to the network are represented in NDS through User objects, which enables you to easily and effectively assign trustee rights and access control and manage all User objects from a single location on the network.
NOTE: Windows users can also be managed through a Windows Domain Controller and UNIX users can be
managed through Network Information Service (NIS).

Getting Started

Novell Native File Access Pack is easy to install. To get started, continue with Chapter 2, Installing Novell Native File Access Protocols on a NetWare 6 Server, on page 9.
Installing Novell Native File Access Protocols on a NetWare 6 Server

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.
TIP: 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.
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 on page 15. For information on configuring Native File Access for Macintosh services and managing Mac users, see Chapter 3, Working with Macintosh Computers, on page 17. 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 Chapter 4, Working with Windows Computers, on page 23. For detailed information on installing and configuring the Native File Access for UNIX component, see Chapter 6, Working with UNIX Machines, on page 49.
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:

The CIFSCTXS.CFG context search file can be edited manually after installation. For more information, see Specifying Contexts in the Context Search File on page 28.
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

Starting and Stopping AFP and CIFS Protocols Service
Each time the server starts, the Novell Native File Access Protocols are loaded from commands that were automatically added to the AUTOEXEC.NCF configuration file by the installation program. You can also load and unload the Native File Access Protocols service manually at the server console.
Macintosh (AFP) Protocols 1 At the server console, enter AFPSTRT to load the Macintosh (AFP) protocols on the server.
Any changes made in the AFP configuration files since the last time you started the service are applied when the AFP protocols are reloaded.
2 At the server console, enter AFPSTOP to unload the Macintosh (AFP) protocols on the server. Windows (CIFS) Protocols 1 At the server console, enter CIFSSTRT to load the Windows (CIFS) protocols on the server.
Any changes made in the CIFS configuration files since the last time you started the service are applied when the CIFS protocols are reloaded.
2 At the server console, enter CIFSSTOP to unload the Windows (CIFS) protocols on the

server.

Whats Next?
After installing the Native File Access Pack software, you must create simple passwords for Macintosh, Windows, and UNIX users before they can access files on the server using their native protocols. To set up and manage Macintosh users, see Chapter 3, Working with Macintosh Computers, on page 17. To set up and manage Windows users, see Chapter 4, Working with Windows Computers, on page 23. To set up and manage UNIX users, see Chapter 6, Working with UNIX Machines, on page 49.
Working with Macintosh Computers
This chapter contains the following information: Administrator Tasks for Native File Access for Macintosh Services (page 17) Macintosh End User Tasks (page 19)
Administrator Tasks for Native File Access for Macintosh Services
Native File Access for Macintosh provides several ways to simplify your administration tasks and customize how Macintosh workstations interact with the network: Creating Simple Passwords for Several Macintosh Users (page 17). Editing the Context Search File (page 17). Creating a Guest User Account (page 18). Renaming Volumes (page 18).

Creating Simple Passwords for Several Macintosh Users
You can create simple passwords for users one at a time using ConsoleOne. But if you want to create passwords for several Macintosh users at once, you can add the CLEARTEXT option to the LOAD AFPTCP command at the server console. For example: LOAD AFPTCP CLEARTEXT When the CLEARTEXT option is added to the AFPTCP command, users logging in to the server from a Macintosh workstation are prompted to provide their NDS username and NDS password. Once the NDS password is verified, a simple password is automatically created and stored in NDS. The simple password is the same as the NDS password. The CLEARTEXT option is meant to be a temporary way to create simple passwords for many Macintosh users. After Macintosh users have created simple passwords, the AFPTCP NLMTM should be loaded without the CLEARTEXT option.
WARNING: The CLEARTEXT option allows unencrypted passwords to be sent over the network. If you are
concerned about someone capturing your password over the network, you should not use this option. Instead, you should manage passwords using ConsoleOne on the Administrator Workstation.
Editing the Context Search File
A context search file allows Macintosh users to log in to the network without specifying their full context. The context search file contains a list of contexts that are searched when no context is provided or the object cannot be found in the provided context. When the Macintosh user enters a username, the server searches through each context in the list until it finds the correct User object.
Macintosh allows only 31 characters for the username. If the full NDS context and username are longer than 31 characters, you must use a search list to provide access.
TIP: Macintosh users do not need to enter a context or have an entry in the context search file if their User
objects are placed in the same container as the Server object.
If User objects with the same name exist in different contexts, the first one in the context search list will be used. To edit the context search file, do the following:
1 Using any text editor, edit the CTXS.CFG file stored in the SYS:\ETC directory of the server
running Novell Native File Access Protocols.
2 On separate lines, enter the contexts to search.
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 to the CTXS.CFG file: sales.acme graphics.marketing.acme marketing.acme

passwords, their NetWare passwords will be affected differently, as described in the following scenarios: If both the NetWare password and the simple password are already the same when the user changes the simple password, the NetWare password is synchronized and both passwords remain the same. If the NetWare password and the simple password are not the same when the user changes the simple password, the NetWare password is not synchronized with the new simple password. The two passwords remain different. Whenever a user changes the NetWare password, the simple password is not synchronized with the new NetWare password. The user must separately change the simple password for the two passwords to match.
NOTE: Password synchronization is simpler for Macintosh users. Native File Access for Macintosh (AFP) software keeps the simple password and the NetWare passwords synchronized. In other words, when a Mac user changes either password using the native client software, password synchronization is automatic and transparent.
Specifying Contexts in the Context Search File
During the installation, you specified the NDS contexts for Windows users who require access to the network. These contexts are saved in the context search file. When Windows users enter a username, the Native File Access component running on the server searches through each context in the list until it finds the correct User object.
NOTE: In Domain mode, 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.
You can add or remove contexts by editing the context search file.
1 Using any text editor, edit the CIFSCTXS.CFG file stored in the SYS:\ETC directory of the
server running Novell Native File Access Protocols.
2 On separate lines, enter the full contexts to search.
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 to the CIFSCTXS.CFG file: sales.acme graphics.marketing.acme marketing.acme
3 Save the file in the SYS:\ETC directory. 4 At the server console, enter CIFSSTOP to unload the current context search file. 5 Enter CIFSSTRT to load the new context search file and apply the changes.

Administrators can customize the network environment for Windows workstations (CIFS) by using one of the following methods: Using ConsoleOne to Configure CIFS (page 29) Using the CIFS.CFG File to Configure CIFS (page 31)
IMPORTANT: You can use ConsoleOne to configure CIFS only if you have installed the SP1 software on the server running Novell Native File Access Protocols. In fact, if SP1 software is installed on your server, the CIFS.CFG file will be disabled and contain a note to use ConsoleOne for configuration.
Using ConsoleOne to Configure CIFS 1 From the Administrator Workstation, log in as a user with the Supervisor right.
Working with Windows Computers 29
2 Run CONSOLEONE.EXE (located in \PUBLIC\MGMT\CONSOLEONE\1.2\BIN\). 3 Right-click the Server object and then click Properties. 4 Click the CIFS tab and select one of the three CIFS pages: Config, Attach, or Shares. 5 Enter the desired parameters in the fields provided.
See the page description sections below for details.
6 Click Apply to save your settings. Config Page Parameters
The following parameter fields appear on the Config Page under the CIFS tab in ConsoleOne: Server Name is the name of the server running Novell Native File Access Protocols. The length can be a maximum of 15 characters. This name is displayed in Network Neighborhood. This server name must be different from the NetWare Server name. Comment is the comment associated with the server name discussed above. This comment is displayed when viewing details. WINS Address is the address of the WINS server to be used to locate the PDC, if the PDC and the server running Novell Native File Access Protocols are on different subnets. Unicode specifies whether Unicode character support is enabled. Unicode characters are used in double-byte languages.
IMPORTANT: To support Unicode, an additional file named UNINOMAP.TXT must be created and saved
in the SYS:\ETC directory. When the -UNICODE value 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:

4 Save the CIFS.CFG file to the same directory (SYS:\ETC). 5 Restart the server. Configuration File Parameters
The following parameters can be set in the SYS:\ETC\CIFS.CFG file to customize the user experience for your environment.
TIP: Any parameter can be excluded by placing a # at the beginning of the command line. If the parameter is
excluded, the default value is used.

-SERVERNAME

The name of the server running Novell Native File Access Protocols. The length can be a maximum of 15 characters. This name is displayed in Network Neighborhood. This server name must be different from the NetWare Server name.
Value: Server_Name Default: None

-COMMENT

The comment associated with the server name listed above. This comment is displayed when viewing details. Value: Comments Default: None

-AUTHENT

The method of authentication used by Novell Native File Access Protocols. DomainClients are members of a domain. A Windows domain controller performs user authentication.The username and password on the domain controller must match the username and password used to log in to the Windows workstation. LocalClients are members of a workgroup. The server running Novell Native File Access Protocols performs the user authentication. The username and password on NetWare must match the username and password used to log in to the Windows workstation. Value: Domain | Local Default: Local

-DOMAIN

The domain or workgroup that the server will belong to. Value: Domain_Name Default: Workgroup

-WORKGROUP

The domain or workgroup that the server will belong to. Workgroup and Domain can be used intergchangeably. Value: Workgroup_Name Default: Workgroup
The PDC server name and static IP address. This is needed if the PDC is on a different subnet. This option should be used only when there is a valid reason for overriding WINS or DNS.
NOTE: The address of the PDC must be static; otherwise, if the PDC reboots and the address changes, the server running Novell Native File Access Protocols will not be able to contact the PDC.
Value: PDC_Name Address Default: None
Address of WINS server to be used to locate the PDC, if the PDC and server running Novell Native File Access Protocols are on different subnets. Value: IP_Address Default: None

-ATTACH

Bind the CIFS protocol to the IP address specified. For multiple addresses, repeat the command as needed. Value: IP_Address Default: Bound to all addresses.

-SHARE

Allow any volumes or directories on the server to be specified as shared points and to be accessible via the Network Neighborhood. If no -SHARE line is specified (or is commented out), then all mounted volumes are displayed. Localpath is the path to the server volume or directory which becomes the root of the sharepoint. This path must end with a backslash (\). Sharename is the name by which the sharepoint is known to the Windows computers. Connection Limit is the number of connections allowed to the sharepoint (0 is unlimited). Comment is a description for the sharepoint that appears in Network Neighborhood or My Network Places. Value: Localpath Sharename Connection Limit Comment Default: All mounted volumes are shared.

-UNICODE

When On (enabled), this command enables Unicode characters (used in double-byte languages). Value: On | Off Default: Off (disabled)
IMPORTANT: To support Unicode, an additional file named UNINOMAP.TXT must be created and saved in the SYS:\ETC directory. When the -UNICODE value 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:
Sample CIFS.CFG Configuration File
#This name will display in Network Neighborhood with the #following comment. -SERVERNAME NW6-NNFAP -COMMENT Server running Novell Native File Access Protocols #Novell Native File Access Protocols is configured to use Local #authentication. -AUTHENT LOCAL #The workgroup name is ONENET. -WORKGROUP ONENET #When this volume is mounted, the local path CIFSVOL:\ will appear as a sharepoint named Graphics Volume with unlimited connections (0) and its corresponding comment. -SHARE CIFSVOL:\ Graphics Volume 0 Lots of image files
CIFS.CFG Configuration File Shortcuts
You can enter the following commands at the server console to modify the configuration file. CIFS SHARE ADD localpath sharename connectionlimit comment adds a new sharepoint and also adds the command to the CIFS.CFG file. CIFS SHARE REMOVE sharename removes the sharepoint and comments it out of the CIFS.CFG file.
Viewing Configuration Details
You can view details about how Novell Native File Access Protocols are configured by entering the following commands at the server console. CIFS INFO displays operational information. CIFS SHARE displays all active sharepoints. CIFS SHARE sharename displays information about a specific sharepoint.

Windows End User Tasks

When Novell Native File Access Protocols is properly configured, the Windows users on your network will be able to perform the following tasks: Accessing Files from a Windows Computer (page 35) Mapping Drives from a Windows Computer (page 35) Changing Passwords from a Windows Computer (page 35)

nisinst [-s name] [-x context] [ -i ip address]
The parameter -s is optional. It specifies the name to be given to the nisserver object. The parameter -x is also optional. It specifies the context where the object should be created in eDirectory. The optional command line option -i is to specify the IP address to be attached to the NISServ Object. This option is useful in a cluster environment and for servers with multiple NIC cards. Run the NISINST manually, if the nisserver object is deleted.
IMPORTANT: If directory services are removed, you need to comment the SEARCH ROOT parameter in
NFS.CFG and do the following:
nfsstop schinst nisinst nfsstart

Upgrade Utility

The upgrade utility (NFAUUPG.NLM) is automatically invoked to upgrade the default configuration of NetWare NFS Services 2.x or 3.0 when you choose Native File Access for UNIX while upgrading the operating system from NetWare 4.x or NetWare 5.x to NetWare 6. When invoked during installation, the upgrade utility retains the existing configuration into the new configuration files, NFS.CFG, NIS.CFG, and NFSSERV.CFG located in SYS:\ETC. The existing configuration files NFSTHOST, and NFSEXPRT are retained. During installation, if N4S schema is detected, then the UAM schema will get extended automatically to support features, such as, multiple domain support, RFC2307 compliance for NIS, starting and stopping NIS services from ConsoleOne.
Setting Up and Managing Novell Native File Access for UNIX
This section explains how to set up and manage Native File Access for UNIX. It includes information on the following: Configuration Methods (page 58) Configuring Server General Parameters (page 59) Migration of NIS Maps (page 63) NFS Server (page 69) NIS Server (page 77)

Configuration Methods

Novell Native File Access for UNIX can be configured using ConsoleOneTM and also by setting the file-based configuration parameters of the various components.
ConsoleOne-Based Configuration
To start ConsoleOne from the client, complete the following steps.
IMPORTANT: Before starting ConsoleOne, ensure that you run NFSSTART on the server that you want to

administer.

1 Start ConsoleOne from the server where Native File Access for UNIX is installed. 2 Click NFSAdmin and then the login toolbar icon. 3 Enter the tree name, context name, authorized username, and authorized password. 4 Click OK. 5 Enter the hostname or IP address and then click OK.
IMPORTANT: To log in successfully, make sure that your file server name and hostname are the same and that you have logged in to the tree of the server you want to administer. You will not be able to administer a NetWare NFS Services 3.0 on NetWare 5.1 from ConsoleOne on NetWare 6. Figure 2 Novell Native File Access for UNIX Objects

NOTE: Administering NetWare 5 NFS Services on NetWare 5 from ConsoleOne on NetWare 6 is not supported.

Migration of NIS Maps

If you already have an UNIX NIS Server (text-based) and you want the new NetWare NIS Server to serve the same data served by the old NIS server, you can copy all those text files into the specified location and then run the migration utility to create eDirectory entries for a specified domain. The migration utility creates the Domain object in the default context as well as two other containers in the same context with the names domainname_U and domainname_G. During the migration, the utility searches for existing eDirectory users and groups under the containers specified by the SEARCH_ROOT configuration parameter (specified in NFS.CFG) and, based on the migration option specified, modifies the UNIX information of those objects. If the objects are not found, the users are migrated to domainname_U and the groups are migrated to domainname_G. The rest of the data is migrated under the Map objects created under the Domain object.
IMPORTANT: The User and Group objects will not be created under the passwd and group Map object. They will spread across the eDirectory tree and DomainName_U, DomainName_G depending upon the SEARCH_ROOT configuration parameter.
Maps can be migrated using the following three options: UPDATE(Default) Updates all existing objects' information with the new information. If no objects exist, it creates new ones. REPLACEDeletes all existing objects and creates new ones. For passwd and group maps, the old objects are not deleted. MERGERetains all existing objects' information and logs them as conflicting records in the MAKENIS.LOG file. If no objects exist, it creates new ones. Before migrating the users and groups, remove the password field ("*", "x", or "!") from the corresponding text file and then migrate. After doing this, you can set the UNIX password. This is done by making the UNIX machine an NIS client to the NetWare machine, logging in as that NIS user, and running an NIS client utility named YPPASWD to set the UNIX password.
NOTE: The password for a migrated UNIX user (one who already has the password) cannot be set from an NIS client. A password can be set only for users who do not have a password.
For more information on UNIX user management, see UNIX User Management Using eDirectory on page 54.

File-Based Migration

Migration, by default uses the makefile SYS:ETC/NIS/NISMAKE, which contains the location of the text file for every map. The general syntax of the migration utility is: makenis [-r resultfilename -[r]d domainname [-n context] [-f nismakefilename] {[mapname -[l|b]p line or byte object in mapname].}
NOTE: All options should be used only in the specified order.
In general, to create a domain and migrate data or to use the existing domain object, use the following format:

6 Click Add Trustee. Enter the hostname that you want to give exported directory/volume
access to. An asterisk (*) will give access to all the hosts. You can also specify the type of access you want to give to the host.
7 Click the Trustee name on the Export New Path panel to set their access rights.
Hosts with Root AccessThe host whose users with root privileges have Admin rights to the exported directory. Select this field to display a list of these hosts. If a host with access is not specified as having root access, root users on that host have the rights of the NFS user Nobody. Hosts with Read-Write AccessThe hosts with access whose users have read/write access to the exported path. Select this field to display a list of these hosts.
8 To remove a host from the Trustee list, select the trustee and click Remove Trustee. Modifying the Exported Path 1 In the left panel of the ConsoleOne main menu, click the server that you want to administer.
The Export icon appears in the right panel.
2 Double-click Exports to see the currently exported path. 3 Right-click the exported path you want to modify and then click Properties.
You can now see the properties of the exported path and modify them.
4 Make the changes as required and then click OK. Removing an Exported Path 1 In the left panel of the ConsoleOne main menu, click the server that you want to administer.
2 Double-click Exports to see the currently exported path. 3 Right-click the exported path you want to delete and then click Remove.
1 Run NFSSTOP. 2 Set the parameters in the NFS.CFG file as follows by following Steps 1 to 5 in Configuring
the Server General Parameters on page 61. NDS_ACCESS=0 NIS_CLIENT_ACCESS=1 NIS_DOMAIN= nis domainname NIS_SERVER= servername which is servicing the specified domain
3 Run NFSSTART. 4 Load NFSSERV. Starting and Stopping NFS Server from ConsoleOne 1 Click NFSAdmin and log in to the server that you want to administer. 2 Click the S icon on the toolbar to start/stop the NFS Server. The background color of the S
icon indicates the status of the NFS Server Software.
Refreshing the Exported Paths View
If the NFSEXPRT file is modified outside ConsoleOne, then to view the current contents of the file, do the following:
1 In the left panel of the ConsoleOne main menu, click the server that you want to administer.
2 Right-click Exports and then click Refresh to view the currently exported paths. Managing NFS Server Log Files

Setting Up a NetWare Server as a NIS Master 1 Copy the NIS related text files required for the domain from the
UNIX machine (which are available in /ETC in UNIX) into SYS:\ETC\NIS.
2 (Conditional) If you want to set up other NIS server as slave to this NIS server, do the

following:

2a Create a text file called YPSERV in SYS:\ETC\NIS. For every slave server enter the
hostname of the slave server in this file in the following format:
slaveserverhostname1 slaveserverhostname1 slaveserverhostname2 slaveserverhostname2
NOTE: The first field should not be IP Address.
2b Enter the YPSERVERS map entry in SYS:\ETC\NIS\NISMAKE with its path in the

following format:

YPSERVERS SYS:\ETC\NIS\YPSERV
3 Migrate the domain. For migration information, see File-Based Migration on page 63. 4 Load NISSERV.NLM. Now the NetWare NIS Server is setup as Master NIS Server. 5 (Conditional) If the map data in NIS master is modified anytime, and the changes done needs
to be updated in the slave servers immediately then execute the following command: yppush -d domainname [-v] mapname
NOTE: The changes done on the NIS master are automatically updated on the slave servers periodically.
Setting Up a NetWare Server as NIS Slave Server 1 While setting up the UNIX machine as the master, add the NetWare server name to the slave

server list.

2 In the NetWare server, make sure that the parameter NIS_CLIENT_ACCESS=1 in the file

SYS:\ETC\NFS.CFG.

3 Set the domain to the one that is being served by the UNIX NIS server, using the following

command:

ypset domainname hostname
To login or to set the password for a user from a UNIX NIS client, set the default domain in the NetWare server using ypset.
4 Make sure NISSERV.NLM is loaded. 5 Run MKSLAVE, to setup the NetWare machine as slave, with the following parameters:
mkslave -d domainname -m master [-x contextname]
Setting Up a NetWare Server as NIS Client 1 Run NFSSTOP. 2 In the NetWare server, make sure that the parameter NIS_CLIENT_ACCESS=1 in the file
Working with UNIX Machines 79
3 Run NFSSTART. 4 Set the default domain by entering
ypset domainname hostname/IP_address
ConsoleOne- Based Management for NIS Server NIS Server Configuration Parameters
To configure the parameters required for nis services, right-click The Nisserv_servername > Click Properties. A panel similar to the following appears:
Figure 14 Nis Server-general Parameters Panel

2 To delete the host address, select the hosts IP address from the IP Address field, and then click
Delete > Apply > OK.
Figure 24 Netgroup Map Records Properties Panel
To add a netgroup address, enter the name of the Map Record, browse the icon for the Map Name, enter the description of the map, and then click Apply > OK.
Figure 25 Network Map Records Properties Panel
1 To enter the IP network number, click Browse, enter the network number, and click OK. 2 To enter the IP netmask number, click Browse, enter the netmask number, click OK, enter the
description of the record, and then click Apply > OK.
Figure 26 Protocols Map Records Properties Panel
1 Enter the protocol number and a brief description of the record. 2 Click Apply > OK.

Figure 27

RPC Map Records Properties Panel
1 In the ONC RPC Number field, enter the RPC number of the program. 2 Enter a brief description of the record. 3 Click Apply > OK.
Figure 28 Services Map Records Properties Panel
1 In the IP Service Port field, enter the port number that this service is available on. 2 In the IP Service Protocol field, enter the protocol used to access the specified service. 3 Enter a brief description of the record. 4 Click Apply > OK.

Figure 29

General Map Records Properties
1 In the Map Record field, specify the map record using the following format:

key record

2 Enter the map name that the record belongs to. 3 Enter a brief description of the record. 4 Click Apply > OK. Starting and Stopping NIS Server from ConsoleOne
Right-click NISSERV_Servername object > click Start/Stop Services.
NOTE: You can also start and stop the NIS Services by using the NIS Server menu. Make sure you refresh ConsoleOne after you change the status of NIS using the menu.
Setting Up Novell Native File Access for UNIX with Novell Cluster Services
To get the full benefit of using Novell Native File Access for UNIX with Novell Cluster ServicesTM, the software must be installed and configured to work in a cluster environment. This section describes the following: Prerequisites (page 89) Configuring the Properties of Cluster Resource (page 91) Component-Specific Configuration (page 93) Starting and Stopping Native File Access for UNIX with Cluster Services (page 94)

Manual

December 10, 2002

Novell NetWare 6

www.novell.com OVERVIEW AND INSTALLATION GUIDE

100-004725-001

NetWare 6 Overview and Installation Guide 100-004725-001 February 25, 2003 Novell Confidential

Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. This product may require export authorization from the U.S. Department of Commerce prior to exporting from the U.S. or Canada. Copyright 2002 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. U.S. Patent No. 5,157,663; 5,349,642; 5,455,932; 5,553,139; 5,553,143; 5,572,528; 5,594,863; 5,608,903; 5,633,931; 5,652,859; 5,671,414; 5,677,851; 5,692,129; 5,701,459; 5,717,912; 5,758,069; 5,758,344; 5,781,724; 5,781,724; 5,781,733; 5,784,560; 5,787,439; 5,818,936; 5,828,882; 5,832,274; 5,832,275; 5,832,483; 5,832,487; 5,850,565; 5,859,978; 5,870,561; 5,870,739; 5,873,079; 5,878,415; 5,878,434; 5,884,304; 5,893,116; 5,893,118; 5,903,650; 5,903,720; 5,905,860; 5,910,803; 5,913,025; 5,913,209; 5,915,253; 5,925,108; 5,933,503; 5,933,826; 5,946,002; 5,946,467; 5,950,198; 5,956,718; 5,956,745; 5,964,872; 5,974,474; 5,983,223; 5,983,234; 5,987,471; 5,991,771; 5,991,810; 6,002,398; 6,014,667; 6,015,132; 6,016,499; 6,029,247; 6,047,289; 6,052,724; 6,061,743; 6,065,017; 6,094,672; 6,098,090; 6,105,062; 6,105,132; 6,115,039; 6,119,122; 6,144,959; 6,151,688; 6,157,925; 6,167,393; 6,173,289; 6,192,365; 6,216,123; 6,219,652; 6,229,809. Patents Pending.
Novell, Inc. 1800 South Novell Place Provo, UT 84606 U.S.A. www.novell.com NetWare 6 Overview and Installation Guide February 2002
Online Documentation: To access the online documentation for this and other Novell products, and to get updates, see www.novell.com/documentation.

Novell Trademarks

ConsoleOne is a trademark of Novell, Inc. GroupWise is a registered trademark of Novell, Inc., in the United States and other countries. eDirectory is a trademark of Novell, Inc. Internetwork Packet Exchange and IPX are trademarks of Novell, Inc. NDS Manager is a trademark of Novell, Inc. NE3200 is a trademark of Novell, Inc. NetWare is a registered trademark of Novell, Inc., in the United States and other countries. NetWare Loadable Module and NLM are trademarks of Novell, Inc. NetWare Management Agent is a trademark of Novell, Inc. NetWare Management Portal is a trademark of Novell, Inc. NetWare Peripheral Architecture is a trademark of Novell, Inc. Novell is a registered trademark of Novell, Inc., in the United States and other countries. Novell Client is a trademark of Novell, Inc. Novell Cluser Services is a trademark of Novell, Inc. Novell Directory Services and NDS are registered trademarks of Novell, Inc., in the United States and other countries. Novell Distributed Print Services is a trademark and NDPS is a registered trademark of Novell, Inc., in the United States and other countries. Novell iFolder is a trademark of Novell, Inc. Novell Support Connection is a registered trademark of Novell, Inc., in the United States and other countries. Open Data-Link Interface and ODI are trademarks of Novell, Inc. SFT and SFT III are trademarks of Novell, Inc. Storage Management Services and SMS are trademarks of Novell, Inc. Transaction Tracking System and TTS are trademarks of Novell, Inc. Virtual Loadable Module and VLM are trademarks of Novell, Inc. ZENworks is a trademark of Novell, Inc.

NetWare 6 Operating System CD.
3 Double-click the Network Preparation folder to view the tasks and read
the Overview section to get an understanding of the tasks.
4 Back up any server data and Novell eDirectory data following the
instructions in the Back Up Data step.
5 Run the View and Update eDirectory Version program to update

eDirectory as required.

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.
6 Run the Prepare for eDirectory program to extend the network schema.
7 (Conditional) If you are upgrading a cluster of NetWare servers, run the
Prepare a Novell Cluster for Upgrade program.
8 (Conditional) If you are upgrading a NetWare 5 server running NDS 7
that has NSS volumes, run the Prepare a Server with NDS 7 and NSS program.
9 Follow the instructions in the Update Certificate Authority (CA) Object
step to create or update a Security container object and a Certificate Authority (CA) object. After you have completed the Network Preparation section of NetWare Deployment Manager, read through the Installation / Upgrade Options section to help you decide the option that best meets your needs.
After choosing an installation or upgrade option, you should now prepare the computer to be a NetWare 6 server.

Preparing the Computer

To prepare your computer for NetWare 6, do the following: Install computer and networking hardware Create and format a DOS partition Access the installation files
Installing Computer and Networking Hardware
Follow the manufacturers instructions to install and connect the network board and network cabling to your computer. Make sure that all storage devices are properly attached to storage adapters.
Creating and Formating a DOS Partition
NetWare requires a DOS partition to start the computer and load NetWare. The DOS partition contains the NetWare startup and server files.
HINT: You should increase the size of your DOS partition to accommodate your specific configuration requirements. See System Requirements on page 27.
To create and format a DOS partition, complete the following steps.
1 Back up any desired data to another computer or offline storage media. 2 Insert the NetWare 6 Operating System CD and boot the computer. 3 Complete one of the following:
If the computer boots from the CD, follow the on-screen prompts to create and format a partition. Skip to Selecting the Language and Accepting the License Agreement on page 36. If you will be installing from files located on another server, continue with the following steps. If the computer does not boot from the CD, continue with the following steps.
4 Boot your computer with DOS 3.3 or later.

access the installation files on the network.
2 At the CD drive or network drive prompt, enter INSTALL.
Navigating in the Character-Based Screens
The initial screens of the installation program display in text-based mode. Auto-detected and default settings appear on each screen.
You can accept the detected and default settings, or you can modify the settings to meet the needs of your networking environment.
HINT: To continue the installation with the standard settings, use the arrow keys to select Continue in the Options box and then press Enter.
To modify the settings, use the arrow keys to select Modify in the Options box and then press Enter. Select the field to be modified and press Enter. Select or enter the appropriate value.
Some screens require additional keystrokes in order to navigate through the interface. Information about screen navigation appears at the bottom of each screen.
Selecting the Type of Installation and Regional Settings
To select the type of installation and select regional settings, you must Select the language and accept the License Agreement Select the type of installation Specify server settings Select the regional settings Select the mouse and video type
Selecting the Language and Accepting the License Agreement
The installation program is available in several languages. You can install other language options, such as the language for the operating system or for users, later during the installation program. Accepting each License Agreement means that you have read and you accept terms and conditions contained in the License Agreement. Press F10 to accept.
Selecting the Type of Installation
Express Installation or Custom Installation Express Installation
The Express Installation automatically detects drivers and installs the NetWare server with default settings and default software programs.The settings include the following 4 GB volume SYS: (Any remaining disk space will be left as free space.) LAN and disk drivers: Auto-discovered and loaded Default products installed Country Code: 1 Codepage: 437 Video mode: VGA Plug N Play Keyboard: United States Mouse: Auto-discovered and loaded

Numbering schemeSome network administrators set up a predetermined numbering scheme to identify servers in particular locations or organizations. For example, all servers in building A might begin with 0101, and all servers in building B might begin with 0102. If you choose to install IP and not IPX, the SERVERID reference is not used and is removed from the AUTOEXEC.NCF file. You can add IPX after the server installation by adding the SERVERID 8_digit_number command after the SERVERNAME command in the AUTOEXEC.NCF file. Load Server at RebootSelect No if you do not want the AUTOEXEC.BAT and CONFIG.SYS files to contain the commands to automatically load the server operating system when the computer reboots. If you select Yes (default), the old AUTOEXEC.BAT and CONFIG.SYS files are renamed and saved with a.00x extension. Server SET ParametersYou might need to modify the SET parameters for some device drivers, such as for network boards and storage devices, in order to complete installation. SET parameters are saved to the STARTUP.NCF file. Startup DirectoryThe directory on the DOS partition that contains the files to launch the NetWare server. (This field will display only during an upgrade.)
Selecting the Regional Settings
Choose the country, code page, and keyboard mapping for your language and computer.
Selecting the Mouse and Video Type
Mouse TypeChoose a mouse type, if available on the computer. The installation program supports USB, PS/2 and serial mouse types, but a mouse is not required. Video TypeThe NetWare installation program is optimized to display with video display hardware that is VESA 2 compliant.
NOTE: The video type is not auto-detected by the installation program. You must
select the settings for the computer.
Selecting a Platform Support Module and Storage Adapter
To select a platform support module and storage adapter, you must Select a platform support module (if required) Select a PCI Hot Plug module (if required) Select and configure a storage adapter

To add a driver, in the Options box select Modify. Select the driver field and press Enter. Press Insert to select from a list of drivers provided with NetWare. Press Insert again to install a driver from diskette. To delete a driver, in the Options box select Modify. Select the driver field and press Enter. Select the driver to delete and press Delete. To modify a driver, in the Options box select Modify. Select the driver field and press Enter. Select the driver to modify and press Enter. Select the property to modify.
Selecting a Platform Support Module (If Required)
A platform support module (PSM) provides increased performance for multiprocessor computers and some specific hardware configurations. If a PSM driver is required, it will be auto-detected. If the installation program does not detect a PSM driver, your computer does not need one.
NOTE: If a PSM driver is detected on a computer without multiple processors, you can
allow the driver to load without adversely affecting performance.
Selecting a PCI Hot Plug Module (If Required)
Computers that support PCI Hot Plug technology allow storage adapters and network boards to be inserted and removed while the computer is on. If the
installation program does not detect a PCI Hot Plug support module, your computer probably does not support the PCI Hot Plug technology.
Selecting a Storage Adapter
A storage adapter provides a link between the computer and one or more storage devices. The storage adapter requires a software driver called a host adapter module (HAM) in order to communicate with the computer (host). Storage devices require a separate driver called a custom device module (CDM).
NOTE:.DSK drivers are no longer supported. Instead, NetWare uses the enhanced capability of NetWare Peripheral ArchitectureTM (NWPA). NWPA requires a HAM and a CDM.
Because a single adapter can control more than one type of storage device, your computer might require only a single HAM, even though it can have more than one type of storage deviceand therefore multiple CDMs. The installation program auto-detects many types of storage adapters, such as IDE and SCSI adapters. If your storage adapter is not detected, select the appropriate driver from the list of available drivers provided with NetWare or add a new driver from a diskette. HAMs can be obtained from the storage adapter manufacturer.
Editing the Properties of the Storage Adapter (If Required)

HINT: You can disable Compatibility Mode by removing the LOAD SCMD command from the servers AUTOEXEC.NCF file. When IPX Compatibility Mode is disabled, the server will process only IP packets. Applications that require IPX will not function properly.

About IPX

Novells traditional protocol, Internetwork Packet Exchange (IPX), lets you continue using IPX-based applications. If IPX, but not IP, is installed on your server, it will actively process IPX packets and ignore packets using other protocols, such as IP. During the installation program, existing IPX frame types will be detected. The installation program will detect one of the following conditions. A single IPX frame typeIf a single frame type is detected, it will be installed. Multiple IPX frame typesIf detected, you will be prompted to choose the frame types that you want to install. No IPX frame typesIf no frame types are detected, Ethernet_802.2 will be installed by default.

Using Both IP and IPX

If you have network clients or applications that require IPX and IP, you can install both protocols. Both protocols can be bound to a single network board. When selected, both IP and IPX protocols are actively supported. The server will process IP requests using IP, and it will broadcast and reply to IPX requests using IPX.
Setting Up Domain Name Service
The IP protocol identifies computers and systems by their assigned IP addresses, such as 123.45.56.89. Domain Name Service (DNS) allows a specific server on the network to maintain a list of simple, readable names that match IP addresses. Applications (or protocols) that require IP addresses rather than names can use a DNS server to translate from one form to another.
HINT: If this server will not be available to the Internet, you can skip this screen and ignore any associated error messages.
If you want this server to be available to the Internet, you must enter the following: Host ComputerThe simple, readable name on the DNS server that matches this NetWare servers name (or the name that you have bound to the network board).
HINT: Set up the host computer name on the DNS server to use the NetWare server name.
Domain NameThe hierarchical name that represents the organization of your network, such as acme.com. Domain Name ServerThe IP address of the DNS server that maintains the list containing this NetWare servers simple, readable name and IP address. For more information, contact your network administrator or Internet service provider.
Configuring a NetWare Server as a DNS Server (Optional)
In addition to standard services, a NetWare server can be configured to provide DNS services. The DNS Server setup is done after completing the NetWare server installation.
Setting the Server Time Zone

The server time and time zone are important in order to synchronize network events. Advanced time synchronization settings are available during the Customize section of the installation.
Setting Up Novell eDirectory
Novell eDirectory provides global access to all networking resources. eDirectory allows users with the proper access rights to log in to the network and view and access network resources.
Network resources such as servers and printers are presented hierarchically in an eDirectory tree. Users log in to the eDirectory tree with a single login name and password instead of logging in to specific servers.
Choosing the Type of eDirectory Installation
To set up eDirectory, you must choose one of the following options: Install the server into an existing eDirectory tree Create a new eDirectory tree Before completing this task, you should understand the concepts relating to eDirectory trees, containers, and context. Tree NameThe top level of the available network resources and must be unique from other eDirectory tree names on the network. ContainersMuch like subdirectories, containers contain network objects. The server can be installed into two types of container objects: Organization (O) and Organizational Unit (OU). ContextThe context, much like DOS directory paths, denotes the full path of a network object in the eDirectory tree. For example, a NetWare server might be installed into an Organizational Unit (OU) named Sales under the Organization (O) named Acme. The context would be denoted as OU=Sales.O=Acme or Sales.Acme.
Install the Server into an Existing eDirectory Tree
Installing your server into an existing eDirectory tree incorporates the server into your network. The server can be installed in any Organization (O) or Organizational Unit (OU) container in the eDirectory tree where you have the Supervisor right. You can create containers during the installation program. You will be required to log in and provide the context, username, and password for the user with the Supervisor right to the container.
IMPORTANT: If this is the first NetWare 6 server to be installed into an existing
eDirectory tree, you should have already completed the Network Preparation section of the NetWare Deployment Manager utility. NetWare Deployment Manager (NWDEPLOY.EXE) is located on the NetWare 6 Operating System CD and is run from a Windows workstation. If you have updated the eDirectory tree on all servers but have not yet prepared the network for NDS 8, you will be prompted to modify the schema. When prompted, you must provide the administrator name and password for the entire eDirectory tree.
Creating a New eDirectory Tree
Create a new tree if you are creating a new network or if this server requires a separate eDirectory tree. The resources available on the new tree will only be available to users logged in to the new tree.

Single IP Address Configuration
The following figure shows the Port Resolver dialog in Single IP Address configuration mode. This example shows all four of the services (or service groups) managed by Port Resolver, namely, NetWare Enterprise Web Server, Apache-based Services (NetStorage, NetWare Web Access, and NetWare Web Search), Novell iFolder Storage Services, and iPrint/NDPS.
Figure 1 Single IP Address configuration mode
In Single IP Address configuration mode, the Port Resolver sets the IP address and host name fields to the servers primary IP address and host name and disables these fields. The non-secure and secure port number fields are
enabled and set to default values. Services are defaulted to their preferred port configurations unless a particular port number is already assigned to another service. If the preferred port number is already used, the Port Resolver sets the port number to a secondary default. In Single IP Address configuration mode, the Port Resolver assigns preferred port numbers based on the following priorities: 1. If a service has been previously installed, and is not being reinstalled, the Port Resolver displays its configuration and disables the configuration fields. In the case of Apache-based Services, even if one or more services are being reinstalled, the Port Resolver does not allow the previous configuration to be changed. This prevents a service that is being installed from changing the configuration of a service that has already been installed. 2. If the user selects to install iPrint/NDPS and checks the Reserve ip address:secure port to use for secure printing check box, the Port Resolver reserves port 443 on the primary IP address; it does not allow it to be assigned to any other service. The IP configuration of the iPrint/ NDPS service cannot be configured during the installation, so it cannot be assigned a different IP address or port number. If another service is assigned port 443 on the primary IP address, the user will not be able to enable secure printing on the server while the other service is running. 3. If the user selects to install NetWare Enterprise Web Server, the Port Resolver assigns it ports 80 and 443. These are the standard http and https ports for web servers. If port 443 has been reserved for the iPrint/NDPS service, the Port Resolver uses a secondary default for the secure port number. 4. If the user selects to install any of the Apache-based Services, the Port Resolver assigns them ports 80 and 443, if these ports are not already assigned. If the Port Resolver has already assigned them as the default ports for another service, it uses secondary default port numbers for the Apache-based Services. 5. If the user selects to install Novell iFolder Storage Services, the Port Resolver will only assign it ports 80 and 443 if it is the only service managed by the Port Resolver that the user has selected to install.

You can decide how the NetWare server appears to Windows workstations by configuring the NNFAP Server Name, NNFAP Server Comment, and Unicode settings.

NNFAP Server Name

The name specified in the NNFAP Server Name field displays as the server name when Windows workstations without Novell Client software browse the network You can change the name but it must be different than the NetWare Server name and no longer than 15 characters. The default NNFAP Server Name is the NetWare server name with an added underscore (_) and a W. For example, a NetWare server named SERVER1 defaults to a NNFAP server name of SERVER1_W.

NNFAP Server Comment

The text in the NNFAP Server Comment field displays when viewing details of the NNFAP server from a Windows workstation.

Enabling Unicode

When enabled, this command enables Unicode characters (used in doublebyte languages). To support Unicode, an additional file named UNINOMAP.TXT must be created and saved in the SYS:\ETC directory.
When UNICODE is enabled, 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:

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.
Selecting an Authentication Method for Windows Workstations
Select one of the following: If users will authenticate using NDS, select Local. If users will authenticate using a Domain, select Domain. For Windows users, there are two types of authentication methods available with Novell Native File Access: Local and Domain. Local authentication requires a simple password to log in to a NetWare server, but a simple password is not required for Domain authentication.

Local Authentication

The server running Novell Native File Access Protocol 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.
Workgroup Name: The domain or workgroup that the server will belong to. In this case, Workgroup and Domain are interchangeable. WINS Address: Address of WINS server to be used to locate the primary domain controller (PDC), if the PDC and server running Novell Native File Access Protocols 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 Authentication

A simple password is not required for domain authentication. Since the password is kept on the Windows domain controller, it is not possible to use Windows native Change Password feature to change the password. Instead, you must use 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.

PDC Is on Same Subnet

Indicates that the PDC is on the same subnet.
Specify PDC Using DNS or WINS
Select this option to use DNS or WINS to specify the primary domain controller.

PDC Name

A PDC server name and static IP address are needed if the PDC is on a different subnet. This option 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 Protocols software will not be able to contact the PDC.
Selecting IP Addresses to Service Windows Workstations
Although we recommend that you enable the CIFS protocol on all IP addresses, you can specify which IP addresses will respond to CIFS protocol requests.
Specifying Share Points for Windows Workstations
Any volume or directory on the server can be specified as a shared point and made accessible via the Network Neighborhood or My Network Places. If no share points are specified, then all mounted volumes are displayed.

Directory

The path to the server volume or directory which becomes 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

The name by which the sharepoint is displayed to Windows computers. For example, if you enter Lots of Pics as the sharename associated with VOL1\GRAPHICS, then Windows workstations browsing the network see "Lots of Pics" instead of "VOL1\GRAPHICS."

User Data

Enter the path to the directory where you want the iFolder user data to be stored on the server.

Admin Names

Enter the names of all the administrators who need rights to modify iFolder user account information via the Server Management Console. If you are entering more than one name, separate the usernames with a semicolon (;). For example, if you wanted users JSmith and Admin to have rights to administer the Server Management Console, you would enter admin;jsmith.

Network Domain

Enter the IP address or the DNS name of your iFolder server.
Install Novell NetStorage
Novell NetStorage provides simple Internet-based access to file storage and serves as a bridge between a company's protected Novell network and the Internet. It allows users secure file access from any Internet location, with nothing to download or install on the user's workstation. Files and folders on a Novell network can be accessed using either a browser or Microsoft Web Folders.
DNS Name or IP Address of Primary eDirectory Server and Context
Specify the IP address or DNS name of a server in your eDirectory tree that has the master replica or a read/write replica of eDirectory. The Primary eDirectory Server URL is required for NetStorage to function properly. This does not necessarily have to be the IP address or DNS name of the server where NetStorage is to be installed. When a user attempts to log in, NetStorage searches the eDirectory database on the server you specify for the User object. If the User object is found, NetStorage attempts to authenticate the user to eDirectory. If you know the eDirectory context for the users that will use NetStorage, you can add that context to the URL by inserting a colon (:) between the IP address or DNS name and the eDirectory context. The context is optional. If no context is specified, NetStorage searches the entire eDirectory tree on the primary eDirectory server for User objects. For example, if the IP address of the server is 127.0.0.1 and the eDirectory context for your users is Personnel, then you would add 127.0.0.1:personnel to the field.
DNS Name or IP Address of Alternate eDirectory Server and Context (Optional)
This optional text box is where you specify alternate IP addresses or DNS names of other servers in your directory tree that have at least read/write eDirectory replicas. You can add two alternate eDirectory server URL and context settings. These alternate settings can be used in the event that eDirectory authentication cannot be accomplished using the primary eDirectory server URL and context. The alternate URL and context settings are optional, but can help provide users with an additional level of access to NetStorage.

1 At the NetWare server system console, enter XMLCONFIG -EXPORT
volume_name:\websphere\migrate.xml adminNodeName NodeName
NOTE: If you installed WebSphere to a different directory, specify that directory.
2 Complete the upgrade to NetWare 6. 3 After the upgrade, continue migrating the applications by following the
instructions in "Migrating from WebSphere to Tomcat in Getting Results with Novell Web Services.
Preparing Servers Running ZENworks for Server 2 (Conditional)
If the server is running ZENworks for Servers 2, you must install ZENworks for Servers 2 Support Pack 1 prior to upgrading the server to NetWare 6.
ZENworks for Servers 2 Support Pack and related information can be obtained from Novell Technical Support (htttp://support.novell.com).
Verify a Valid DOS Partition
Your NetWare server uses the DOS partition to start the computer and load NetWare. Many of the existing NetWare startup files will be replaced with new NetWare 6 files. In addition, the DOS partition must exceed the minimum amount of available space to accommodate new NetWare 6 files. If the DOS partition does not have enough available space, you cannot upgrade the server. You must create a new DOS partition and install a new server. See Setting Up NetWare 6 on page 27.
HINT: If your computer does not meet the minimum requirements, you might try using the Novell Migration Wizard utility to migrate data to another computer. For more information, see www.novell.com/documentation.
Access the Installation Files
NetWare 6 can be upgraded from the servers local CD drive or from installation files located on the network. To access the NetWare 6 installation files, complete the following steps.
1 Insert the NetWare 6 Operating System CD and boot the computer. 2 Complete one of the following:
If the computer boots from the CD, follow the on-screen prompts and skip to Selecting the Language and Accepting the License Agreement on page 36. If the computer does not boot from the CD, continue with the following steps.
3 Boot your computer with DOS 3.3 or later. 4 Access the NetWare 6 Operating System CD.