Manage NetWare server connections and authentication
Most administrative, printing, and file system functions require that you
have an authenticated connection from iSeries™ to a NetWare server
that runs the NetWare Enhanced Integration NLM. You can think of this as the iSeries user's logging
on to the server.
To make this connection, you must have a NetWare user name and password.
In most cases the NetWare user name and the iSeries user profile should be the same. When
they are different, you identify the NetWare user name that you want to use
for the connection in one of these ways:
- By specifying it when you manually start the connection.
- By specifying it in the NetWare authentication entry.
You can establish connections in these three ways:
- Directly by manually starting a connection with
the STRNTWCNN command. This connection is active only until the user signs
off (whereas setting up an authentication entry automates this process). Use
this method when you need to specify:
- The iSeries user profile authorized to use the connection (for example, when
the NetWare user name and the iSeries user profile are different).
Only
jobs running under the specified iSeries user profile name can use the connection.
- The job that is authorized to use the connection.
The connection can
be used by either the current job or by any job running under the specified
user profile name.
- The type of authentication to be performed.
For example, NetWare backup
services require a separate authentication in addition to a normal user login.
- Indirectly by creating an authentication entry for the NetWare Directory Service (NDS) tree that
the server is in. Once you create an authentication entry, iSeries automatically
starts a connection when necessary. Using authentication entries greatly enhances
usability.
- Indirectly by using iSeries user enrollment, which has iSeries automatically create the authentication entries. Again the authentication
entry enables iSeries to start connections automatically.
You can also display and work with connections and authentication entries
in these ways: