Port 2104: Zephyr Hostmanager — The Campus Messaging Port That Time Forgot

Port 2104 is registered to zephyr-hm — the hostmanager component of MIT's Zephyr Notification Service, developed as part of Project Athena in the mid-1980s.¹

You almost certainly have never used it. That doesn't make it uninteresting.

What Zephyr Was

In 1986, MIT's Project Athena had a problem: thousands of students and researchers scattered across hundreds of workstations, and no way to find each other or send real-time notifications across the network. Email was asynchronous. Talk was one-to-one. There was nothing in between.

Zephyr was the solution. It introduced concepts that feel obvious now but were genuinely novel then: presence detection (knowing whether a user was logged in and where), publish-subscribe messaging (subscribing to message classes, not individual users), and real-time delivery across a distributed campus network.²

Slack would solve this same problem, commercially, about 28 years later.

The Three Ports

Zephyr used a cluster of three ports:

The hostmanager (port 2104) was the local agent — a daemon running on each workstation that maintained the connection between that machine and the central Zephyr server. When you logged in, the hostmanager announced your presence. When a message arrived for you, the hostmanager received it. It was the last mile of the Zephyr network.

The design was elegant: the server handled routing and subscriptions, the hostmanager handled the per-machine reality of users appearing and disappearing. Port 2104 was where those two worlds met.³

Is Anything Using This Port Today?

Almost nothing. Zephyr survived as an active protocol at MIT and a handful of other universities for decades — remarkably longer than anyone expected — but has faded from even academic use. The GitHub repository for the Zephyr protocol exists but is largely dormant.⁴

If you see traffic on port 2104, it's almost certainly not Zephyr. It's more likely custom application software that picked an obscure registered port to avoid conflicts, or a misconfigured service.

Check What's Listening

To see if anything is using port 2104 on your machine:

# macOS / Linux
ss -tlnp | grep 2104
# or
lsof -i :2104

# Windows
netstat -ano | findstr :2104

If something is listening, check the process ID and look it up — it won't be Zephyr.

Why Unassigned-Adjacent Ports Matter

Port 2104 is technically registered, but its registrant is a 40-year-old academic project that predates the modern Internet. In practice, it behaves like an unassigned port — available for any software that wants a home in the registered range (1024–49151) without going through IANA.⁵

This is common. The registered port space is vast, enforcement is minimal, and plenty of software quietly uses ports that are technically claimed by something else. Port conflicts are rare in practice — the Internet is big, and most software never runs in the same environment as Zephyr.