Port 1606: Salutation Manager — The forgotten handshake between office machines

Port 1606 carries the Salutation Manager protocol—a service discovery system created in the mid-1990s when the biggest networking problem facing corporations was getting printers, copiers, and fax machines to find each other.

The protocol still has its officially assigned port. The world it was built for has moved on.

What Runs on Port 1606

The Salutation Manager (SLM-API) operates on both TCP and UDP port 1606.¹ It's a service broker protocol that allows devices and applications—called "Networked Entities"—to discover and utilize each other's capabilities.

The architecture works in three parts:

• Services register their capabilities with the Salutation Manager
• Clients query the Salutation Manager to discover available services
• The Manager acts as the intermediary, matching clients with the services they need

The protocol is transport-independent. You can run Salutation over TCP/IP, infrared, serial connections, or any transport mechanism with an appropriate Transport Manager implementation.

The Vision That Didn't Arrive

In 1995, the Salutation Consortium formed with an ambitious goal: create a universal architecture for networked devices. Canon, Ricoh, IBM, Xerox, Kyocera-Mita, and others joined forces to define a uniform way of describing device capabilities—fax machines, printers, copiers, PDAs, phones—with a single common method for sharing that information.²

The problem they were solving was real. Every manufacturer had their own way of announcing capabilities. A printer from one vendor couldn't tell a computer from another vendor what paper sizes it supported, what print quality options it offered, or whether it could duplex. The Salutation architecture aimed to create a common vocabulary.

The consortium released specifications throughout the late 1990s. A Java version of Salutation-Lite arrived in May 2000.³ The protocol was carefully designed to be network-agnostic, using RPC technology to enable communication between different implementations.

But the world moved faster than the standard.

What Happened

Service discovery became a solved problem—just not the way the Salutation Consortium envisioned. Instead of devices registering capabilities with a centralized manager, the Internet moved toward different approaches:

• UPnP (Universal Plug and Play) became the standard for consumer device discovery
• mDNS and DNS-SD (Bonjour) emerged for zero-configuration networking
• SSDP (Simple Service Discovery Protocol) took over for media devices
• Bluetooth SDP handled discovery for short-range wireless
• Eventually, most services just exposed HTTP APIs and assumed everything spoke the same web protocols

Salutation appears alongside these protocols in academic comparisons of service discovery mechanisms, but it's listed as a historical example rather than a current solution.⁴

The Protocol Today

Port 1606 remains officially assigned to Salutation Manager in the IANA registry.¹ The assignment isn't going anywhere—port numbers don't get revoked just because a protocol falls out of use.

If you see traffic on port 1606 in 2026, you're either encountering:

• Legacy office equipment still running Salutation-enabled software
• An embedded system that integrated Salutation decades ago and never got updated
• Something else entirely that's using the port unofficially because it was available

The third option is uncommon—most modern software doesn't randomly pick ports in the registered range. But it's possible.

How to Check What's Listening

If you find port 1606 active on your network:

# On Linux/Mac - see what's listening on port 1606
sudo lsof -i :1606
sudo netstat -tulpn | grep 1606

# On Windows
netstat -ano | findstr :1606

You can also use nmap to identify the service:

nmap -sV -p 1606 <target-ip>

If it's actually Salutation Manager, nmap's service detection might identify it. More likely, you'll see "unknown" or a misidentification—few modern tools maintain signatures for protocols that stopped being actively developed before the iPhone existed.

Why This Port Matters

Port 1606 represents a category of protocol that's essential to understanding how the Internet evolved: the well-intentioned standard that got displaced.

The Salutation Consortium wasn't wrong. Device discovery was a real problem. Their architecture was technically sound, transport-independent, and carefully designed. But creating a standard isn't enough—you need adoption, ecosystem momentum, and timing.

UPnP won because Microsoft and Intel pushed it. Bonjour won because Apple shipped it with every Mac and iOS device. HTTP won because browsers were everywhere and nobody wanted to implement yet another protocol.

Salutation lost because solving device discovery required more than clever engineering. It required network effects the consortium couldn't manufacture.

Related Ports

Other service discovery protocols claimed their own ports:

• Port 427 - Service Location Protocol (SLP), another 1990s service discovery mechanism
• Port 1900 - SSDP (Simple Service Discovery Protocol), used by UPnP
• Port 5353 - mDNS (Multicast DNS), the foundation of Bonjour/Zeroconf

Of these, only mDNS and SSDP see significant modern use. The pattern repeats: good ideas, official ports, but the market moved elsewhere.