18.6 NCP Implementation and Maintenance

If you have installed the NCP server for OES, eDirectory/Novell Client users can access files on the OES 2 server with no additional configuration.

The implementation information in the following sections can help you get started with NCP on OES 2 servers.

18.6.1 The Default NCP Volume

The NCP Server for OES enables NCP access to NCP and NSS volumes defined on the OES 2 server. When you install the NCP server, the installation creates one NCP volume named SYS: that maps to the /usr/novell/sys folder on the OES server.

This NCP volume contains LOGIN and PUBLIC directories that, in turn, contain a small subset of the files traditionally found on a NetWare server in the directories with the same names.

18.6.2 Creating NCP Home and Data Volume Pointers

Initially, there are no NCP home directories or data volumes available to Novell Clients that attach to an OES 2 server.

For existing eDirectory users: If you want users to have NCP home or data directories on the server, you must decide where you want these directories to reside on the server’s partitions and then create NCP volumes by using the NCPCON utility at the terminal prompt.

For example, if you wanted to create an NCP volume (pointer) named HOME and mount it to the /usr folder on the Linux server, you would enter the following command at the command prompt:

ncpcon create volume HOME /usr

After issuing this command, when a Novell Client attaches to the OES 2 server, the HOME: volume appears along with the SYS: volume created by the installation.

For new eDirectory users: If you create an NCP or NSS volume on the server prior to creating users, then you have the option of specifying that volume in iManager as the location of the home directory for the new users.

IMPORTANT:NCP Volume pointers are always created with uppercase names (HOME:, SYS:, etc.) regardless of the case specified when the volume pointers are created.

18.6.3 Assigning File Trustee Rights

You can use the same methods for assigning file trustee rights on NCP volumes on OES 2 servers that you use when assigning them on NetWare. For example, the Novell Client can be used by anyone with the Access Control right on the volume, or the root user can use the ncpcon utility > rights command at a command prompt to administer NCP trustee rights. See Managing File System Trustees, Trustee Rights, and Attributes on NCP Volumesin the OES 2 SP3: NCP Server for Linux Administration Guide. (The ncpcon rights command is related to but not the same as the rights utility used to manage trustees on NSS volumes.)

18.6.4 NCP Caveats

Starting with OES 2 SP2, cross-protocol file locking (CPL) is enabled by default on all new servers with NCP installed. For more information, see Section 1.5.5, Cross-Protocol File Locking Change.

18.6.5 NCP Maintenance

Because NCP provides Novell Client access to files on NetWare and OES 2 servers, the service is covered by maintenance tasks that apply to file systems on these servers. For information on maintaining file services, see the storage/file systems section in the online documentation.