What This Port Is
Port 2959 sits in the registered port range — the 48,127-port stretch between 1024 and 49151 where companies, standards bodies, and individual developers can claim a number for their software. Unlike the well-known ports below 1024 (which require root or administrator privileges to open), registered ports are available to any application. They're the middle ground of the port world: not privileged, not ephemeral, but recognized.
IANA has assigned port 2959 to a service called RMOPAGT, registered by Shuji Okubo at Fujitsu (okubo@yk.fujitsu.co.jp). The registration covers both TCP and UDP. Beyond that, the IANA record offers nothing. No description. No linked RFC. No documentation of what RMOPAGT stands for or what it does.1
The name suggests something like a Remote Management Operations Agent — a Fujitsu internal daemon for some server management or monitoring product, possibly related to their ServerView suite. But that's inference from the letters, not documentation.
The Honest Answer
Nobody outside Fujitsu seems to know what RMOPAGT is, and Fujitsu's public documentation doesn't mention port 2959 by name in any accessible manual. This isn't unusual. The IANA registered port list contains hundreds of entries like this — a port number claimed by a company for internal software, the registration made in good faith, the product long since evolved or discontinued or simply never widely deployed. The port number persists in the registry. The software context evaporates.
If you're seeing activity on port 2959, it almost certainly isn't RMOPAGT. It's more likely:
- A development server or local service using a convenient uncontested port
- A gaming application or P2P client that picked this range
- An application that chose this port for an internal API
How to Check What's Actually Listening
If port 2959 is open on your machine, you can identify the process in seconds.
On Linux or macOS:
On Windows (Command Prompt as Administrator):
The output will show you the process ID (PID) using the port. On Linux/macOS, lsof will show the process name directly. On Windows, take that PID to Task Manager or run:
Why Unassigned-in-Practice Ports Matter
The registered port range was meant to bring order to chaos — a place where software could claim a number so that two applications wouldn't accidentally collide. In practice, IANA registration is voluntary for ports above 1024, compliance is unenforceable, and the registry is full of entries where the registrant has no ongoing obligation to document, maintain, or publicize their assignment.
Port 2959 is a small example of a larger truth: the port registry is a historical record, not a live map. It tells you what someone once claimed. It doesn't tell you what's actually running.
Was deze pagina nuttig?