Choose your language

Choose your login

Support

How can we help?

Lightbulb icon
Lightbulb icon

Here’s your answer

Sources:

Lightbulb icon

Oops!

We currently don’t have an answer for this and our teams are working on resolving the issue. If you still need help,
User reading a resource

Popular resources

Conversation bubbles

Contact us

Configure a Linux or Novell iPrint secondary print server

This page applies to:

This section describes the process of setting up a secondary print server on a Linux system. The primary server (Application Server) can either be a Windows, Mac, Novell, or a Linux-based system. PaperCut NG/MF has full support for “mixed” or heterogeneous printing environments.

Step 1: Ensure the primary server is set up correctly

Before installing a secondary server, you should ensure the Application Server is set up and running correctly. Verify that the Application Server is functioning correctly. For example, verify that:

  • printers on this server are being tracked

  • users can log in to user pages from their workstations

  • administrators can access the system.

Step 2: Ensure firewall software is set to allow access to port 9191, 9192, 9195

The secondary server needs to communicate (initiate a TCP connection) on port 9191 (HTTP) or 9192/9195(HTTPS). Make sure any firewall software on the Application Server is not set to block any incoming local network traffic on this port. A good way to test is to open a browser on the planned secondary server, then check you can access the administration web interface on port 9191.

Step 3: Check that the host account exists

On the secondary server, create a user account called papercut. Set the papercut user’s home directory to the desired install location. This is normally /home/papercut. The method of creating this account is the same as that used for the primary server setup. For more information, see Installation .

Step 4: Install the Print Provider

Install the Print Provider software onto the secondary server by copying all files and directories from the primary Application Server’s directory:

[app_path]/providers/print/linux-x64/* (64-bit)

To the equivalent location on the secondary server:

/home/papercut/providers/print/linux-x64/ (64-bit)

on the secondary server. Perform the copy operation as the papercut user so that files are owned by the papercut user. You can use any method to copy the files, including over the network or via a USB key. If the primary server is also Linux, the simplest way would be use Secure Copy (scp) as follows:

shell> su - papercut
shell> mkdir -p providers/print
shell> cd providers/print
shell> scp -r primary.server.name:/home/papercut/providers/print/* .

After the copy operation is performed, execute the setperms and roottasks scripts as root:

64-bit

shell> su - root
shell> sh ~papercut/providers/print/linux-x64/setperms
shell> sh ~papercut/providers/print/linux-x64/roottasks

Step 5: Configuration

The Print Provider on the secondary server needs to know where the primary server is installed (that is, its IP address).

  1. Open the following file in a text editor:

    /home/papercut/providers/print/linux-x64/print-provider.conf (64bit)
    
  2. Locate the line starting with ApplicationServer= and change localhost to the name or IP address of the primary server.

You now need to integrate the binaries copied in step 4 into the CUPS, Samba, or Novell iPrint print queues.

This process is detailed in Linux print queue integration and Step 5 - Printer/iPrint configuration .

Step 6: Test

The secondary server should now be configured. Perform some test printing on all of this secondary server’s printers. Log in to the system as “admin” and verify that the printers are now listed on the Printers List page. Perform a multi-page test print on each printer and verify that print jobs are tracked correctly.

Comments