Client-side connection tests

When you run the client-side connection diagnosis tool from the Eclipse IDE, the following tests are run:

Retrieving Development Hub Server IP Address

The test checks whether the remote host's IP address can be established.

The test fails if the client machine cannot resolve the IP address using the name given in the Host name field.

Pinging remote host

The test attempts to ping the server.

If the test fails, your client machine cannot ping the server, which suggests some sort of network configuration issue (such as a failed DNS lookup, or a firewall or routing issue). Contact your network administrator to troubleshoot further.

Verifying username and password

The test checks whether the logon credentials (user ID and password) provided in the connection are valid.

If the test fails, update the connection with the correct user ID, specifying the correct password on connection.

Accessing SSH on the remote host

Note: This test is only applicable for connections in which the remote file system is SSH, or the remote shell is SSH.

The test checks whether the remote host accepts SSH commands.

The test fails if the remote host does not support SSH commands. SSH must be enabled on the remote host.

Check whether the remote port is open

Note: This test is only applicable to those connections in which the server launcher type is Daemon.

The test checks whether the remote daemon port specified in the connection is open.

This test fails if the daemon port is not available. Ensure the daemon is running on the port specified in the connection properties:

Port connection number

Connecting to the remote daemon

Note: This test is only applicable to those connections in which the server launcher type is Daemon and the remote shell type is DStore.

The test checks whether your client can make a connection to the daemon running on the remote host.

The test fails if the client fails to make a connection to the remote daemon. The check first tries to connect with SSL enabled, and if it fails to make a connection, it again tries with SSL disabled.

If SSL is enabled on the remote host and your client has not saved the SSL certificates, you are prompted to save them.

Launching a new server

Note: This test is only applicable if the server launch type is either SSH or Daemon.

The test checks whether a server can be launched on the remote host.

The test fails if a server cannot be launched from the daemon. For RSE connection types, check that the daemon specified in the connection is running, on the port specified, on the remote host. To see which port is specified, right-click the connection, then choose Properties > Connector Services > DStore Connector Services > Remote Server Launcher > Launcher Properties > Daemon Port.

For SSH connection types, check that the server launch command is referencing the correct product and pathname: right-click the connection, then choose Properties > Connector Services > DStore Connector Services > Remote Server Launcher > Launcher Properties > Server Launch Command. The test first tries to connect with SSL enabled, and if it fails to make a connection, it tries again with SSL disabled.

If SSL is enabled on the remote host and your client has not saved the SSL certificates, you are prompted to save them.

Checking whether X Server is running

The test checks whether an X Window can be opened, using the location taken from the Debug Preferences page (Window > Preferences > Micro Focus > Debug).

If the Default X Server (DISPLAY) field is empty, clientMachineName:0.0 is used as default.

The test generates a warning if the X Server cannot be contacted. The warning contains the details of the DISPLAY it is trying to contact. Edit the Default X Server (DISPLAY) field if the details are incorrect.

Checking the write access in home directory

The test checks whether the user, specified in the connection user ID, has write access in the home directory on the remote host.

The test fails if the user does not have the write permission in the /home/user ID directory. You must update the permissions on the remote host.

Compiling to 32-bit

The test checks whether a program can be compiled to 32 bit on the remote host.

The test generates a warning if a program cannot be compiled to 32 bit. Check whether the remote host supports 32-bit compilation.

Compiling to 64-bit

The test checks whether a program can be compiled to 64 bit on the remote host.

The test generates a warning if a program cannot be compiled to 64 bit. Check whether the remote host supports 64-bit compilation.

Checking the product version

The test checks whether the product version of the Visual COBOL Development Hub on the remote host and the product version of Visual COBOL are compatible.

This test generates a warning if there is a compatibility issue with the products installed. The warning also specifies both product versions. It is possible to continue working, but if you find issues, it is advisable to update to compatible versions.

Creating and modifying files

The test checks whether a file can be created via one mechanism and modified by another on the remote host. This checks whether a file created by Samba/NFS or RSE can be modified at the remote end. It also checks whether a file created at the remote end can be modified by Samba/NFS or RSE.

The test fails if the file created with one mechanism cannot be modified by another mechanism.

UDP

The test checks whether the client can communicate with the remote host using the UDP protocol.

If the test fails, check whether UDP packets are being blocked by the firewall at the client end, and if so, contact your network administrator to troubleshoot further.

A lack of UDP support means that features such as ES/MFDS and IMTK deployment may not work.

Note: To view your connection properties:

Click Window > Show View > Other > Remote Systems > Remote Systems.
This opens the Remote Systems view.
Right-click the connection, and then click Properties.
This opens your connection's Properties dialog box.