The following sections are provided only as introductory information. For more information about using NetStorage, see the OES NetStorage Administration Guide for NetWare .
The inherent value of NetStorage lies in its ability to connect users with various servers and file systems. Some connections are created automatically depending on the OES platform where NetStorage is installed. Other connections must be created by the network administrator.
Table 35-3 NetStorage Access Summary
To provide access to file systems not listed in Table 35-3, you must create Storage Location objects in eDirectory. For instructions on creating Storage Locations, see the following:
Novell iFolder access in NetStorage is controlled through the iFolder Storage Provider task in iManager and does not involve Storage Location objects. For more information about the iManager task, see the context-sensitive help in iManager.
If your NetStorage installation has a Novell iFolder link, you must complete all the instructions in Section 35.8, Novell iFolder 2.1 x Implementation and Maintenance before attempting to let users access the service.
Because NetStorage provides access to other file storage systems, the users and groups that access the other systems through NetStorage must be created and granted file and directory access on those systems.
NetWare users must exist in the eDirectory tree where the NetWare server resides and have access rights to the files and directories on the NetWare server.
Windows users must exist on the Windows systems and have the required access rights to the files and directories on those systems.
If your users will access Samba files on an OES Linux server, they must be enabled for LUM and Samba access on the OES Linux server. For more information, see Section 18.1.5, Services in OES Linux That Require Linux-Enabled Access.
IMPORTANT:The usernames and passwords used to authenticate to the NetStorage (OES) server through eDirectory must match the usernames and passwords defined on the target systems.
The OES installation establishes a primary authentication domain for NetStorage. To access any storage location, users must exist somewhere in this primary domain. When it receives an authentication request, NetStorage searches for the username in the context you specified during OES installation and in all its subcontexts.
Authentication to other file systems is often controlled by other authentication domains. For example, you might create a storage location on the OES server that points to a NetWare server that resides in a different eDirectory tree. To access this storage location, users must authenticate to the other tree.
This means that you must specify an additional context in the NetStorage configuration as a nonprimary authentication domain.
When defining a nonprimary authentication domain, you must
Ensure that the username and password in the nonprimary domain matches the username and password in the primary domain.
Specify the exact context where User objects reside. NetStorage doesn’t search the subcontexts of nonprimary authentication domains.
By default, users must reauthenticate each time they access NetStorage in a browser. This is true even if another browser window is open and authenticated on the same workstation.
The reason for this is that persistent cookies are not enabled by default.
Your NetStorage installation can change as your network changes and evolves by providing access to new or consolidated storage locations. For information about the kinds of tasks you can perform to keep your NetStorage implementation current, see the following: