NS3000/iX Operations and Maintenance Reference Manual (36922-90042)

Chapter 5 67
Common Network Problems
Command Errors
the IP address of the remote node configured in the NS
Configuration file.
• All virtual terminals on the remote node are already in use, which
means there are no remote resources available to establish a remote
session. This would cause a failure in a REMOTE HELLO or a DSCOPY or
RPMCREATE that tried to automatically log on to a session.
• Someone has exclusive access to the specified line or the user
requested exclusive access to a line that is already in use.
• Someone is exclusively accessing a server program. For example,
someone is executing the STORE command or a SYSGEN system
backup on DSSERVER.NET.SYS.
• There is a hardware problem—the communications device is not
responding correctly.
Line Closing Errors
There are several reasons why a DSLINE command for closing a
communications line might be rejected. The following list summarizes
the likely causes of line closing failures:
• The user made a syntax error in the DSLINE command.
• The user specified an erroneous
nodename or envid in the DSLINE
command. The nodename must match the one configured with
NMMGR. Make sure that all users know the correct nodenames. You
may want to post a map with the configured nodenames for all the
nodes on the network.
• The remote node may not be operational.
• There is a hardware problem — the communications device is not
responding correctly.
NMS Utility Errors
A file system error (FSERR) may have occurred while attempting to
access the configuration file. Try to access the configuration file under
the same user ID using NMMGR. Use the NMMGR Error screen to find
out what the underlying FSERR is. A complete listing of NMS error
messages is available in Using the Node Management Services (NMS)
Utilities. Correct the problem and retry.