Client-server connectivity troubleshooting guide

Client-server Connectivity Troubleshooting Guide

Both the client and the server contains a built in HTTP server. Server side HTTP server serves requests generated by the client related to user actions. Client side HTTP server receives requests from the server related to server side actions/events such as task progress, state change etc.

Ports

Port 4380 and 4381 – used for bi-directional communication between the client and the server.
We only configure the value of the main port (4380) in the vmoptions or on the GUI server browser. The other port is automatically set to be the next port (eg. if we set the port to 1000, the port 1001 would automatically be used as well)

Troubleshooting

  1. Check IP and port configuration 
    • On the gui under the server manager. It is the first screen on the client before connecting and logging into a server.
    • And optionally in the server vmoptions file where the default parameters are:
      -Domixon.server.host=localhost
      -Domixon.server.port=4380
  2. For testing the server from a locally installed client
    • Set up IP/port address to 0.0.0:4380 to allow connections through any physical network device configured on the server (eg.: wifi device)
  3. Telnet from the server machine
    Using either “localhost” or 127.0.0.1 as one of them might not work due to platform or configuration related issues. For Windows you might need to first enable telnet. Click here for details.

    • Enter the below commands into a terminal or command line window:
      telnet 127.0.0.1 4380
      GET /
    • Expected result:  any HTML content. It fails if you receive a flood of incomprehensible characters
    • Enter the below commands into a terminal or command line window:
      telnet localhost 4380
      GET /
    • Expected result:  any HTML content It fails if you receive a flood of incomprehensible characters.
    • If both of the above fails: Most likely the Omixon server is not running.
  4. Check the currently running server from a web browser on the server
    (using either “localhost” or 127.0.0.1  as one of them might not work due to platform or configuration related issues)

    • Enter the below commands into a terminal or command line window:
      0.0.1:4380/public/workingDir
    • Expected result: installation folder of the currently running server executable
    • Enter the below commands into a terminal or command line window:
      localhost:4380/public/workingDir
    • Expected result: installation folder of the currently running server executable
    • Validate that the correct Omixon server instance is running if you have more than one installed.
  5. Ping the server from the client machine
    • Enter the below command into a terminal or command line window:
      ping (server IP)
    • Note that “ping” might be disabled so it is not certain that it will yield a response.
  6. Telnet from client machine
    • Enter the below commands into a terminal or command line window:
      telnet (server IP address) 4380
      GET /
    • Expected result: any HTML content. It fails if you receive a flood of incomprehensible characters.
    • If it fails: if the ping worked, then it might be a firewall issue.
    • If it fails and the ping didn’t work: Check if there is any other service running on the server machine and try to connect to that from the client machine. This could be any 3rd party service.
  7. Check the currently running server from a web browser remotely
    • Enter the below commands into a terminal or command line window:
      (server IP address):4380/public/workingDir
    • Extra step: Might provide additional information on the installation directory.