KNAN22265-E

Verification of the IM configuration failed because a remote connection was not possible.

S:

Cancels processing.

O:

• An attempt to connect monitored host failed.

• The collection of log files did time-out.

  If this message appears at startup of a remote log-file trap and the OS of the monitored host is UNIX, check the following items, and then restart the remote log-file trap.

  • Is communication with the monitored host possible?

  • Has the remote communication type for the monitored host name been set correctly?

  • Is the SSH server running on the monitored host?

  If no error is found by checking the above items, make sure that the SSH connection has been configured correctly.

  If this message appears at startup of a remote log-file trap and the OS of the monitored host is Windows, check the following items, and then restart the remote log-file trap.

  • Is communication with the monitored host possible?

  • Has the remote communication type for the monitored host name been set correctly?

  • Has the number of connections exceeded the maximum for Windows?

  If no error is found by checking the above items, make sure that the NetBIOS (NetBIOS over TCP/IP) connection has been configured correctly.

  If this message appears at startup of a remote event-log trap, check the following items, and then restart the remote event-log trap.

  • Is communication with the monitored host possible?

  • Has the password for the user who logs in to the monitored host expired?

  • Has the remote communication type for the monitored host name been set correctly?

  • Is the WMI service running?

  If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

  If the above methods cannot resolve the problem or if a timeout occurred during collection of log files, check the following items:

  • Check the load on the system.

  • Make sure that the host is running.

  • Check whether the number of connections exceeds the maximum.

  • Make sure that the IM host account has been specified correctly in the system common settings.

• Remote communication settings have not been configured.

  Configure the remote communication settings.

• Authentication failed.

  If this message appears at startup of a remote log-file trap and the OS for the monitored host is UNIX, check the following item:

  • Has SSH authentication been configured correctly?

  If no error is found by checking the above item, make sure that the SSH connection has been configured correctly.

  If this message appears at startup of a remote log-file trap and the OS for the monitored host is Windows, check the following item:

  • Are the user name, password, and domain name specified correctly in the System Common Settings or Remote Monitoring Settings window?

  If no error is found by checking the above item, make sure that the NetBIOS (NetBIOS over TCP/IP) connection has been configured correctly.

  If the above methods cannot resolve the problem or if a timeout occurred during collection of log files, check the following items:

  • Are the user name, password, and domain name specified correctly in the System Common Settings or Remote Monitoring Settings window?

  • Is DCOM configured correctly on the monitored host?

  • Is DCOM configured correctly on the JP1/IM - Manager host?

  If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

• Acquisition of an SSH private key failed.

  Make sure that a private key exists on the manager host.

• Creation of the jcfallogtrap process failed.

  Check the IM host account specified in the system common settings.