KNAK3410-E
Cannot connect to the connection destination host (host-name) or JP1/AJS3 service on the connection destination host. (detailed information = port-number, IP-address)
Connection cannot be established with the connection destination host or the JP1/AJS3 service on the connection destination host. The probable causes are:
-
The JP1/AJS3 service is not running on the connection destination host.
-
The port number definition does not match the port number (defined for jp1ajs3cdinetd) at the connection destination.
-
The connection destination host is not running.
-
The connection destination host is busy.
-
The connection destination host is in a state in which a network connection cannot be established.
-
In the JP1/Base settings at the connection destination, the IP binding method is specified on the receiving side for the physical host. Then, connection is attempted by using an IP address that is not bound to the physical host or any logical host.
-
Available TCP/IP ports are insufficient.
-
ajscdinetd is not running.
-
JP1/AJS3 - Manager of a version that satisfies the request of JP1/AJS3 - Web Console is not installed at the connection destination.
- (S)
-
Cancels processing.
- (O)
-
Correct the error, and then retry.
- If the connection destination host is in a state in which a network connection cannot be established:
-
Check the network environment with the connection destination host. If a firewall is set up between the Web Console server and the connection destination host, check the firewall settings.
- If connection is attempted by using an IP address that is not bound to the connection destination physical host or any logical host:
-
Use a bound IP address to establish a connection, or define jp1hosts information at the connection destination. For details about the definition of jp1hosts information, see the JP1/Base User's Guide.
- If there are insufficient TCP/IP ports:
-
Check the port status, wait until there are fewer ports in the TIME_WAIT status, and then try again. If the user application has made a very large number of calls to the API for JP1/AJS3 - Web Console in a short period of time, revise the number of times the API can be called. If there might be a problem other than the user application (for example, too many applications are using ports), revise the number of applications that can start concurrently and the settings related to TCP/IP ports.