---
title: Ping & TCP
description: Run ICMP ping sweeps and ad-hoc TCP connectivity tests from the Edge Server to verify whether a device is reachable on the network.
source: https://documentation.controlcomtech.com/build/edge-server/web-interface/tools/ping
---

# Ping & TCP

`/tools/ping` is two independent network reachability tools on one page. Both run from the Edge Server, not your browser, which is exactly what you need when the question is "can my Edge Server reach this device?"

> **Workflow Stage: Collect**

## ICMP Ping

| Field     | Notes                               |
| --------- | ----------------------------------- |
| **Host**  | Hostname or IP.                     |
| **Count** | 1, 2, 4, 6, 8, or 10 echo requests. |

Click **Start** to stream results live. The results table shows sequence number, status (Reply or Failed), RTT in milliseconds, the resolved address, and the timestamp of each probe. A summary row aggregates **Sent**, **Received**, **Loss %**, and **Min / Max / Avg RTT**. **Stop** cancels an in-flight ping.

## TCP Connectivity

| Field       | Notes                        |
| ----------- | ---------------------------- |
| **Host**    | Hostname or IP.              |
| **Port**    | TCP port (1–65535).          |
| **Timeout** | Seconds to wait (default 5). |

**Test** opens a single TCP connection and reports **Open** or **Closed**, the resolved address, duration in ms, and the underlying error if the connection failed. Use this to verify that, for example, Modbus port 502 is reachable on a PLC before you wire up a client in the cloud.