Port 2725: MSOLAP PTP2 — A Microsoft Protocol Nobody Talks About

What Port 2725 Is

Port 2725 is registered in the IANA port registry for MSOLAP PTP2 (msolap-ptp2), assigned by Cristian Petculescu at Microsoft.¹ Both TCP and UDP are registered.

MSOLAP is the OLE DB provider for Microsoft SQL Server Analysis Services — the engine behind OLAP cubes and multidimensional data models. The "PTP2" suffix suggests a peer-to-peer or point-to-point variant of the protocol, possibly intended for direct node-to-node communication in Analysis Services cluster configurations.

In practice: this port is almost never used. Microsoft's Analysis Services documentation doesn't reference it as a required port. No major firewall guides call it out. No security advisories track it. It exists in the registry, but the silence around it is telling.

What Range It Belongs To

Port 2725 falls in the registered port range (1024–49151). These ports require registration with IANA to prevent conflicts, but registration doesn't mean active use. Thousands of registered ports represent protocols that were planned, partially deployed, or simply abandoned while the registration remained.²

Registered ports sit between the well-known ports (0–1023), which are tightly controlled and universally recognized, and the dynamic/ephemeral ports (49152–65535), which are handed out temporarily for outbound connections. Registered ports are the middle ground — structured, but far less scrutinized.

Security Considerations

Something listening on port 2725 on a non-Analysis Services machine has no obvious legitimate reason to be there. The port has been flagged by some security databases as historically associated with unauthorized use, likely because its obscurity makes it attractive for malware trying to avoid detection by hiding on ports that firewalls don't specifically block.³

If you see unexpected traffic on port 2725, investigate.

How to Check What's Listening

On Linux/macOS:

# Show what process is listening on port 2725
sudo ss -tlnp sport = :2725

# Or with lsof
sudo lsof -i :2725

On Windows:

netstat -ano | findstr :2725

Then cross-reference the PID with Task Manager or:

tasklist /fi "pid eq <PID>"

Why Unassigned-in-Practice Ports Matter

The port number system depends on coordination. When every application invented its own port, chaos followed. IANA registration was meant to solve this — a single registry, one protocol per port, no conflicts.

But registration doesn't enforce use. It doesn't prevent abandonment. The result is a registry with thousands of entries like port 2725: technically occupied, practically vacant, and occasionally exploited by software that knows nobody is watching.

These quiet ports are worth understanding. They're a reminder that the Internet's infrastructure includes a lot of ghost towns — structures built for protocols that never arrived, or arrived and left.