Port 2030: Unassigned — Oracle's Quiet Default

Port 2030 belongs to the registered port range (1024–49151). These ports are available for any application to use, with IANA maintaining a registry of official assignments to prevent collisions. Port 2030 has no official IANA assignment.

But it has a story.

The Unofficial Tenant

Oracle quietly made port 2030 its own. Oracle Services for Microsoft Transaction Server (OraMTS) uses it as the default recovery service port — and has for decades.¹

OraMTS is middleware that lets Oracle databases participate in Microsoft's distributed transaction system. When an application running on a Windows server needs to perform a transaction that spans multiple systems (including an Oracle database), OraMTS coordinates the two-phase commit: the handshake that ensures either everything succeeds or everything rolls back. No partial writes. No half-committed state.

The recovery service on port 2030 handles the cleanup when something goes wrong mid-transaction — crashes, network failures, anything that leaves a transaction in an uncertain state. It's the fallback that keeps data consistent when the normal flow breaks down.²

Oracle's own documentation instructs administrators: "If you are doing a silent install, the default port is 2030."³ No explanation for why 2030. No RFC. No IANA registration. Just a number baked into an installer that's shipped in Oracle Database for Windows since the late 1990s.

The IANA registry lists port 2030 as unassigned. Oracle and IANA have never reconciled this.

What the Scanners See

Port 2030 sees active reconnaissance. The SANS Internet Storm Center records daily scanning attempts — automated probes sweeping the Internet looking for whatever might be listening.⁴ Most of this is opportunistic: bots scanning the entire port range looking for open doors. Port 2030 is not a known target for specific exploits, but any open port attracts attention.

Nmap's service database labels port 2030 as "device2" — a placeholder that means Nmap has observed something on this port in the wild but doesn't know what.⁵ This is what happens when software skips the registration process: the tools that map the Internet have to make up names.

Checking What's Listening

If you see port 2030 open on a system, it's likely either:

• An Oracle Database installation on Windows with OraMTS enabled
• Something unrelated that chose this port by configuration

To check what's using it:

On Linux/macOS:

# Show what process is listening on port 2030
ss -tlnp | grep 2030
# or
lsof -i :2030

On Windows:

# Show the process bound to port 2030
netstat -ano | findstr :2030
# Then match the PID:
tasklist | findstr <PID>

With Nmap (from another machine):

nmap -sV -p 2030 <target-ip>

Why Unassigned Ports Matter

IANA's port registry exists to prevent exactly this kind of ambiguity. When Oracle ships OraMTS defaulting to port 2030 without registering it, any other application that also wants port 2030 has a problem. Both think they own it. Neither formally does.

The registered port range (1024–49151) has over 48,000 ports. Roughly 13,000 are officially assigned. The rest sit unassigned — available for use, but unregistered. Some are genuinely empty. Others, like 2030, are quietly occupied by software that never bothered to file the paperwork.

This is more common than the clean numbering suggests. The Internet runs partly on informal conventions that accumulated before anyone thought to write them down.