PaperCut LPD Service

KB Home   |   PaperCut LPD Service

Main.PaperCutLPDService History

Hide minor edits - Show changes to output

September 23, 2019, at 07:26 AM by timg - Link updates
Changed line 53 from:
A: The most likely reason for this is the use of "Class", "Mode 4," or "Type 4" printer drivers on the Windows print queue. The way the Windows Print Spooler works with these new drivers means jobs from Linux or macOS clients won't print, and in this situation, we recommend using equivalent Type 3 drivers. If your organization has a requirement for Type 4 drivers (e.g. [[WindowsRT]]), we suggest duplicating the print queue with a Type 3 driver.
to:
A: The most likely reason for this is the use of "Class", "Mode 4," or "Type 4" printer drivers on the Windows print queue. The way the Windows Print Spooler works with these new drivers means jobs from Linux or macOS clients won't print, and in this situation, we recommend using equivalent Type 3 drivers. If your organization has a requirement for Type 4 drivers, we suggest duplicating the print queue with a Type 3 driver.
September 20, 2018, at 11:43 PM by Arturo - clarity, grammar
Changed lines 24-27 from:
The LPD Service listens on port 515 by default, so Administrators will need to ensure that this port is open to requests from clients (check that the port is not blocked by your firewall). The installation wizard will also check for previous versions of the Windows LPD Service  and disable these to ensure there is no port conflict.

'''Note:'''  The PaperCut LPD Service requires that you share the printer before being able to connect to it via LPR. This is different from Microsoft’s implementation, but provides an extra level of control
over which queues can be printed to via LPR. No permissions need to be set on the queue, so Windows users can still be prevented from connecting to these shares.
to:
The LPD Service listens on port 515 by default, so Administrators need to ensure network security services or the print server's firewall don't interfere with connections to the port. The installation wizard also checks for the Windows LPD Service and disables it to prevent port conflicts.

'''Note:'''  Unlike Microsoft’s implementation, the PaperCut LPD Service requires sharing the printer for clients to be able to connect to it via LPR. Through the application's print queue monitoring and restriction abilities, PaperCut's implementation provides an extra level of control over print queue sharing
over LPR. There isn't a requirement for permission settings on the queue, so Windows users can still be prevented from connecting to these shares.
Changed line 29 from:
Most operating systems, including Windows, support connecting to an LPD Service via the LPR printing protocol. The information you will need is;
to:
Most operating systems, including Windows, support connecting to an LPD Service via the LPR printing protocol. Here is the information you need:
Changed lines 31-33 from:
*The name of the queue. Either share name or queue name will work.
'''Note:''' Some systems won’t allow spaces in queue names, so a share or queue name that does not include spaces will improve likelihood of connection.
to:
*The name of the queue. Either the share name or queue name work.
'''Note:''' Some systems won’t allow spaces in queue names, so a share or queue name that does not include spaces improves the likelihood of connection.
Changed line 35 from:
#Log into the CUPS Administration UI
to:
#Log into the CUPS Administration UI by pointing your client computer's web browser to @@http://localhost:631/@@.
Changed lines 38-39 from:
#Enter in the connection string using the example format on the page. i.e.[[<<]]@@lpd://hostname/queue@@[[<<]]@@lpd://10.100.65.38/Global@@[[<<]]Noting again, queue name can be either the share name or print queue name on the Print Server and in the case of CUPS cannot contain spaces.
#Create the CUPS queue entering in the rest of the required information, such as
Name, Description, Location etc.
to:
#Enter the connection string formatted like one of these examples:[[<<]]@@lpd://hostname/queue@@[[<<]]@@lpd://10.100.65.38/Global@@[[<<]]Noting again, queue name can be either the share name or print queue name on the Print Server and should not contain spaces.
#Finish creating the CUPS queue by entering the
Name, Description, Location etc.
Deleted line 42:
Print jobs will be accepted via LPD into the Windows printing system.
Changed line 44 from:
It’s important at this point to consider how the print jobs are being tracked. The print jobs will be sent with the username from the client system: i.e. the Unix, Linux, Mac, etc username associated with the print job. If the username isn’t consistent with the Windows username you wish to bill the job for, you may need to consider additional PaperCut features like:
to:
It’s important at this point to consider how print jobs are tracked. LPD/LPR jobs are sent with the username belonging to the client machine's current log-on session. If the log-on username isn’t consistent with the PaperCut username you wish to bill the job to, you may need to consider additional PaperCut features like:
Changed lines 47-48 from:
*Enable the ‘Override user-level settings’ at a given queue and charge all jobs to a given Shared Account if this queue services a single account.
to:
*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.
Changed lines 53-58 from:
A: The most likely reason for this is the use of Mode 4 or Type 4 printer drivers on the Windows Print queue. Due to changes in the way the Windows Print Spooler works with these new drivers you can not use a Non-Windows Mode 4 driver to print to the queue.

In this situation we recommend that you use Mode 3 or
Type 3 drivers.

If you must use Mode 4 / Type 4 (e.g. [[WindowsRT]]) then we suggest that you have duplicate print queues setup, perhaps on a [[SecondaryServerSoftware]]

to:
A: The most likely reason for this is the use of "Class", "Mode 4," or "Type 4" printer drivers on the Windows print queue. The way the Windows Print Spooler works with these new drivers means jobs from Linux or macOS clients won't print, and in this situation, we recommend using equivalent Type 3 drivers. If your organization has a requirement for Type 4 drivers (e.g. [[WindowsRT]]), we suggest duplicating the print queue with a Type 3 driver.
Changed line 57 from:
A: Check out this article on: [[https://www.papercut.com/kb/Main/PaperCutLPDUnintelligibleCharactersInJobQueue|Fixing encoding problems/unintelligible characters appearing in PaperCut LPD job queue]].
to:
A: Check out this article on [[https://www.papercut.com/kb/Main/PaperCutLPDUnintelligibleCharactersInJobQueue|fixing encoding problems]] in the print queue.
September 01, 2016, at 10:53 PM by timg - Added link to Unicode issue KB
Changed lines 50-54 from:
! Troubleshooting
!! Print jobs don't come out. They just disappear!

The
most likely reason for this is the use of Mode 4 or Type 4 printer drivers on the Windows Print queue. Due to changes in the way the Windows Print Spooler works with these new drivers you can not use a Non-Windows Mode 4 driver to print to the queue.
to:
!! Troubleshooting

Q: Print jobs don't come out. They just disappear. What's going on?

A:
The most likely reason for this is the use of Mode 4 or Type 4 printer drivers on the Windows Print queue. Due to changes in the way the Windows Print Spooler works with these new drivers you can not use a Non-Windows Mode 4 driver to print to the queue.
Added lines 59-62:

Q: Why do jobs fail when non-ASCII characters are used in either the jobname or the username?

A: Check out this article on: [[https://www.papercut.com/kb/Main/PaperCutLPDUnintelligibleCharactersInJobQueue|Fixing encoding problems/unintelligible characters appearing in PaperCut LPD job queue]].
March 09, 2016, at 01:04 AM by tim shimmin - fix grammar - double "also"
Changed line 24 from:
The LPD Service listens on port 515 by default, so Administrators will need to ensure that this port is open to requests from clients (check that the port is not blocked by your firewall). The installation wizard will also check for previous versions of the Windows LPD Service also, and disable these to ensure there is no port conflict.
to:
The LPD Service listens on port 515 by default, so Administrators will need to ensure that this port is open to requests from clients (check that the port is not blocked by your firewall). The installation wizard will also check for previous versions of the Windows LPD Service  and disable these to ensure there is no port conflict.
March 09, 2016, at 01:02 AM by tim shimmin - fix formatting of AS400
Changed line 12 from:
*`AS400 Servers
to:
*[=AS400=] Servers
Added lines 49-57:

! Troubleshooting
!! Print jobs don't come out. They just disappear!

The most likely reason for this is the use of Mode 4 or Type 4 printer drivers on the Windows Print queue. Due to changes in the way the Windows Print Spooler works with these new drivers you can not use a Non-Windows Mode 4 driver to print to the queue.

In this situation we recommend that you use Mode 3 or Type 3 drivers.

If you must use Mode 4 / Type 4 (e.g. [[WindowsRT]]) then we suggest that you have duplicate print queues setup, perhaps on a [[SecondaryServerSoftware]]
June 22, 2015, at 05:39 AM by 203.222.91.204 -
Changed lines 9-10 from:
The PaperCut LPD Service allows print network administrators to;
Connect
disparate systems to a Windows Print Server, allowing the server to accept jobs from
to:
The PaperCut LPD Service allows print network administrators to connect disparate systems to a Windows Print Server, allowing the server to accept jobs from:
Changed lines 24-25 from:
LPD Servers listen on port 515 by default, so Administrators will need to ensure that this port is open to requests from clients (check that the port is not blocked by your firewall). The installation wizard will also check for previous versions of the Windows LPD Server also, and disable these to ensure there is no port conflict.
to:
The LPD Service listens on port 515 by default, so Administrators will need to ensure that this port is open to requests from clients (check that the port is not blocked by your firewall). The installation wizard will also check for previous versions of the Windows LPD Service also, and disable these to ensure there is no port conflict.
Changed line 45 from:
It’s important at this point to consider how the print jobs are being tracked. The print jobs will be sent with the username from the client system; i.e. the Unix, Linux, Mac, etc username associated with the print job. If the username isn’t consistent with the Windows username you wish to bill the job for you may need to consider additional PaperCut features like;
to:
It’s important at this point to consider how the print jobs are being tracked. The print jobs will be sent with the username from the client system: i.e. the Unix, Linux, Mac, etc username associated with the print job. If the username isn’t consistent with the Windows username you wish to bill the job for, you may need to consider additional PaperCut features like:
June 04, 2015, at 03:13 AM by 203.222.91.204 -
Changed line 13 from:
*AS400 Servers
to:
*`AS400 Servers
Changed line 52 from:
''Categories:'' [[Category.Architecture|+]], [[Category.Implementation / Deployment|+]]
to:
''Categories:'' [[Category.Architecture|+]], [[Category.Implementation|+]]
June 04, 2015, at 03:12 AM by 203.222.91.204 -
Deleted line 1:
Added lines 23-24:
Attach:LPD_install.png
Changed line 38 from:
#Scroll to Other Network Printers and choose ‘LPD/LPR Host or Printer’
to:
#Scroll to Other Network Printers and choose ‘LPD/LPR Host or Printer’[[<<]]Attach:LPD_CUPS_01.png
Changed lines 41-43 from:
#Choose the driver and finish the install with Add Printer

to:
#Choose the driver and finish the install with Add Printer[[<<]]Attach:LPD_CUPS_02.png

Changed line 52 from:
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
to:
''Categories:'' [[Category.Architecture|+]], [[Category.Implementation / Deployment|+]]
Changed line 54 from:
[-Keywords: TODO keywords here if needed-]
to:
[-Keywords: PSFU, Print Services for Unix, Windows TCP/IP Services, LPD, LPR]
June 04, 2015, at 03:01 AM by 203.222.91.204 -
Changed line 28 from:
!!Connecting to an LPD Service
to:
!!!Connecting to an LPD Service
Changed line 34 from:
!!!An example in CUPS
to:
!!!!An example in CUPS
Changed lines 38-39 from:
#Enter in the connection string using the example format on the page. i.e.\\lpd://hostname/queue\\lpd://10.100.65.38/Global
Noting again, queue name can be either the share name or print queue name on the Print Server and in the case of CUPS cannot contain spaces.
to:
#Enter in the connection string using the example format on the page. i.e.[[<<]]@@lpd://hostname/queue@@[[<<]]@@lpd://10.100.65.38/Global@@[[<<]]Noting again, queue name can be either the share name or print queue name on the Print Server and in the case of CUPS cannot contain spaces.
Changed lines 46-47 from:
*Username aliasing 
*Unauthenticated printing
to:
*[[https://www.papercut.com/kb/Main/UserNameAliasing|Username aliasing]]
*[[https://www.papercut.com/products/ng/manual/ch-auth-print-laptop.html#id636842|Unauthenticated printing]]
Deleted lines 49-50:
TODO link your page here: https://www.papercut.com/kb/Main/Miscellaneous
Changed line 53 from:
[-Keywords: TODO keywords here if needed-]
to:
[-Keywords: TODO keywords here if needed-]
June 04, 2015, at 02:55 AM by 203.222.91.204 -
Added lines 1-56:
(:title PaperCut LPD Service:)

Administrators building a print network to support cross platform printing have long relied on the Windows LPD Services as a convenient way to get print jobs onto a Windows Print Server from a variety of clients. Historically, this service was provided by Windows from Windows NT onwards to support printing from Unix systems.

One of the attractive features of this type of interoperability is that clients connecting to the LPD service aren’t required to authenticate. The LPD service will simply accept print jobs with little scrutiny via this service and print them to end devices using the queues the server hosts.

With Microsoft announcing that the LPD service will shortly be deprecated, PaperCut now ships with its own LPD Service, to continue support for this method of print networking, and to provide end-to-end support for customers that use PaperCut and LPD.

!!Using the PaperCut LPD Service
The PaperCut LPD Service allows print network administrators to;
Connect disparate systems to a Windows Print Server, allowing the server to accept jobs from
*Mac Clients/Servers
*Linux Clients/Servers
*AS400 Servers
*Mainframes
*...any other client or server that supports LPR printing (LPD is the ‘server’, LPR is the client)
*Bypass any authentication requirements to print to a Windows Server

!!!Installing the PaperCut LPD Service
PaperCut v15.1 or later server installations will ship the PaperCut LPD Service with a wizard style installer.

@@[appath]\providers\lpd\win\pc-lpd-installer.exe@@

LPD Servers listen on port 515 by default, so Administrators will need to ensure that this port is open to requests from clients (check that the port is not blocked by your firewall). The installation wizard will also check for previous versions of the Windows LPD Server also, and disable these to ensure there is no port conflict.

'''Note:'''  The PaperCut LPD Service requires that you share the printer before being able to connect to it via LPR. This is different from Microsoft’s implementation, but provides an extra level of control over which queues can be printed to via LPR. No permissions need to be set on the queue, so Windows users can still be prevented from connecting to these shares.

!!Connecting to an LPD Service
Most operating systems, including Windows, support connecting to an LPD Service via the LPR printing protocol. The information you will need is;
*The address of the server running the PaperCut LPD Service.
*The name of the queue. Either share name or queue name will work.
'''Note:''' Some systems won’t allow spaces in queue names, so a share or queue name that does not include spaces will improve likelihood of connection.

!!!An example in CUPS
#Log into the CUPS Administration UI
#Click Administration >> Add Printer
#Scroll to Other Network Printers and choose ‘LPD/LPR Host or Printer’
#Enter in the connection string using the example format on the page. i.e.\\lpd://hostname/queue\\lpd://10.100.65.38/Global
Noting again, queue name can be either the share name or print queue name on the Print Server and in the case of CUPS cannot contain spaces.
#Create the CUPS queue entering in the rest of the required information, such as Name, Description, Location etc.
#Choose the driver and finish the install with Add Printer


Print jobs will be accepted via LPD into the Windows printing system.
!!Next steps
It’s important at this point to consider how the print jobs are being tracked. The print jobs will be sent with the username from the client system; i.e. the Unix, Linux, Mac, etc username associated with the print job. If the username isn’t consistent with the Windows username you wish to bill the job for you may need to consider additional PaperCut features like;
*Username aliasing
*Unauthenticated printing
*Enable the ‘Override user-level settings’ at a given queue and charge all jobs to a given Shared Account if this queue services a single account.

TODO link your page here: https://www.papercut.com/kb/Main/Miscellaneous

----
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
----
[-Keywords: TODO keywords here if needed-]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on September 23, 2019, at 07:26 AM
Printable View   |   Article History   |   Edit Article