Port 3683: BMC EDV/EA — Mainframe middleware, registered but rarely seen

What Is Port 3683?

Port 3683 sits in the registered ports range (1024–49151) and is officially assigned by IANA to bmc-ea — BMC Software's Enterprise Adapter (EA), registered in January 2003.¹

It appears on "unassigned" lists across the web. Those lists are wrong.

What BMC EDV/EA Actually Is

BMC Software is one of the largest enterprise software vendors in the world, and a significant portion of their business runs on IBM mainframes — the z/OS systems that quietly process an enormous share of the world's banking transactions, airline reservations, and insurance records.

The Enterprise Adapter (EA) is part of BMC's mainframe infrastructure tooling, specifically their User Interface Middleware (UIM) server. It acts as a bridge — letting modern applications talk to mainframe systems over TCP/IP. Port 3683 is the default communication port for that adapter.²

Most people will never see this port in the wild. It lives inside enterprise networks, behind firewalls, talking to systems that were built before most of the web existed. If you're not running BMC's mainframe tools on z/OS, this port does nothing for you.

Who Uses This Port?

Large institutions: banks, insurance companies, airlines, government agencies — the kind of organizations that still run mainframes because mainframes are genuinely excellent at certain things and the cost of migrating decades of business logic is astronomical.

If you see port 3683 active on a system, it's almost certainly BMC software doing its job, or a misconfiguration, or a scanner probing for open ports. The SANS Internet Storm Center does record occasional scanning activity on this port³ — opportunistic probes, not targeted attacks on anything BMC-specific.

How to Check What's Listening

If port 3683 shows up in your network traffic and you want to know why:

Linux/macOS:

# See what process is listening on port 3683
sudo ss -tlnp | grep 3683

# Or with lsof
sudo lsof -i :3683

Windows:

# Check what's bound to port 3683
netstat -ano | findstr :3683

# Then look up the PID
tasklist | findstr <PID>

If nothing is listening, traffic to this port will be dropped or rejected — standard behavior for any closed port.

Why Registered Ports Like This Matter

The registered ports range exists so software vendors can claim a default port without stepping on each other. BMC registered 3683 so their Enterprise Adapter always has a predictable home — system administrators know where to open firewall rules, and nothing else is supposed to be there.

In practice, thousands of registered ports belong to software that's obscure, discontinued, or so specialized that you'll never encounter it. They're claimed real estate on a quiet street. Port 3683 is one of them: officially spoken for, rarely occupied from the Internet's perspective, entirely unremarkable unless you're running mainframe middleware from 2003.