███████╗██████╗ ██████╗ ██╗███╗ ██╗████████╗
╚══███╔╝██╔══██╗██╔══██╗██║████╗ ██║╚══██╔══╝
███╔╝ ██████╔╝██████╔╝██║██╔██╗ ██║ ██║
███╔╝ ██╔═══╝ ██╔══██╗██║██║╚██╗██║ ██║
███████╗██║ ██║ ██║██║██║ ╚████║ ██║
╚══════╝╚═╝ ╚═╝ ╚═╝╚═╝╚═╝ ╚═══╝ ╚═╝
Universal LAN Zero-Configuration Print Bridge
ZPrint transforms any USB host-based, GDI, or CAPT printer (such as the legendary Canon LBP 2900 / 3000, HP LaserJet 1020 / P1005, Epson, and other legacy office printers) into a high-performance, driverless Network Smart IP Printer across your entire local area network (LAN/WLAN).
With native RFC 8011 IPP (Internet Printing Protocol) support, mobile devices (iPhone, iPad, Android) and desktop operating systems (macOS, Linux, Windows) can print seamlessly using their standard OS print dialog (Ctrl+P or Share -> Print) with zero manufacturer driver installation required on client devices.
- Why ZPrint Was Created (The Motivation)
- Technical Deep-Dive: Why USB Printer Sharing Is Fundamentally Broken
- The Solution: A True Network IP Printer Architecture
- Architecture Overview
- Feature Comparison
- Quick Start
- Client Setup Walkthrough
- Host Server Administration
- CLI Reference
- Zero-Dependency Architecture
- Building & Testing
- License
In offices, factories, hospitals, logistics warehouses, and schools worldwide, millions of ultra-durable USB laser printers refuse to die. The most iconic example is the Canon LBP 2900 / 3000 (and its HP twin, the LaserJet 1020). Built with heavy-duty metal rollers, mechanical simplicity, and indestructible toner cartridges (Canon 303 / HP 12A), these printers routinely outlive multiple computer cycles, operating system generations, and entire IT infrastructures.
While the printers endure, the surrounding computing environment has fundamentally transformed:
- Teams no longer work on homogenous Windows desktop fleets. Workplaces are now filled with macOS MacBooks (Apple Silicon M1/M2/M3), iPads, iPhones (iOS), Android tablets, and Linux workstations.
- To enable team members to print, the standard practice has always been to plug the USB printer into one Windows desktop and turn on Windows Printer Sharing (
\\host\printer). - The result is an endless nightmare of IT support tickets:
- Windows cumulative updates trigger error codes
0x0000011bor0x00000709. - Non-Windows devices cannot connect at all.
- Client machines struggle to find or install matching 32-bit / 64-bit drivers over the network.
- Spoolers hang whenever two people print at once, requiring a manual reboot of the host PC or restarting the
spoolerservice.
- Windows cumulative updates trigger error codes
- Systems administrators resort to risky registry hacks (
RpcAuthnLevelPrivacyEnabled = 0) that compromise network security, only to have the next Windows update overwrite their changes. Replacing these bulletproof printers with commercial network printers costs hundreds or thousands of dollars and introduces costly, fragile cartridge DRM.
ZPrint was created to solve this chronic engineering dilemma permanently. It bridges the legacy USB world and modern network standards, converting a USB printer into a True Network IP Printer that is immune to Windows RPC hardening, completely driverless for client devices, and natively accessible from any operating system on the LAN.
To understand why ZPrint's architecture is necessary, one must examine the low-level technical failure modes of traditional sharing methods.
There are two fundamentally different classes of printers:
| Characteristic | Enterprise Network Printer (PostScript / PCL) | Host-Based / CAPT / GDI Printer (USB) |
|---|---|---|
| Onboard Processor | Dedicated 500MHz–1.2GHz RISC / ARM CPU | None (Pure mechanical microcontroller) |
| Onboard Memory | 512 MB – 2 GB RAM | Minimal internal line buffer (~64 KB - 2 MB) |
| Rasterizer (RIP) | Onboard hardware Raster Image Processor | Host PC CPU (Software rasterizer) |
| Input Protocol | High-level vector descriptions (PCL 5/6, PostScript, PDF) | Raw proprietary binary dot-matrix bitmaps |
| USB Handshake | Unidirectional or standard IEEE-1284 / USB print | Tight, proprietary bidirectional engine sync |
Printers like the Canon LBP 2900 utilize CAPT (Canon Advanced Printing Technology). The printer hardware is essentially a "dumb" laser scanning assembly and paper transport. It has no capability to render fonts, compute vector Bézier curves, or parse PostScript.
The host PC's CPU must rasterize every character and vector path into an enormous raw bitmap (up to 30–50 MB per page at 600 DPI) and stream it using proprietary microcode. Furthermore, the CAPT driver continuously interrogates the printer engine over USB (monitoring laser polygon mirror synchronization, toner sensor capacitance, fuser roller temperature, and paper registration interrupts).
Why this breaks over SMB network sharing: When shared via standard Windows SMB, the client PC's driver attempts to execute this proprietary rasterization and communicate over SMB remote procedure call (RPC) pipes. High latency, packet jitter, or minor OS version discrepancies cause the CAPT engine to lose synchronization, resulting in dropped jobs, communication timeouts, or driver crashes.
Windows printer sharing relies on MS-RPRN (Print System Remote Protocol) transported over SMB named pipes (\pipe\spoolss).
Following the discovery of the catastrophic PrintNightmare vulnerabilities (CVE-2021-34527 and CVE-2021-1675), Microsoft permanently hardened the Windows Print Spooler:
- RPC Packet Privacy (
RpcAuthnLevelPrivacyEnabled = 1): Microsoft mandated packet-level encryption and integrity authentication for all RPC communications. Connecting clients that do not negotiate this level fail immediately with error0x0000011b. - Restricting Point-and-Print (
RestrictDriverInstallationToAdministrators = 1): Windows blocked standard users from automatically downloading and installing print drivers from shared printer hosts, producing error0x00000709or0x0000007c. - SMB v2/v3 Signing Checks: Security baselines drop unauthenticated guest connections, preventing machines in different workgroups or subnets from accessing shared printers without identical domain accounts.
Applying registry workarounds to bypass these mitigations leaves machines vulnerable to remote code execution and is regularly reverted by subsequent Windows cumulative updates.
Many administrators attempt to bypass Windows sharing using alternative hardware, only to hit fundamental technical road-blocks:
-
Hardware USB-to-LAN Print Server Dongles (TP-Link, D-Link, HP JetDirect):
- These devices operate strictly as simple TCP socket gateways (Raw Port 9100 / AppSocket) or LPR/LPD forwarders.
- They transmit data blindly to the USB port, expecting the printer to have an onboard PostScript or PCL processor.
- With a host-based CAPT printer, the dongle sends bytes, but the printer has no onboard RIP to decode them and cannot perform the required bidirectional USB status handshake. Result: Zero pages printed, printer remains dead silent.
-
Raspberry Pi with Linux CUPS (
ccpdNightmare):- Setting up CUPS on a Raspberry Pi or Linux box requires Canon's proprietary Linux drivers (
cndrvcups-captand theccpddaemon). - Canon never officially compiled or supported these drivers for modern ARM64 Linux kernels.
- The community reverse-engineered wrappers are notoriously unstable: the
ccpddaemon regularly crashes upon USB re-enumeration, consumes 100% CPU when paper runs out, and silently drops multi-page print jobs.
- Setting up CUPS on a Raspberry Pi or Linux box requires Canon's proprietary Linux drivers (
In modern environments:
- macOS & iOS (Apple AirPrint) natively communicate via RFC 8011 IPP over HTTP/HTTPS with mDNS ZeroConf discovery. Apple devices have no support for Windows SMB RPC named pipes (
\pipe\spoolss) and cannot run proprietary Windows GDI/CAPT drivers. - Android utilizes the Mopria standard or CUPS IPP Everywhere.
- Without a protocol translation bridge, mobile and macOS devices are completely incapable of printing to host-based USB printers.
When multiple network clients print at the same time through Windows SMB:
- The host spooler spawns concurrent asynchronous worker threads.
- Host-based printers require a continuous, serialized stream of data into the USB pipe.
- When concurrent print jobs compete for the single USB endpoint, the spooler either deadlocks, cancels jobs, or interleaves pages between separate users' documents.
A true network IP printer satisfies five fundamental criteria:
- Sovereign IP Address & Standard Ports: Accessible directly over IP (e.g. port
6310for IPP, port9200for high-speed TCP) across subnets and VLANs. - Industry-Standard Driverless Protocol (RFC 8011 IPP): Complies with IPP Everywhere / AirPrint. Any modern device prints using its built-in OS print dialog (
Ctrl+P, Share -> Print) with zero external driver downloads. - Decoupled Client & Host Rendering: The client outputs standard document formats (PDF, PWG-Raster, PostScript); the host bridge handles hardware-specific translation.
- Deterministic Sequential Queueing: Concurrency is managed through an atomic FIFO queue that guarantees zero spooler deadlocks and zero page interleaving.
- Zero-Configuration Discovery: Automatically announces its availability via UDP ZeroConf/mDNS on the local subnet.
ZPrint runs as a lightweight, zero-dependency bridge service on the Windows PC physically connected to the USB printer. It decouples the network ingestion layer from the physical device execution:
[ Client Workstations & Mobile Devices ]
(iOS, Android, macOS, Linux, Windows)
|
| RFC 8011 IPP (HTTP / Port 6310) OR ZPrint ZeroLz4 TCP (Port 9200)
v
+========================================================================+
| ZPrint Host Bridge Engine |
| |
| 1. Network Ingestion Layer |
| - RFC 8011 IPP Server (application/ipp, application/pdf, PWG-Raster)|
| - ZeroLz4 Wire Protocol Server (Pure C# 1.6 GB/s decompressor) |
| - UDP 9201 ZeroConf LAN Auto-Discovery Responder |
| |
| 2. Serialized FIFO Job Queue (`PrintJobQueue`) |
| - Atomic queue serializer with memory backpressure |
| - Guarantees 0% page interleaving and 0% collision deadlocks |
| |
| 3. Win32 Direct Kernel Spooler Subsystem (`winspool.drv` RAW) |
| - Injects print stream directly into local spooler in RAW mode |
| - Native local Canon/HP driver handles CAPT/GDI USB communication |
| - COMPLETELY BYPASSES Windows SMB & MS-RPRN network security stack |
+========================================================================+
|
| USB Bidirectional CAPT / GDI Handshake
v
[ Dumb USB Printer: Canon LBP 2900 / HP LaserJet 1020 ]
Instead of exposing the Windows Spooler over the network via vulnerable SMB named pipes (\pipe\spoolss), ZPrint receives print jobs over standard HTTP/IPP or TCP and injects them locally into the Win32 print subsystem via low-level P/Invoke calls:
OpenPrinterStartDocPrinterWritePrinterEndDocPrinterClosePrinter
By specifying data type "RAW", ZPrint delivers the payload directly to the locally installed official manufacturer driver (e.g. Canon official Windows driver).
Key Benefits:
- Complete Immunity to
0x0000011band0x00000709: Because the spooler call is 100% local to the host PC, Windows network RPC packet privacy checks (RpcAuthnLevelPrivacyEnabled) and Point-and-Print restrictions are never triggered. - 100% Hardware Compatibility: The official Canon/HP driver handles the complex USB timing, bidirectional engine polling, and CAPT encoding locally with hardware perfection.
- No Driver Installation on Clients: Remote clients simply speak standard IPP or send documents to ZPrint; they never need the manufacturer driver.
When printing high-resolution 1200 DPI graphics or complex drawings, uncompressed raster print files can easily exceed 40–80 MB per document. On crowded office 2.4 GHz Wi-Fi networks, this causes severe network congestion and transmission delays.
ZPrint integrates ZeroLz4, a pure C# high-speed compression engine:
- 1.6 GB/s decompression speed on standard multi-core CPUs with zero heap allocations (
Span<T>and pooled memory). - 70%–85% bandwidth reduction, compressing a 30 MB document down to 4 MB for lightning-fast over-the-wire transit.
- Sub-millisecond transfer times, ensuring immediate printer response.
To eliminate spooler deadlocks and corrupted output from simultaneous printing:
- ZPrint's
PrintJobQueueutilizes lock-free synchronization primitives (Channel<T>and atomic counters). - When multiple clients hit print at the same instant, ZPrint queues the jobs sequentially, writes them to isolated buffer storage, and streams them to the local printer one by one.
- Guarantees 0% page interleaving and eliminates concurrent buffer overflows.
+------------------------------------------+
| Client Nodes |
| |
| [macOS / iOS] [Linux] [Windows PC] |
| (AirPrint) (CUPS) (Ctrl+P) |
+-------+-------------+------------+-------+
| | |
RFC 8011 IPP | | | ZPrint CLI / Tool
(application/ipp) | | | (ZeroLz4 TCP)
v v v
+------------------------------------------+
| ZPrint Host Server Node |
| |
| +--------------------+ +------------+ |
| | ZPrintIppServer | | TCP Server | |
| | (Port 6310) | | (Port 9200)| |
| +---------+----------+ +-----+------+ |
| | | |
| | (ZeroLz4 Decomp)| |
| +---------+---------+ |
| | |
| v |
| +-------------------+ |
| | PrintJobQueue | |
| | (FIFO Serializer)| |
| +---------+---------+ |
| | |
| v |
| +-------------------+ |
| | WindowsSpooler | |
| | (winspool.drv RAW)| |
| +---------+---------+ |
| | |
+----------------------|-------------------+
v
[Canon LBP 2900 / HP 1020 / USB]
| Feature | Windows SMB Share (\\host\printer) |
Dedicated Hardware Print Server | ZPrint Bridge |
|---|---|---|---|
| Canon LBP 2900 / CAPT Support | ❌ Unreliable / Crashes | ❌ Fails (No CAPT on hardware) | 100% Native & Stable |
| 0x0000011b & 0x00000709 Errors | ❌ Frequent | Immune (Direct RAW Spool) | |
| Driverless Printing (No Client Driver) | ❌ Driver required on every PC | Native (AirPrint / IPP) | |
| macOS & iOS (AirPrint) | ❌ Not supported | Plug & Play | |
| Android & Linux (CUPS) | ❌ Complex SMB setup | Standard IPP Everywhere | |
| Wire Compression | ❌ None (Raw network SMB) | ❌ None | ZeroLz4 (1.6 GB/s) |
| Concurrent Job FIFO Queue | Thread-safe FIFO Queue | ||
| Automatic LAN Discovery | UDP 9201 in < 1.5s | ||
| Cost | Free (but buggy) | $40 – $100 per device | Free & Open Source |
Connect your printer to a Windows PC via USB and start the server:
# Automatically picks your Windows default printer
zprint server
# Or specify a printer explicitly
zprint server --printer "Canon LBP2900"To detach from the console and run silently in the background:
zprint server --printer "Canon LBP2900" --backgroundThe console window immediately hides. Logs are written to %LOCALAPPDATA%\ZPrint\zprint-server.log.
No Canon or manufacturer driver needed on the client PC!
- Open Settings -> Bluetooth & devices -> Printers & scanners -> Add device.
- Click Add manually (The printer that I want isn't listed).
- Select Select a shared printer by name and enter:
http://<SERVER_IP>:6310/ipp/printers/canon - Click Next. Windows automatically binds the native Microsoft IPP Class Driver.
- You're ready to print! Use
Ctrl+Pin any application.
- Open System Settings -> Printers & Scanners -> Add Printer, Scanner, or Fax.
- Select the IP tab (Globe icon).
- Enter settings:
- Address:
<SERVER_IP>:6310 - Protocol:
Internet Printing Protocol - IPP - Queue:
/ipp/ - Name:
Canon LBP2900 (Network) - Use:
Generic PostScript Printer(orAuto Select)
- Address:
- Click Add.
Run via terminal or add through GNOME / KDE Printer Settings:
# Register driverless IPP printer with CUPS
lpadmin -p ZPrint_Canon -E -v ipp://<SERVER_IP>:6310/ipp/ -m everywhere
# Verify printer status
lpstat -p ZPrint_Canon- Ensure your iPhone/iPad is connected to the same Wi-Fi network.
- In any app (Safari, Photos, Mail, Files), tap the Share button -> Print.
- Tap Select Printer.
- Tap Canon LBP2900 (detected automatically via IPP/mDNS).
- Tap Print.
- Open Settings -> Connected devices -> Connection preferences -> Printing.
- Select Default Print Service or Mopria Print Service.
- Choose Add printer by IP address:
- Address:
<SERVER_IP>:6310
- Address:
- Print directly from Chrome, Google Drive, or Gallery.
ZPrint also provides a high-performance desktop client for batch printing:
# Drag & drop any PDF/file onto zprint.exe, or run:
zprint print invoice.pdf
# Specify page ranges and multiple copies:
zprint print contract.pdf --pages "1, 3, 5-8" --copies 2
# Discover all active ZPrint servers on the LAN:
zprint listOutput:
Machine Name IP Address TCP Port IPP Port Shared Printers
------------------------------------------------------------------------------
DESKTOP-PRINT-01 192.168.1.105 9200 6310 Canon LBP2900
Configures ZPrint to start silently in the background whenever the current user logs into Windows:
# Enable autostart with specific printer
zprint autostart enable --printer "Canon LBP2900"
# Check current autostart status
zprint autostart status
# Disable autostart
zprint autostart disablePlatform Implementation: Windows Registry HKCU\Software\Microsoft\Windows\CurrentVersion\Run | Linux ~/.config/autostart/zprint.desktop | macOS ~/Library/LaunchAgents/.
Configures ZPrint to start as a background system service when the machine boots up, even before any user logs in.
Important
Must be executed from an elevated terminal (Run as Administrator on Windows, or sudo on Linux).
# Install and register system boot task
zprint service install --printer "Canon LBP2900"
# Start the service immediately
zprint service start
# Check service status
zprint service status
# Stop service
zprint service stop
# Uninstall service
zprint service uninstallPlatform Implementation: Windows Task Scheduler (schtasks.exe /sc onstart /ru SYSTEM /rl HIGHEST) | Linux systemd unit (/etc/systemd/system/zprint.service).
ZPrint integrates seamlessly with ZeroUniverse's ZUpdate engine for atomic, in-place binary upgrades:
# Check if a new version is available on GitHub Releases
zprint update --check
# Download package and perform atomic in-place upgrade
zprint update
# Force download and reinstall current or newer version
zprint update --force
# Suppress user confirmation prompts during update execution
zprint update --silentUsage: zprint <command> [options]
Commands:
server Start the print server daemon on the host PC
print <file> Send a document to a ZPrint server
list Discover all active ZPrint servers on the LAN
autostart <action> Configure user login autostart (enable, disable, status)
service <action> Manage system boot service (install, uninstall, start, stop, status)
update Check or perform atomic in-place updates via ZUpdate
install-printer Display driverless IPP setup instructions for all platforms
Server Options:
--port <port> Custom TCP port for ZPrint protocol (default: 9200)
--ipp <port> Custom IPP port for AirPrint/driverless clients (default: 6310)
--printer <name> Target local printer name (default: Windows default printer)
--background, -b Run daemon silently in background (hides console window)
--no-ipp Disable RFC 8011 IPP server
--no-discovery Disable UDP LAN auto-discovery responder
Print Options:
--server <ip:port> Target ZPrint server (auto-discovered if omitted)
--printer <name> Target printer name on remote server
--pages <range> Page range filter (e.g., "1, 3, 5-8", "2-")
--copies <num> Number of copies (default: 1)
Update Options:
--check Check GitHub Releases without downloading or replacing binaries
--force Force download and reinstall even if already up-to-date
--silent Execute update without interactive console prompts
ZPrint adheres strictly to the ZeroUniverse engineering philosophy:
- 0 External NuGet Packages: Every byte of networking, compression, serialization, and protocol parsing is implemented with pure C# BCL.
- Ultra-Lightweight Footprint: Memory usage typically stays under 15 MB RAM, making it ideal for running continuously in the background on office PCs or dedicated print boxes.
- Sovereign Reliability: No third-party dependency vulnerabilities, no version drift, and instant cold startup.
dotnet build ZPrint.slnxdotnet test ZPrint.slnxIn accordance with ZeroUniverse publication guidelines (framework-dependent single file):
dotnet publish src/ZPrint.Tool/ZPrint.Tool.csproj -c Release -r win-x64 --self-contained false -p:PublishSingleFile=true -o publish/zprint-win-x64This project is licensed under the MIT License.
Copyright (c) 2026 Phong Võ (kzxl) / ZeroUniverse. All rights reserved.