Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

I'm having problems connecting my client to the Optimal Trace server

I'm having problems connecting my client to the Optimal Trace server


I'm having problems connecting my client to the Optimal Trace server, what steps can I take to determine the cause of the problem?


If you are experiencing problems connecting to the Optimal Trace server, check the following in the order in which they appear. The most likely issues appear first:

1. In Optimal Trace client, check the machine name you have specified for the Optimal Trace Server in 'Options > General Options > Server Settings' is correct.

2. Check that you can 'ping' the machine specified in 1 above. To do this, from a command shell, type 'ping machinename'. The output you get from ping should be a series of uninterrupted replies, e.g.

    Pinging opitmaltraceserver .optimaltrace.com [] with 32 bytes of data:

    Reply from bytes=32 time

    Reply from bytes=32 time

    Reply from bytes=32 time

    Reply from bytes=32 time

    Ping statistics for

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

If the response from ping is not similar to the above, you have a serious network problem and you need to consult with your network system administrator.

If ping is ok, do a 'tracert' call and make sure its ok also:

    C:\>tracert opitmaltraceserver

you should see something like:

    Tracing route to opitmaltraceserver.optimaltrace.com []

    over a maximum of 30 hops:


    Trace complete.

Note: Also check that you can do a 'ping' and 'tracert' from the Server Machine back to the Client machine using the same process as above. Its more likely that there is a firewall running on your Server Machine, so its very important to do this reverse check also.

3. Check there are no firewalls running on either your client or server machines. For example, upgrading to Windows XP SP2 will install a firewall on your machine that you must manually turn off. To check if a firewall is running locally, go to 'Start > Control Panel > Windows Firewall' and make sure its turned off. Do this on both machines.

A good firewall check is to check you can 'telnet' from both the client to the server machine, and from the server machine to the client machine. You can do this as follows:

  • start Optimal Trace Server on the server machine
  • start Optimal Trace Enterprise on the client machine
  • on the client machine, run a 'cmd' prompt and type 'telnet 5456'. You should be presented with a blank screen. Type 'ctrl-]' to get a telnet prompt, and type 'quit' to exit telnet.
  • on the server machine, run a 'cmd' prompt and type 'telnet 6100'. Again you should be presented with a blank screen. Type 'ctrl-]' to get a telnet prompt, and type 'quit' to exit telnet.

4. Check the Optimal Trace log files for both the client and the server. The clients log file is called 'Optimal Trace Enterprise_log.log', and is located in your Optimal Trace Enterprise 4.0 installation directory. The Server log file is called 'Optimal Trace Enterprise Server_log.log' and is located in your Optimal Trace Server installation directory.

5. Check your Optimal Trace Server log file. If you see log entries usch as:

ConnectionException: Connection Timed Out: this is mostly caused by a firewall (or somebody pulled the network plug)

ConnectionException: Connection Refused: nothing is running on that port (or sometimes this can be caused by a firewall)

ConnectionException: No Route to Host: misconfigured network (e.g. bad DNS ) , or a machine down along the way.

Some firewalls block ports 1 to 1024, and as we have no control over which ports we use (currently) the Server can sometimes try to use one of these ports and get refused the connection.

If the output in the start of your log files indicate a 'Port already in use' messages, the most likely cause of this problem is that some other process is 'hijacking' the Optimal Trace ports.

The reason this happens is that some windows process randomly pick ports to use, and unfortunately that random range includes the port numbers that we use, and as these processes start before Optimal Trace, they can use the Optimal Trace ports.

We've changed our default ports to be much higher port numbers for the next Optimal Trace 4.0 release, so hopefully this shouldn't happen as often (if ever). For now though, you need to set the Optimal Trace ports to different values, can you do the following:

  • stop Optimal Trace Server
  • edit 'server.properties' in the '\\Program Files\Micro Focus\Optimal Trace\Optimal Trace Server Edition' directory
  • change the rmi_registry_port and rmi_daemon_port values to the following:
    • rmi_registry_port=5456
    • rmi_daemon_port=5460
  • also change commandLinePort to be:
    • commandLinePort=5464
    • save server.properties and restart the Optimal Trace server
    • now, on your client machine, shut down your Optimal Trace Client
    • in your client installation, edit the 'default.properties' file in your Optimal Trace client installation directory
  • find the 'rmi_registry_port' setting and change it to: rmi_registry_port=5456
  • restart Optimal Trace client

Old KB# 10329


Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 17:40
Updated by:
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.