35.1 Overview of File Services

The file service components in OES include the following:

The file service components in OES are all mutually compatible—you can install one or more of them on the same OES server.

35.1.1 Using the File Services Overviews

Each graphical overview in the following sections introduce 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 35.2, Planning for File Services.

35.1.2 Native File Access Protocols

The Novell Native File Access Protocols (NFAP) product lets users on Macintosh, Windows, and UNIX workstations access and store files on OES NetWare servers without installing any additional software, such as the Novell Client™ (see Figure 35-1).

Figure 35-1 Native File Access Protocol Support on NetWare

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

Access Methods

Authentication/File Encryption

NFAP Services

Linux, UNIX, Macintosh, and Windows workstation users can create drive mappings, mount points, etc., to the NetWare server. Then they can access the files as though they were stored on a network server that is native for the respective platforms.

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.

After the service is fully configured, users can log in just as they would to access files on other native systems.

Files are stored on NSS volumes on OES NetWare servers. The same files can be accessed by users on different platforms.

35.1.3 NetWare Core Protocol

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

And now 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 users who run Novell Client™ software can now access data, manage files and folders, map drives, etc., using the same methods as they do on NetWare servers.

Figure 35-2 illustrates the basics of NCP file services. For more information on how NCP can help you manage access to network resources, see Access.

Figure 35-2 NCP Services for Linux and NetWare

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

Access Methods

Authentication

NCP Services

Access is through an NCP client—specifically, the Novell Client.

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.

35.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 35-3.

Figure 35-3 Common Network File Storage Problems

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

Access Methods

Authentication

Target File Systems

Solution: NetStorage

Browser or PDA access is business 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.

Novell NetStorage ties all of these issues together with an easy-to-administer, easy-to-use solution.

Novell NetStorage on Linux

NetStorage on Linux provides local and Web access to files on many systems without requiring the Novell Client (see Figure 35-4).

Figure 35-4 How NetStorage Works on OES Linux

The following table explains the information illustrated in Figure 35-4.

Access Methods

Authentication

NetStorage Server

Target Servers

Users have read and write access to files from

  • Windows Explorer: This is 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.

A Novell iFolder server running on the same server as NetStorage is automatically available through NetStorage to Novell iFolder users.

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

  • The same targets as NetWare (see Figure 35-5) if the NCP server is running

  • Windows workgroup shares (CIFS or Samba shares)

  • Linux traditional volumes through an SSH connection.

Additionally, Linux volumes can also be made available as NCP volumes.

Novell NetStorage on NetWare

NetStorage on NetWare provides local and Web access to files on NetWare and Linux without requiring the Novell Client software (see Figure 35-5).

Figure 35-5 How NetStorage Works on OES NetWare

The following table explains the information illustrated in Figure 35-5.

Access Methods

Authentication

NetStorage Server

Target Servers

Users have read and write access to files from

  • Windows Explorer: This is 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 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.

A Novell iFolder server running on the same server as NetStorage is automatically available to Novell iFolder users. You must configure NetStorage if you want access to the Novell iFolder data stored on other servers.

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

  • NetWare Traditional volumes where users have access rights

  • NSS volumes on either NetWare or OES Linux servers where users have access rights

  • Any administrator-defined NCP volumes created on an OES Linux server

35.1.5 Novell iFolder 2.1 x

Novell iFolder 2.1 x provides a Web- and network-based repository (Novell iFolder server) that stores master copies of locally accessible files (see Figure 35-6).

Figure 35-6 How Novell iFolder Works

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

Access Methods

Authentication/File Encryption

Novell iFolder Services

Linux and Windows workstation users who have the Novell iFolder Client installed can access and modify their files in a workstation folder. Changes are automatically synchronized with the Novell iFolder server.

Windows users who install NetDrive can map a network drive to the Novell iFolder server. Files are modified on the server.

NetStorage is the Web-access solution for Novell iFolder 2.1 x.

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 using a passphrase for transmission to and from storage on the Novell iFolder server.

Local and network copies of each file can be automatically synchronized by the Novell iFolder Client and Server pieces, or users can manually synchronize the files.

Novell iFolder 2.1 x offers other access options and features not shown in this graphic, including

  • Web access to files on other Novell iFolder 2.1 x servers through a seamless integration with NetStorage.

  • Concurrent access to multiple accounts and collaborative access to a single account.

  • Thin-client support.

35.1.6 Novell iFolder 3.1

Novell iFolder 3.1 supports multiple iFolders per user, user-controlled sharing, and a centralized network server for file storage and secure distribution (see Figure 35-7).

Figure 35-7 How Novell iFolder Works

The following table explains the information illustrated in Figure 35-7.

Access Methods

Authentication/File Encryption

Novell iFolder Services

Linux, Macintosh, 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.x 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).

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

Additional overview information is available in Overview of Novell iFolder 3.x in the Novell iFolder 3.x Administration Guide.

For detail about new features in iFolder 3 and to compare differences between iFolder 2.1 x and iFolder 3, see What's New in the Novell iFolder 3.x Administration Guide.

35.1.7 Novell Samba

Samba on an OES Linux server provides Windows (CIFS and HTTP-WebDAV) access to files stored on the OES server (see Figure 35-8).

Figure 35-8 How Samba on OES Works

The following table explains the information illustrated in Figure 35-8.

Access Methods

Authentication

File Storage Services

eDirectory users on Windows workstations have two native Windows file access options (provided their eDirectory accounts have been enabled for LUM and Samba):

  • CIFS Client Access

    Windows Explorer users can access and modify files on the Samba 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 Linux server running Samba are accessed and maintained using 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. See Web Links in the Samba Administration Guide for OES Linux SP2 .