What is the Meaning of the Response Messages when Performing a Ping Test for the IP Address of MicroEngine IP Controllers via Command Prompt

Summary:

• PING response message with Normal Reply.

• PING response message with Request Timed Out.

• PING response message with Reply from <IP address>: Destination Host Not Reachable.

• PING response message with General Failure.

• PING Continuously (ping -t) with Intermittently Connection and Dropped reply.

.

Step-by-step Guide:

• PING response message with Normal Reply:

Step 1: When user run ping test successfully, the following message will be prompted to show the reply from the IP address with the ping latency.
 
Figure 1: Command Prompt Response Showing Reply from IP Address and Ping Latency

.

Step 2: The response message of "Reply from IP Address: bytes=32  time=1ms  TTL=100" shows that the ping test has been transmitted from host (xPortalNet Server PC) to receiver (MicroEngine controller), and the host also successfully receives a response from the receiver.
 
Figure 2: Illustration to Show the Response Message under the Normal Reply

.

Step 3: Under the Ping statistics section, more information is displayed of the ping test, which includes number of packet Sent, Received and Lost, as well as the approximate round trip times in millisecond (ping latency).
 
Figure 3: Ping Statistics of the Ping Test

.

.

.

• PING response message with Request timed out:

Step 1: If user run ping test and the Command Prompt returned the following response message as below to indicate that Request timed out, it means the host (xPortalNet Server PC) did not receive a response from the receiver (MicroEngine controller).
 
Figure 4: Command Prompt Response Showing Request Timed Out Message 

.

Step 2: The response message of "Request timed out" shows that the host did not receive a response from the receiver, but it was able to reach it. This can be due to many causes: network traffic, packet filtering, failure of the ARP request and routing error.
 
Figure 5: Illustration to Show the Response Message under the Request Timed Out Reply

.

.

• PING response message with Reply from <IP address>: Destination host not reachable:

Step 1: If user run ping test and the Command Prompt returned the following response message as below to indicate Destination host unreachable, it means the host (xPortalNet Server PC) did not reach the receiver (MicroEngine controller).
 
Figure 6: Command Prompt Response Showing Destination Host Unreachable Message

.

Step 2: The response message of "Reply from IP Address:Destination host unreachable" shows that the ping test data was sent from the host (xPortalNet Server PC) to the receiver (MicroEngine controller), but the data cannot reach the receiver. This can be due to many causes: remote router is not properly routed in the local system or that the device is not operating in the same local network.
 
Figure 7: Illustration to Show the Response Message under the Destination Host Unreachable Reply

.

.

• PING response message with General Failure:

Step 1: If user run ping test and the Command Prompt returned the following response message as below to indicate General failure, it means the xPortalNet Server PC is not properly configured with internet protocols
 
Figure 8: Command Prompt Response Showing General Failure Message

.

Step 2: The response message of "General failure" shows that the xPortalNet Server PC is not properly configured with the internet protocol settings.
 
Figure 9: Illustration to Show the Response Message under the General Failure Reply

.

.

• PING Continuously (ping -t) with Intermittently Connection and Dropped reply:

Step 1: If user run the ping continuously test (ping IP Address -t) command, and the Command Prompt returned the following responses intermittently, there might be another device with the same IP address and is clashing with the receiver's IP address, or that the network connection between the host and the receiver is unstable.

Figure 10: Command Prompt Response Showing Intermittent Responses from the Receiver

1/4/2020 (Rev 1.0)