Checking connection with remote machine
HULFT connects to remote hosts and carries out file transfer by using the TCP/IP protocol. The remote machines that are counterparts in transfer are identified by their 'host names.' Therefore, you must verify the connection to each host by running a connection test with host name specified (using the PING command).
In addition, a local host has to satisfy all of the following conditions:
-
Active state of address '127.0.0.1' (LOOPBACK address)
-
Existence of 'Internet address: 127.0.0.1/Host name: LOOPBACK' in TCP/IP host table
In order to be ready for the communication test that will be explained later in this manual, make sure that the result of the connection test to the local host name of the machine is successful.
If you are using a network in which a firewall is installed, configure in advance communication in HULFT to pass through the firewall.
Command Entry S1234567
Request level: 4
Previous commands and messages:
> PING HOST01
Verifying connection to host system HOST01 at address 172.16.XX.XXX.
PING reply 1 from 172.16.XX.XXX took 15 ms. 256 bytes. TTL 64.
PING reply 2 from 172.16.XX.XXX took 0 ms. 256 bytes. TTL 64.
PING reply 3 from 172.16.XX.XXX took 0 ms. 256 bytes. TTL 64.
PING reply 4 from 172.16.XX.XXX took 0 ms. 256 bytes. TTL 64.
PING reply 5 from 172.16.XX.XXX took 0 ms. 256 bytes. TTL 64.
Round-trip (in milliseconds) min/avg/max = 0/3/15.
Connection verification statistics: 5 of 5 successful (100 %).
Bottom
Type command, press Enter.
===>
F3=Exit F4=Prompt F9=Retrieve F10=Include detailed messages
F11=Display full F12=Cancel F13=Information Assistant F24=More keys
Screen 1.1 Connection Test Result (When Successful)
Command Entry S1234567
Request level: 4
Previous commands and messages:
> PING ASHOST
Unknown host, ASHOST.
Bottom
Type command, press Enter.
===> PING ASHOST
F3=Exit F4=Prompt F9=Retrieve F10=Include detailed messages
F11=Display full F12=Cancel F13=Information Assistant F24=More keys
Screen 1.2 Connection Test Result (When Unsuccessful)