Port 467: Mylex-mapd — The Ghost of RAID's Golden Age

Port 467 is a time capsule. It was assigned to mylex-mapd, the management daemon for Mylex Corporation's RAID controllers. If you worked in a server room in the 1990s, you probably touched a Mylex card. If you're reading this in 2026, you probably never heard of them.

What Runs on Port 467

Port 467 carries mylex-mapd on both TCP and UDP.¹ This was the protocol that let administrators monitor and manage Mylex RAID controllers—the hardware that turned multiple hard drives into fault-tolerant storage arrays.

RAID (Redundant Array of Independent Disks) was how you kept data safe before cloud storage existed. If a drive failed, the array kept running. Mylex made the controllers that orchestrated this.

The Company Behind the Port

Mylex Corporation existed from 1983 to 1999. They started making peripherals and expansion cards, but in 1993 they pivoted to RAID controllers.² It worked. By the mid-1990s, Mylex controlled 75% of the RAID controller market.³

That's not "a major player." That's dominance.

Their AcceleRAID and eXtremeRAID product lines became industry standard. IBM servers shipped with them. Sun used them. If your company had a file server in 1997, there was a good chance it had a Mylex card inside.

What Happened

In 1999, IBM acquired Mylex for $240 million.⁴ Three years later, IBM sold the division to LSI Logic. The Mylex brand disappeared into the consolidation that defined enterprise hardware in the 2000s.

But port 467 remains in the IANA registry. A permanent record of a company that briefly owned an entire category of infrastructure.

The Protocol Nobody Uses

Mylex-mapd is effectively dead. The hardware it managed is decades obsolete. Modern RAID controllers use different management protocols. IPMI, vendor-specific web interfaces, operating system drivers—the ecosystem moved on.

But port 467 sits in the well-known range (0-1023), which means it was assigned before the IANA tightened registration requirements. Getting a well-known port in the 1990s meant something. It meant your protocol mattered enough to deserve a permanent address.

Unofficial Uses

Some sources claim Cisco's Server Load Balancing (SLB) protocol uses port 467.⁵ This appears to be an informal usage—Cisco SLB is proprietary and not officially assigned to this port.

Port 467 has also been associated with trojan activity in the past,⁶ though this is true of many ports. Malware will use whatever port is open.

Why This Port Matters

Port 467 is a monument to impermanence. A company dominated a market, got a well-known port assignment, then vanished into acquisition history. The technology is obsolete. The protocol is unused. The company is gone.

But the port number remains, forever reserved in the IANA registry, a fossil in the Internet's nervous system.

Every port tells a story about what mattered when it was assigned. Port 467's story is about RAID controllers in the 1990s, about a company that briefly owned a category, about how completely infrastructure can be forgotten.

How to Check This Port

To see if anything is listening on port 467 on your system:

Linux/Mac:

sudo lsof -i :467
netstat -an | grep 467

Windows:

netstat -an | findstr :467

You probably won't find anything. The hardware is gone. The protocol is dead. The port is empty.

The Well-Known Range

Port 467 sits in the well-known range (0-1023), ports originally assigned by Jon Postel and the early Internet Assigned Numbers Authority. These ports were meant for standard services that every system might need.

Mylex-mapd got one of these permanent addresses because in the 1990s, RAID management seemed like fundamental infrastructure. And for a moment, it was.

Related Ports

• Port 3260: iSCSI, the modern way to access block storage over networks
• Port 623: IPMI over LAN, used for modern server hardware management
• Port 902: VMware ESX Server management, how virtualization replaced a lot of physical RAID