16.1 Overview of File Services

The file service components in OES include the following:

FTP Services: Lets users securely transfer files to and from OES servers.
NetWare Core Protocol: Provides NetWare Core Protocol (NCP) access to NCP volumes (including NSS volumes) that you define on OES server partitions.
NetStorage: Provides network and Web access to various file services through common file service protocols, such as CIFS.

The NetStorage server doesn’t actually store files and folders. Rather, it provides access to other file services that support the native TCP/IP protocol.
AFP: Provides native Macintosh access to files stored on an NSS volume on an OES server.
CIFS: Provides native Windows (CIFS and HTTP-WebDAV) access to files stored on an NSS volume on an OES server.

16.1.1 Using the File Services Overviews

Each graphical overview in the following sections introduces one of the OES file service components. If visual presentations help you grasp basic concepts, continue with the following overviews. If you prefer to skip the overviews, go to Section 16.2, Planning for File Services.

16.1.2 FTP Services

OES offers a level of integration between eDirectory and Pure-FTP that allows users to authenticate to eDirectory for FTP access to the server. You simply select the OES FTP Server pattern in the OES installation, then make sure the users needing access are LUM-enabled and have access rights to the areas on the server they need to use. You can also migrate an existing FTP server configuration from a NetWare server to OES. For migration instructions and a brief FAQ, see Migrating FTP to OES 2018 SP3 in the OES 2018 SP3: Migration Tool Administration Guide.

For documentation on Pure-FTP, visit the Pure-FTP Web site.

16.1.3 NetWare Core Protocol

NetWare Core Protocol (NCP) is the technology beneath many of the network services for which NetWare is famous.

In OES, NCP is also available on Linux. The OES NCP Server for Linux provides the rich file services that Novell is known for. Windows users who run Client for Open Enterprise Server software can access data, manage files and folders, map drives and so on, using the same methods as they do on NetWare servers.

Figure 16-1 illustrates the basics of NCP file services. For more information on how NCP can help you manage access to network resources, see Access Control and Authentication.

Figure 16-1 NCP Services for Linux and NetWare

The following table explains the information illustrated in Figure 16-1.

Table 16-1 NCP Access

Access Methods	Authentication	NCP Services
Access is through an NCP client—specifically, the Client for Open Enterprise Server.	All file service access is controlled by eDirectory authentication.	Files are stored on NetWare or NCP volumes that the administrator has created. The same core set of NetWare file attributes are available on both Linux and NetWare.

Access Methods

Authentication

NCP Services

Access is through an NCP client—specifically, the Client for Open Enterprise Server.

All file service access is controlled by eDirectory authentication.

Files are stored on NetWare or NCP volumes that the administrator has created.

The same core set of NetWare file attributes are available on both Linux and NetWare.

16.1.4 NetStorage

NetStorage makes network files available anywhere, any time.

Common Network File Storage Problems

Network file access is often confusing and frustrating to users, as illustrated in Figure 16-2.

Figure 16-2 Common Network File Storage Problems

The following table explains the information illustrated in Figure 16-2.

Table 16-2 NetStorage Access Solutions

Access Methods	Authentication	Target File Systems	Solution: NetStorage
Browser or PDA access is critical to those who must travel. However, access method support varies widely among file service providers.	Authentication helps protect information assets, but having diverse authentication methods leads to frustration and lost productivity.	Having diverse file storage services only adds to the complexity and confusion.	NetStorage ties all of these issues together with an easy-to-administer, easy-to-use solution.

NetStorage

NetStorage on OES provides local and Web access to files on many systems without requiring the Client for Open Enterprise Server (see Figure 16-3).

Figure 16-3 How NetStorage Works on OES

The following table explains the information illustrated in Figure 16-3.

Table 16-3 NetStorage on Linux

Access Methods	Authentication	NetStorage Server	Target Servers
Users have read and write access to files from Windows Explorer: Enabled by the HTTP protocol with WebDAV extensions. Browsers: Users can access files directly by connecting to the NetStorage server. PDAs: PDA users with network connections can access their files as well. Access is granted through login script drive mapping (NCP server required) or through Storage Location Objects.	File service access is controlled by LDAP-based authentication through the eDirectory LDAP server. Although shown separately, eDirectory could be running on the OES server.	The NetStorage server receives and processes connection requests and provides access to storage on various servers on the network.	NetStorage on Linux can connect eDirectory users to their files and folders stored in the following locations: Windows workgroup shares (CIFS shares) Linux POSIX volumes through an SSH connection. Linux volumes can also be made available as NCP volumes. Management of NSS volumes on OES through NetStorage requires SSH access to the server. See When Is SSH Access Required?.

Access Methods

Authentication

NetStorage Server

Target Servers

Users have read and write access to files from

Windows Explorer: Enabled by the HTTP protocol with WebDAV extensions.
Browsers: Users can access files directly by connecting to the NetStorage server.
PDAs: PDA users with network connections can access their files as well.

Access is granted through login script drive mapping (NCP server required) or through Storage Location Objects.

File service access is controlled by LDAP-based authentication through the eDirectory LDAP server.

Although shown separately, eDirectory could be running on the OES server.

The NetStorage server receives and processes connection requests and provides access to storage on various servers on the network.

NetStorage on Linux can connect eDirectory users to their files and folders stored in the following locations:

Windows workgroup shares (CIFS shares)
Linux POSIX volumes through an SSH connection.

Linux volumes can also be made available as NCP volumes.

Management of NSS volumes on OES through NetStorage requires SSH access to the server. See When Is SSH Access Required?.

16.1.5 AFP

The AFP service lets users on Macintosh workstations access and store files on OES servers with NSS volumes (see Figure 16-4).

Figure 16-4 How Novell AFP Works

Table 16-4 AFP Access

Access Points	Authentication
eDirectory users on Macintosh workstations have native access to NSS volumes on the OES server.	All file service access is controlled by LDAP-based authentication through the eDirectory LDAP server.

16.1.6 CIFS

The CIFS service lets users on Windows workstations access and store files on OES servers with NSS volumes without installing any additional software, such as the Client for Open Enterprise Server (see Figure 16-4).

Figure 16-5 How Novell CIFS Works for eDirectory Users

Table 16-5 CIFS Access for eDirectory Users

Access Methods	Authentication
eDirectory users on Windows workstations have two native Windows file access options: CIFS Client Access: Windows Explorer users can access and modify files on the OES server just as they would on any workgroup server share. Web Folder: Users can create Web Folders in Windows Explorer or Internet Explorer. Files on the OES server are accessed and maintained with the HTTP-WebDAV protocol.	All file service access is controlled by LDAP-based authentication through the eDirectory server.

Figure 16-6 How CIFS Works for Active Directory Users

Table 16-6 CIFS Access for Active Directory Users

Access Methods	Authentication
Active Directory users gain access to CIFS file services as follows: The user presents a Kerberos ticket obtained from Active Directory to the CIFS server. The CIFS server validates the ticket with Active Directory. After validation, files on the OES server are accessed and maintained through the CIFS protocol.	All CIFS file service access is controlled by Kerberos-based authentication and Active Directory.