HP Integrity NonStop H-Series - Manual (Page 162)

B Error Messages
This appendix explains the cause and effect of messages produced by the TCP/IP application
client programs and TN6530. The message descriptions include suggestions on how to recover
from an error. The messages for each application are presented separately and arranged
alphabetically. See the manual describing the mail service you are using for information about
errors that appear when you are sending mail.
Recovering From Errors
You can apply the following general approach to recover from errors you encounter while using
the TCP/IP client programs:
•
Make sure the command you have entered has valid parameters, such as the host name or
address, the user name or ID, or the port number. Some errors result from a simple typing
mistake.
If you have made a typing error, try the command again. If the error is more complicated,
you can ask your system manager for help in locating the problem. If necessary, you can also
contact the system administrator of the remote system.
•
Communication problems that result in socket error messages can occur. These error messages
include an error-reason that is returned from a TCP/IP sockets library routine named error
or from the Guardian file system. To find a full explanation of these errors, refer to the TCP/IP
Configuration and Management Manual, the TCP/IP (Parallel Library) Configuration and
Management Manual, or the TCP/IPv6 Configuration and Management Manual, which
describe the error-reason values in an appendix. The descriptions of file-system errors in
the Guardian Procedure Errors and Messages Manual also explain some error-reason
values you might encounter, as well as the error-number values included in some messages.
•
In some cases, problems occur because the TCP/IP process is no longer running. Ask your
system manager to check whether the TCP/IP process has stopped.
ECHO Error Messages
This subsection describes the ECHO error messages.
Connection Refused
Cause
The remote system is accessible, but it has no active ECHO server.
Effect
Your request for an ECHO connection terminates.
Recovery
Contact the system administrator of the remote system to determine whether an ECHO server
should be available.
connection timeout
Cause
No reply has been received from the remote system within the TCP/IP system-defined timeout
interval.
Effect
Your ECHO connection terminates.
Recovery
Contact the system administrator of the remote system to determine why the ECHO server is not
responding, or try again later.
Name does not resolve to supplied parameters.
162 Error Messages