WinLPR

The Windows Line Printer Daemon is an application that runs on your Windows PC, allowing your PC to accept print jobs from any Line Printer Protocol host.
This means you can have your mainframe, UNIX servers, NT servers all print to your PC even if youre not on the same physical or virtual network. You dont need to share your printer with your NT server, and you dont need complex resource sharing software for UNIX.
The LPR protocol is an Internet standard supported by UNIX, NT, and most mainframe systems. It allows any machine that speaks LPR to talk to another machine to arrange a print job.
To accept a print job from a remote host, you need to have a daemon running. The daemon is a small program (WinLPR in this case) which listens for print jobs from a host or hosts, and accepts and prints them.
The daemon must be running to work properly, but it requires no user intervention to function.
WinLPR is also pretty small, simple and easy-to-use.
Here are some key features of "WinLPR":
ï¿­ Start minimized and as service options. Start automatically will run after the user logs in... if you want to accept print jobs before a user logs in, start as a service. Note: to run as a service under Windows NT/2000 requires the NT Service version.
ï¿­ Suppress or allow banner (who it came from) pages for each job and queue.
ï¿­ Confirm job before print, and insert CR/LF to combat "stair step" effect.
ï¿­ Full logging to a file.
ï¿­ Accept jobs from only sanctioned hosts.
ï¿­ Send Printer Control Files before and after print jobs to activate special features of your printer (such as change to landscape mode, etc.)
ï¿­ Create multiple queues for jobs. Each queue can print to a different printer, send leading and trailing control files to the printer to configure it, ask a user for job print confirmation, convert fineleeds to carriage return linefeed pairs and ban or allow hosts to send print jobs.
ï¿­ Take advantage of the "any" queue. The "any" queue is a special queue the WinLPR creates for you. This queue allows you to accept any job, even if you dont know the "proper" queue name it was sent to, and send it to a printer. Again, you can perform manipulations like any other queue.
ï¿­ Hide unnecessary configuration information by turning advanced menus off, minimizing the chances a user will alter settings.
ï¿­ Remote management allowing you to control all settings (except language), turn accept and print job functionality on and off; print a test job and see the main log (since you connected) among other things, all through the Internet or your local TCP/IP network.
Limitations:
ï¿­ 40-days trial