How to Use Proxy Queues to Release Jobs from a Virtual Queue in Papercut

Question:

How can we enable job release from a virtual queue on a different site server in Papercut? >
> We have a Papercut infrastructure with multiple site servers and one application server. We have local queues on site server 3 that need to release jobs from a virtual queue on site server 1. The devices and the virtual queue are configured correctly in Papercut, but the jobs in the virtual queue are not visible on the devices when we log in. We think there might be a port issue between the site servers. What are the possible solutions?

Answer:

How to enable job release from a virtual queue on a different site server in Papercut

Papercut is a print management software that allows you to control and monitor your printing environment. One of the features of Papercut is the ability to use virtual queues, which are queues that do not have a physical printer associated with them. Instead, they act as a holding area for print jobs, which can then be released to any device that is configured to accept jobs from the virtual queue.

This can be useful for scenarios where you want to offer users a choice of printers, or where you want to reduce the number of print queues on your network. However, there are some challenges when using virtual queues across multiple site servers, which are servers that act as local print servers for remote locations.

In this article, we will explain how to enable job release from a virtual queue on a different site server in Papercut, and what are the possible solutions if you encounter any issues.

Let’s say you have a Papercut infrastructure with multiple site servers and one application server. The application server is the central server that runs the Papercut application and database, and the site servers are the servers that handle the printing traffic for each site.

You have local queues on site server 3 that need to release jobs from a virtual queue on site server 1. The devices and the virtual queue are configured correctly in Papercut, but the jobs in the virtual queue are not visible on the devices when you log in. You think there might be a port issue between the site servers.

The solution

There are two possible solutions to this problem:

  • Solution 1: Open the required ports between the site servers. Papercut uses a range of ports to communicate between the application server and the site servers, and between the site servers themselves. These ports need to be open on the firewall for the communication to work properly. The ports are:
  • TCP 9191: This is the main port used by the Papercut application server and the site servers to communicate with each other. It is also used by the devices to communicate with the site servers.
  • TCP 9192: This is the port used by the Papercut application server and the site servers to replicate the database changes. It is also used by the devices to communicate with the application server.
  • TCP 9193: This is the port used by the Papercut application server and the site servers to transfer the print job data. It is also used by the devices to download the print jobs from the virtual queue.
  • You need to make sure that these ports are open between site server 1 and site server 3, and between site server 3 and the application server. You can use a tool like telnet or netcat to test the connectivity between the servers on these ports. If you open these ports, the jobs in the virtual queue should be visible on the devices, and you should be able to release them.

  • Solution 2: Use a proxy queue instead of a virtual queue. A proxy queue is a type of queue that acts as a proxy for another queue. It allows you to redirect print jobs from one queue to another queue, without changing the original queue settings. This can be useful for scenarios where you want to use a virtual queue, but you have network or firewall restrictions that prevent the communication between the site servers.
  • To use a proxy queue, you need to create a local queue on site server 3 that has the same name as the virtual queue on site server 1. Then, you need to configure the proxy queue settings in Papercut, by going to Printers > [proxy queue name] > Proxy Queue Settings. You need to enable the proxy queue option, and select the virtual queue on site server 1 as the target queue. You also need to enable the option to copy the job attributes from the target queue, such as the color mode, duplex mode, and page size. If you use a proxy queue, the jobs in the virtual queue will be redirected to the proxy queue on site server 3, and they will be visible on the devices. You will be able to release them as normal.

    Conclusion

    In

this article, we have explained how to enable job release from a virtual queue on a different site server in Papercut, and what are the possible solutions if you encounter any issues. We hope this article was helpful and informative. If you have any questions or feedback, please feel free to contact us. Thank you for using Copilot. 😊

Leave a Reply

Your email address will not be published. Required fields are marked *

Privacy Terms Contacts About Us