The file service components in OES are generally compatible. However you cannot run Novell Samba on the same OES server as Novell AFP, Novell CIFS, or Domain Services for Windows, which is not reviewed as a file service, but includes an alternative Samba file service instead of Novell Samba.

18.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 18.2, Planning for File Services.

18.1.2 FTP Services

OES 11 SP3 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 Novell FTP Server pattern in the OES 11 SP3 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 11 SP3.

18.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 Novell NCP Server for Linux provides the rich file services that Novell is known for. Windows and Linux users who run Novell Client software can access data, manage files and folders, map drives, etc., using the same methods as they do on NetWare servers.

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.

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

Of course, the same files can also be accessed through other OES file services (such as NetStorage) that connect to NSS volumes.

18.1.6 Novell CIFS

The Novell 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 Novell Client (see Figure 18-4).

The following table explains the information illustrated in Figure 18-6.

Table 18-6 iFolder Access

Access Methods

Authentication/File Encryption

Novell iFolder 3.9.2 Services

Linux, Mac, and Windows workstation users who have the Novell iFolder Client installed can access and modify their files in one or more workstation folders. Changes are automatically synchronized with the iFolder 3.9.2 Enterprise servers.

A Web interface lets users access their files from any computer with an active network or Internet connection.

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

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

Files can be encrypted for transport using SSL connections (HTTPS).

Slave servers can be added as needed, providing the ability to dynamically grow iFolder services without disrupting users.

Local and network copies of each file are automatically synchronized by the Novell iFolder Client and Server pieces.

Files on the OES server running Samba are accessed and maintained with the HTTP-WebDAV protocol.

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

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

Of course, the same files can also be accessed through other OES file services (such as NetStorage) that connect to Linux volumes.

Samba is an open source initiative. In addition to Linux support, Samba initiatives provide support for other platforms such as Apple Computer’s operating systems. More information is available on the Web.