Press CTRL+K to open search

Printing to Pharos Uniprint from Non-Windows Platforms

  • Updated on Oct 19, 2026
  • Published on Mar 19, 2024
  • 2 minute(s) read
Prev Next

Overview

Pharos Uniprint server components run on supported Windows platforms. Non-Windows clients can submit print jobs to a Pharos Uniprint system through TCP/IP printing when the Pharos LPD Server and the client platform are configured for a compatible workflow.

The Pharos LPD Server uses the RFC1179 Line Printer Daemon protocol. Jobs received by the LPD Server enter Pharos spool queues, where Uniprint can control and cost them.

Applies to

  • Pharos Uniprint Print Server on Windows.

  • UNIX and Linux clients that support RFC1179 LPR or LPD printing.

  • MacOS clients that support LPR or LPD printing.

  • Other non-Windows platforms that provide RFC1179-compatible printing software.

  • This article covers LPD printing only. It does not cover Pharos Cloud, MobilePrint, Print Scout, Popup Client, or IPP workflows.

Before you start

  • Confirm the Uniprint version and the supported client platforms for your deployment.

  • Confirm that the Pharos LPD Server is installed on a supported Print Server.

  • Confirm that the client can connect to the Pharos Print Server over the required TCP/IP path.

  • Confirm the intended Pharos queue name and the user identity or costing requirements.

  • Check whether another LPD or TCP/IP print service is already using the required endpoint.

  • For MacOS and Linux deployments, verify how the client supplies the print-job username before deploying broadly.

Steps

  1. Install and configure the Pharos LPD Server by following the installation documentation for your Uniprint version.

  2. Confirm that the Pharos LPD Server is running and that no competing TCP/IP print service is using the same endpoint.

  3. On the non-Windows client, configure an LPR or LPD printer connection to the Pharos Print Server.

  4. Enter the hostname or IP address of the Pharos Print Server.

  5. Enter the Pharos queue name supplied by the Uniprint administrator.

  6. Submit a test print job from the client.

  7. Confirm that the job enters the Pharos-controlled spool queue.

  8. Verify that the job is associated with the expected user identity and costing information.

  9. Release or process the job using the normal Uniprint workflow.

Validation

  • The client can connect to the Pharos Print Server.

  • The test job appears in the expected Pharos queue.

  • Uniprint applies the expected control, authentication, and costing behavior.

  • The job can be released or processed successfully.

  • The recorded username matches the identity expected by the deployment.

  • No competing LPD service or firewall rule prevents subsequent submissions.

Notes

  • Uniprint server components do not run natively on UNIX, Linux, or MacOS through this workflow. The non-Windows platform submits the job to the Windows-based Pharos Print Server.

  • LPD submission is different from IPP, MobilePrint, Print Scout, Popup Client, and Pharos Cloud printing.

  • Support for a specific modern Linux distribution or MacOS release must be confirmed against the applicable product documentation.

  • If the submitted username does not match the expected Pharos identity, review the client authentication and identifier-mapping design before changing the Uniprint configuration.

  • Contact Pharos Technical Support with the Uniprint version, client operating system and version, submission protocol, queue name, and relevant logs if the job does not appear in the Pharos queue.

Related articles