Ping tool
Test network connectivity from SIA Connect to a device, server, or cloud service and interpret common ping results.
The Ping tool tests whether SIA Connect can reach a device, server, or cloud service by its IP address or hostname. Use it when diagnosing network routes, device availability, or Domain Name System (DNS) resolution.
The ping request is sent from SIA Connect. It tests connectivity from the gateway, not from the computer running the browser.
Open the Ping tool
- Sign in to the Edge Portal.
- Expand Tools in the sidebar.
- Select Ping.
The page contains a Host URL / IP field, a Ping button, and an output area that appears after a test.
Run a ping test
- Enter the destination in Host URL / IP. You can enter an IP address such as
192.168.1.10or a hostname such asexample.com. - Do not include a protocol or page path. Enter
example.cominstead ofhttps://example.com/status. - Select Ping, or press Enter.
- Wait while the page displays Pinging and the message Pinging [host], please wait.
- Review the output displayed below the field.
The field and button are unavailable while the test is running. The field is cleared when the test finishes.
Understand the result
The output begins with the tested destination and the date and time when the test was run. The remaining lines contain the response returned by the ping service.
| Result | What it means |
|---|---|
| Replies are received | SIA Connect can reach the destination and the destination allows ping responses. |
| Some packets are lost | The destination is reachable, but the connection may be unstable or congested. |
| All packets are lost or the request times out | No ping response was received. The destination may be offline, unreachable, incorrectly addressed, or configured to block ping traffic. |
Error: couldn't resolve host |
The entered hostname could not be resolved, the field was empty, or no usable result was returned. |
A successful ping confirms basic IP connectivity. It does not confirm that a specific service or port, such as OPC UA, MQTT, or a database connection, is available.
Test an IP address and a hostname
Testing both forms can help separate a routing problem from a DNS problem.
- Ping the destination using its IP address.
- Run another test using its hostname.
- Compare the results.
- If both tests succeed, IP connectivity and hostname resolution are working.
- If the IP address succeeds but the hostname fails, review the gateway DNS configuration.
- If both tests fail, review the destination address, network configuration, route, cabling, and destination availability.
See Change network settings in the Edge Portal for instructions about network interfaces and DNS settings.
Troubleshoot ping problems
| Message or result | What to check |
|---|---|
Error: couldn't resolve host |
Check that the field is not empty and that the hostname is spelled correctly. Remove prefixes such as http:// or https:// and remove page paths. If an IP address works but the hostname does not, check the configured DNS servers. |
Enter a host URL/IP and try again. |
Enter an IP address or hostname in Host URL / IP, and then run the test again. |
Ping failed with status [code] |
The portal could not complete the ping request. Check whether the portal is still connected to the gateway, refresh the page, and retry. Review the system logs if the problem continues. |
Network error while running ping. |
The request between the portal and the gateway failed. Check connection notifications, refresh the page, and sign in again if the session has expired. |
| No replies or complete packet loss | Confirm that the address is correct and the destination is powered and connected. Check the gateway network interface, subnet, route, VLAN, cabling, and firewall rules. Some devices intentionally block Internet Control Message Protocol (ICMP) ping requests. |
| Intermittent replies or packet loss | Check for an unstable cable or wireless link, network congestion, duplicate IP addresses, or an overloaded destination. Repeat the test to determine whether the result is consistent. |
If ping succeeds but a Connector or instance still reports an error, check the service address, port, credentials, protocol settings, and destination service. See Troubleshoot Connector, instance, item, and mapping errors.