Port 2370: Unassigned — Squatted by Enterprise Schedulers

Port 2370 is a registered port — meaning it falls in the range that IANA tracks (1024–49151) — but IANA has not assigned it to any official service. No RFC governs it. No protocol claims it by name.

That doesn't mean it sits empty.

What Range This Port Belongs To

The registered port range (1024–49151) is where most application software lives. Unlike the well-known ports (0–1023), which require elevated privileges to open and are tightly controlled, registered ports can be used by any application. IANA maintains a registry of assignments in this range, but the registry has gaps — ports that were never claimed, or claimed and later abandoned.

Port 2370 is one of those gaps. It's registered in the sense that IANA tracks the range, but unassigned in the sense that no service has staked an official claim.

Known Unofficial Uses

Two enterprise software packages treat port 2370 as home turf:

BMC Control-M — The primary association. Control-M is an enterprise workload automation platform that orchestrates batch jobs across large organizations. By default, TCP port 2370 is the channel through which the Control-M/Enterprise Manager connects to the Control-M/Server to exchange scheduling commands, job status, and control information. BMC's own documentation acknowledges this is "often changed during installation" — which is a polite way of saying the default exists for convenience, not because the port was reserved for this purpose.¹

Port 2369 is the companion: the Control-M Server Configuration Agent listens there, while 2370 handles the Enterprise Manager-to-Server conversation.²

Symantec Endpoint Protection — A secondary, older association. Some versions of Symantec Endpoint Protection Manager used port 2370 for communication between the management server and its clients. This use appears in community documentation but is not consistent across versions.³

How to Check What's Listening on Port 2370

On Linux or macOS:

# Show what process is using port 2370
ss -tlnp | grep 2370
# or
lsof -i :2370

On Windows:

netstat -ano | findstr :2370

Then cross-reference the PID with Task Manager or tasklist to identify the process.

If you find something listening on 2370 that you don't recognize, that's worth investigating — but the most likely culprit is a Control-M installation or an endpoint security management server.

Why Unassigned Ports Matter

The port registry is not airtight. Software ships with defaults. Defaults stick. And sometimes those defaults land on unregistered ports that happen to be available — until another application makes the same choice.

Port collisions are rare but real. If you're running both BMC Control-M and another application that also chose 2370 as a default, one of them loses. This is why BMC's own documentation suggests changing the port during installation: the default is a starting point, not a guarantee.

Unassigned ports in the registered range are also sometimes targeted by malware, precisely because they're less likely to be monitored. Port 2370 has appeared in older security threat databases in this context — not because it's inherently dangerous, but because the absence of a well-known legitimate service makes anomalous traffic easier to hide.⁴

If 2370 appears in your firewall logs and you're not running Control-M or Symantec EPM, it's worth a closer look.