The file service components in OES include the following:
Native File Access Protocols: Lets Linux, Macintosh, UNIX, and Windows users access and store files on OES NetWare® servers using their native file access methods.
NetWare Core Protocol: Provides NetWare Core Protocol™ (NCP™) access to NetWare servers and to NCP volumes that you define on OES Linux server partitions.
NetStorage: Provides network and Web access to various Linux, NetWare, and Windows file services.
The NetStorage server doesn’t actually store files and folders. Rather, it provides access to other file services on OES Linux and NetWare servers that support the native TCP/IP protocol.
Novell iFolder 2.1 x: Provides a Web- and network-based repository (Novell iFolder® server) that stores master copies of locally accessible files on the OES server.
Novell Samba: Provides Windows (CIFS and HTTP-WebDAV) access to files stored on an OES Linux server’s file system.
The file service components in OES are all mutually compatible—you can install one or more of them on the same OES server.
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.
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.
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.
NetStorage makes network files available anywhere, any time.
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.
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
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:
Additionally, Linux volumes can also be made available as NCP volumes. |
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.
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.
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.
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.
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.
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.
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
.