“ help ! I ’ m an IT System Administrator that needs to provide unauthenticated printing from multiple systems and clients to a Windows Server ! How do I achieve this ? ”
If your requirements don ’ deoxythymidine monophosphate involve unauthenticated printing, we would recommend for you take to take a expression at PaperCut NG/MF ’ s alternate features to enable macOS and Linux printing :

What’s this all about then?

The Line Printer Daemon protocol ( LPD ) and Line Printer Remote protocol ( LPR ) refer to a net protocol for submitting print jobs to a printer or print server, alike to SMB or IPP. Sometimes these terms are used interchangeably, but to be precise, LPR refers to the protocol used by the client to send a print caper, whereas LPD refers to the service running on the server .
IT System Administrators building a print network to support varying systems ( such as Windows, macOS, Linux etc. ) have long relied on the Windows LPD Services as a commodious way to get print jobs onto a Windows Print Server. One of the attractive features of LPR is the interoperability that clients connecting to the LPD service aren ’ t required to authenticate. The LPD overhaul will just accept print jobs with fiddling examination via this service and print them to end devices using the queues the server hosts .
This serve is provided by Microsoft, but with the second coming of Windows Server 2012 the original Windows LPD Service has since been deprecated. The LPD service on Windows Server can still be used – but at some point in the future it may be removed. At PaperCut we see environments where these protocols are used when there is a significant mix of clients are show, such as :

  • macOS Clients/Servers.
  • Linux Clients/Servers.
  • AS400 Servers.
  • Mainframes.
  • ERP systems (such as SAP).

LPD/LPR implementations are not without their quirks though when working with PaperCut NG/MF, so use this article as a guide to minimize these unexpected behaviors .

PaperCut LPD Service


From v15.1 onwards, PaperCut NG/MF comes bundled with the PaperCut LPD Service with a ace vogue installer. The installer charge is located here : [app-path]\PaperCut NG/MF\providers\lpd\win\pc-lpd-installer.exe
The PaperCut LPD Service listens on port 515 by nonpayment, so IT System Administrators need to ensure network security services or the print server ’ s firewall don ’ deoxythymidine monophosphate interfere with connections to this port. The installation sorcerer besides checks for the Windows LPD Service and disables it to prevent port conflicts .
Please note : Unlike Microsoft ’ south execution, the PaperCut LPD Service requires sharing the printer for clients to be able to connect to it via LPR. Through the application ’ s photographic print queue monitoring and restriction abilities, PaperCut NG/MF ’ south execution provides an extra level of control over print queue sharing over LPR. There international relations and security network ’ triiodothyronine a requirement for license settings on the queue, so Windows users can still be prevented from connecting to these shares .

Connecting to the service

Most operating systems, including Windows, accompaniment connecting to an LPD Service via the LPR print protocol. here is the information you need :

  1. The address of the server running the PaperCut LPD Service.
  2. The name of the queue. (Either the share name or queue name will work.)

Please note : Some operating systems won ’ deoxythymidine monophosphate give up spaces in the queue identify, so a share or line up name that does not include spaces greatly improves the likelihood of a joining .

Example – CUPS (macOS & Linux)

  1. Login to the CUPS Administration web UI by pointing your client computer’s web browser to http://localhost:631.
  2. Click Administration >> Add Printer
  3. Scroll to Other Network Printers and choose LPD/LPR Host or Printer.

  1. Enter the connection string using either or a Hostname or IP Address, such as: lpd://hostname/queue or lpd://
  2. Finish creating the CUPS queue by entering the Name, Description, Location etc.
  3. Choose the driver and finish the install with the Add Printer button.

Final considerations

It ’ randomness authoritative at this point to consider how print jobs are tracked. LPD/LPR jobs are sent with the username belong to the client machine ’ south stream log-on seance. If the log-on username international relations and security network ’ thymine consistent with the PaperCut username you wish to bill the print job to, you may need to consider extra PaperCut NG/MF features like :

  • Username aliasing.
  • Unauthenticated printing.
  • Enabling the ‘Override user-level settings’ at a given queue and charging all jobs to a given Shared Account if this queue services a single account.


PaperCut LPD Service

q Can I remove the IP address from the username seen in the Windows print queue ?

Heck yes ! The PaperCut LPD Service added an option in the pc-lpd.config file to enable the host cover to be removed from the job owner ’ randomness name ( RemoveHostAddress = true ) .
Q Why do print jobs fail when non-ASCII characters are used in either the mark job list or the username ?
Check out this article on fixing encoding problems in the relevant mark line up.

[Legacy] Windows’ LPD Service

Q The print jobs don ’ triiodothyronine come out of the printer and just disappear. What ’ south going on ?
The most likely reason for this is the use of “ Class ”, “ Mode 4, ” or “ Type 4 ” printer drivers on the Windows server ’ s print queue. The way the Windows Print Spooler works with these newer types of drivers means jobs from macOS or Linux clients won ’ thyroxine print .
If you ’ re in this situation, we recommend using an equivalent type 3 driver from the same driver manufacturer. If your administration has a requirement for Type 4 drivers, we suggest duplicating the print queue with a type 3 driver in this scenario .
Q The wrong username is associated with the print jobs, what gives ?
One of the challenges we hear of when printing via the LPD protocol is that the print jobs are logged in PaperCut NG/MF with the wrong username. This may happen because an ERP system is actually submitting the mark job on behalf of the user, which is why the username will appear to be “ SYSTEM ” or the name of the overhaul account that the ERP arrangement is running angstrom .
fortunately, with PaperCut ’ s NG/MF ’ s Enterprise Environment Username Extraction sport it ’ s potential to accurately attribute these enterprise system-generated print jobs to PaperCut users .
Q Sometimes we see print jobs disappear occasionally, what ’ second happen ?
The other problem encountered with Windows LPD print is when photographic print jobs disappear with an mistake message “ A print job was attempted to be unpaused ” in the PaperCut NG/MF logs. This may happen because the Windows Print Spooler service is able to resume LPR mark jobs which PaperCut NG/MF has paused for analysis or Find-Me impression, at which point PaperCut NG/MF attempts to cancel the resume job .

If after reading this article you decide that you still must use the deprecate Windows LPD Service then here ’ s our advice to avoid problems :
Set up freestanding mark queues ( or a Find-Me print queue ) entirely for LPR printing. This makes troubleshooting much simple because now LPR jobs have been isolated into their own print queue. Plus, you can give the mark line up a share name suitable for *UNIX systems ( e.g. ASCII only with no spaces ). Pause the LPR print queue, this will prevent the Windows Spooler from bypassing PaperCut NG/MF ’ s control. To do this :

  1. Open


    .msc on the Windows server

  2. Right click on the LPR print queue and choose Pause Printing.

normally if you do this Windows users will see a confuse balloon telling when they try to print that “ the queue is paused ”, but since you set up a separate mark line up entirely for LPR print this won ’ thymine be a problem .

Still have questions?

Let us know ! We love chatting about what ’ s going on under the hood. Feel free to leave a gloss below or visit our Support Portal for far aid.

Categories : How-to Articles, Print Queues
Keywords : Windows, macOS, Linus, Unix, ERP, Mainframe, AS400, unauthenticated, LPD, LPR, bequest