HP JetDirect

History

HP JetDirect originated in the HP LaserJet IIISi generation, the model that introduced local-area-network connectivity through HP's MIO (Modular Input/Output) expansion slot. Sources disagree on the exact timing: HP's own history materials and the HP Computer Museum date the LaserJet IIISi printer to around Fall 1990, while secondary references commonly date the JetDirect MIO card itself to early 1991 (frequently cited as March 1991). The precise month rests largely on secondary sources rather than a primary HP press archive, so the safest framing is that the JetDirect card appeared in the IIISi generation — printer circa Fall 1990, card commonly dated to early 1991.

JetDirect is sometimes described in HP-history and marketing-style writing as an early mass-market Ethernet network printer. That superlative traces mainly to secondary sources and should be treated cautiously; there is no primary confirmation of an unqualified "first" claim.

In the early MIO era a printer generally needed a separate card per network protocol (for example TCP/IP, IPX/SPX, AppleTalk, and DLC/LLC). Multi-protocol MIO cards are reported to have followed around the mid-1990s, though specific dates are only loosely sourced. External JetDirect print-server boxes, connecting to a printer's parallel port, were introduced in the early-to-mid 1990s and extended network printing to devices without an MIO slot.

Around 1997, HP introduced EIO (Enhanced Input/Output) — reported as a 32-bit, 33 MHz, 3.3 V PCI-signaling implementation debuting with the LaserJet 4000 series — as the successor slot standard to MIO. Later internal JetDirect cards (the 600n/610n/615n/620n/625n/630n/635n families and wireless variants) are EIO cards. Over time HP moved much of this capability into Embedded Jetdirect, integrating network functionality directly into the printer or multifunction device.

What problem it solved

Before network print servers, a shared printer was typically cabled to a single PC, to a dedicated print-server computer, or connected through limited sharing schemes. That approach created bottlenecks, single points of failure, and cabling-distance limits.

JetDirect let a printer become an independent node on the LAN with its own network address, reachable by many users and multiple operating systems at once, without tying up a host computer. Because 1990s offices ran several competing network protocols simultaneously, JetDirect also gave a single hardware line a way to speak those protocols from one device.

How it works

A JetDirect device gives the printer a network identity and a network protocol stack. It obtains an IP address via BootP, DHCP, manual configuration, or link-local Auto IP, then listens for incoming print jobs and management traffic.

For raw or "socket" printing, the device opens a listening TCP socket on port 9100. A client establishes a TCP connection and streams already-rendered print data — PCL, PostScript, or another page-description language — straight through, and the print server passes the bytes to the printer engine essentially unaltered. The connection is bidirectional, so the printer can return status back over the same channel.

Historically, many JetDirect devices also exposed a Telnet configuration interface, supported alternative print protocols such as LPD/LPR and IPP, and offered management via SNMP and an embedded web server.

Where it sits in the print/document pipeline

JetDirect sits at the transport and delivery stage of printing. It operates after an application and printer driver on the client have rendered the document into a page-description language, and before the printer's interpreter rasterizes it.

It is, in effect, the wire and the doorway: it carries the finished PDL stream across the network into the device. In raw mode it deliberately does the least possible work, adding no job framing of its own — which is the source of both its speed and its lack of built-in security.

Relationship to printers

JetDirect is fundamentally printer-attached networking. Internal cards (MIO, later EIO) plug into HP printer expansion bays; external boxes connect via parallel (and later USB) ports to printers from HP and third parties; Embedded Jetdirect is built into the device's main board.

Because port-9100 raw printing is so simple, it became a de facto industry convention. Many non-HP network printers implement a port-9100 listener and are described as "JetDirect-compatible." That phrasing is descriptive of the convention, not an HP endorsement — JetDirect the product line is HP's.

Relationship to operating systems

JetDirect was explicitly multi-protocol to serve mixed environments: TCP/IP (Unix and Windows), IPX/SPX (Novell NetWare), AppleTalk (Mac), and DLC/LLC (IBM and Microsoft LAN environments).

In modern practice, TCP/IP raw printing on port 9100 is the common denominator:

• Windows implements it as the "Standard TCP/IP Port" in RAW mode (port 9100).
• CUPS (macOS, Linux, and Unix) provides an "AppSocket / HP JetDirect" backend using device URIs of the form socket://<ip-address>[:9100].
• Linux and Unix systems can also reach JetDirect devices via LPD/LPR or IPP when the device supports them.

Relationship to PDF / PostScript / drivers

JetDirect is PDL-agnostic transport — it does not render or interpret documents. The client-side driver produces the byte stream (PCL, PostScript, and on capable modern devices PDF or other PDLs), and JetDirect simply delivers it; the printer's own interpreter performs the rasterization.

The IANA service names registered for port 9100 — hp-pdl-datastr ("PDL Data Streaming Port") and pdl-datastream ("Printer PDL Data Stream") — reflect exactly this: it is a page-description-language data stream, not a specific PDL. JetDirect is therefore orthogonal to the choice of PostScript versus PCL versus PDF; it carries whichever the driver and printer agree on.

Note that raw port-9100 printing bypasses the richer job-attribute negotiation that a protocol such as IPP provides.

Modern use

Raw port-9100 printing remains very widely deployed because it is simple, fast, and reliable, and is supported out of the box by Windows, CUPS, and virtually all network printers.

At the same time, the industry has been shifting toward IPP / IPP Everywhere / driverless printing, which adds encryption, richer job attributes, and status reporting. Security guidance — including the CUPS documentation — recommends IPP over raw AppSocket/JetDirect where possible, because port 9100 offers no authentication or encryption. The CUPS documentation states plainly that while the AppSocket protocol is simple and fast, "it also offers no security and is often an attack vector with printers," and suggests considering IPP with encryption instead.

Many discrete JetDirect card and box products have been discontinued as networking moved into Embedded Jetdirect and as EIO-slot printers aged out, though HP still offers Jetdirect LAN accessories for certain devices.

Advantages

• Very simple and low-overhead; among the fastest network print paths.
• The bidirectional TCP channel can return printer status and error feedback to the client.
• PDL-agnostic — carries any print data stream unchanged.
• Broad, near-universal support across operating systems and printer brands.
• Historically bridged several coexisting network protocols in one product line.
• Does not require spooling the entire job to disk before transmission (unlike classic LPD).

Limitations

• No built-in security: raw port-9100 offers no authentication and no encryption, and is widely noted as a printer attack vector.
• No standardized job accounting, queuing semantics, or rich attribute negotiation in raw mode — functionality that IPP provides.
• Raw streaming assumes the client sends correctly formed PDL; there is minimal protocol-level error handling.
• Configuration and management interfaces of older devices (Telnet, SNMP, embedded web) have themselves been sources of vulnerabilities.
• Legacy protocol support (IPX/SPX, AppleTalk, DLC/LLC) and older MIO/EIO hardware are now largely obsolete.

Related standards and protocols

• Raw / AppSocket / port 9100 — the raw TCP printing method. CUPS refers to "the AppSocket protocol (sometimes also called the JetDirect protocol)." AppSocket is commonly attributed (in secondary sources) to Tektronix for its Phaser printers, a line later sold to Xerox; treat the attribution as reported rather than primary-verified.
• LPD/LPR (RFC 1179) — the older line-printer daemon protocol.
• IPP — Internet Printing Protocol (IETF/PWG; RFC 8010 covering encoding and transport and RFC 8011 covering model and semantics, plus IPP Everywhere) — the modern, secure, feature-rich successor.
• SNMP — used for printer management and monitoring.
• BootP / DHCP — IP address assignment methods used by JetDirect devices.
• MIO and EIO — HP's printer expansion-slot interfaces that host internal JetDirect cards.

Timeline

1. c. 1990

   HP LaserJet IIISi ships; it is the generation that introduces LAN connectivity via the MIO expansion slot.

2. Early 1991

   The JetDirect MIO card is commonly dated to this period in secondary sources (frequently cited as March 1991); the exact month is not primary-confirmed.

3. Early 1990s

   Early MIO network cards typically require a separate card per protocol (TCP/IP, IPX/SPX, AppleTalk, DLC/LLC).

4. Early-to-mid 1990s

   External JetDirect print-server boxes (parallel-port connection) are introduced; multi-protocol MIO cards are reported to follow around the mid-1990s.

5. ~1997

   EIO is introduced as the successor slot standard to MIO, reported alongside the LaserJet 4000 series; later internal JetDirect cards are EIO cards.

6. Late 1990s–2000s

   EIO card families (600n through 635n and wireless variants) and Embedded Jetdirect broaden protocol and speed support.

7. 2000s–present

   Industry shift toward IPP / IPP Everywhere / driverless printing; many standalone JetDirect card and box products are discontinued as functionality moves into Embedded Jetdirect.