Connection failures between the console and the UIM server

The console client does not successfully connect to the UIM server.

This situation might occur when you are installing the console, making a web browser (HTTP) connection, or making a console request.

The console client might be on a separate TCP sub network from the UIM server host. A firewall or router might be denying access.

You must determine the point of connection failure by performing these steps:

  1. Test whether your personal computer can determine the IP address for YourHost.

  2. Determine whether the personal computer can access the target system by pinging YourHost.

  3. If the ping command is unsuccessful, determine at what point the path fails.

To test whether the IP address can be determined for YourHost

  1. Type NSLOOKUP YourHost.
    • If the IP address was found, the IP address is displayed.

    • If the IP address was not found, an error message is returned.

      If the IP address is not found, the problems may be an incorrect domain name, an incorrect server name, an inappropriate update for name registrations, or an invalid system name request.

  2. Access the system by using the IP address instead of the host name to test the connection. Use the following format:


  3. If the PC cannot connect, review the personal computer and IP configuration and make any needed adjustments.

To determine whether the PC can access the target system

To determine whether the PC can access the target system on which the UIM server is running, type ping YourHost.
  • A successful ping indicates that you can access the target system and provides information about response time for the IP.

  • An unsuccessful ping displays the error Request timed out. An unsuccessful ping might be the result of routers or firewalls between the personal computer and the target system that do not allow ping responses.

  • If the ping fails, you must determine at what point the path fails, as described in the following task.

To determine at what point the path fails

Type tracert YourHost to determine at what point the path fails.

In a successful trace, each line of output indicates the next connection point (hop) to the target. The time for each hop is displayed.

If the trace was unsuccessful, review the trace output to determine where it failed. You will see the error Request timed out after the first unsuccessful hop. Tracert (by default) attempts 30 hops before stopping.

Was this page helpful? Yes No Submitting... Thank you