User Guide

412 System Messages
System Messages
103-000150-001
August 29, 2001
Novell Confidential
Manual 99a38 July 17, 2001
NWCONFIG-X-394: No LAN drivers are currently loaded. Installation from a remote
server requires access to the network. A LAN driver must be loaded and bound to a
protocol stack on this server.
Source: NWCONFIG.NLM
Explanation: A network connection is required to install from a remote server. Without a
LAN driver being loaded and bound to a protocol, a network connection
cannot be created.
Action: Load a LAN driver and bind it to a protocol.
NWCONFIG-X-401: Error executing file name. The file cannot be loaded remotely.
Source: NWCONFIG.NLM
Explanation: This error could result from I/O errors, file corruption, or a bad network
connection, or the error could occur because this file must be loaded on the
console.
Action: Verify that this file can be loaded remotely. See Resolving File I/O Errors in
the Traditional File Services Administration Guide.
NWCONFIG-X-402: An attempt to establish a server-to-server session failed. A
server-to-server session must exist in order to access the remote server specified in
the installation source path: path.
Source: NWCONFIG.NLM
Explanation: The attempt to establish a server-to-server connection failed. Possible reasons
follow: wrong password for the specified user, this server is unable to see the
other server (router problems, or the other server is down), or this server is not
connected to the same network with the same protocols as the other server.
Action: Make sure that the other server is up and that this server can see it. Make sure
that the user name and password are correct and that both servers can
understand one another.
NWCONFIG-X-403: ISSLIB.NLM (Install Server To Server I/O Library NLM) must be
loaded in order to access the remote server specified in the installation source path:
path.
Source: NWCONFIG.NLM
Explanation: The attempted operation requires that the file ISSLIB.NLM be loaded. Verify
that this file exists, is executable, and is in the server's search path.
Action: Check for the possible problems listed above. See Resolving Volume I/O
Errors in the Traditional File Services Administration Guide.