When populating printers from the PaperCut Print Provider, printers will be prefixed with the machine name, even if the printers are on the same system as the Application Server. In this list the printer names will appear as
A PaperCut administrator has recently submitted an issue where printers were suddenly re-added to the Printers list with
localhost as the server name, meaning they had both a
server-name\printer1 and a
localhost\printer1 in this list. This can cause issues when running reports, as the printer will now report jobs on the localhost printer.
The administrator found that an SSL certificate on their print server had recently expired, and the only visible effect witnessed was the server reporting as localhost as the hostname. Once the certificate was renewed, the server started reporting the correct hostname.
If you find that you have never used an SSL certificate on your print server, please get in touch with the support team over at http://support.papercut.com
One of the team will then help you our further.
To set the Application server hostname to the Print Provider instead of
localhost, you can use the below key in the ‘print-provider.conf’ file for the Print Provider.
# # Define the name or IP address of the application server. # On secondary server installs, this value should be changed to point to the # primary application server. # Default: 127.0.0.1 # Examples: mainserver.localdomain.com, win2003, 220.127.116.11 # # IMPORTANT: Please restart the server or the "Print Provider Service" after # changing this value. # ApplicationServer=127.0.0.1
However, the Print Provider uses this above key to determine the App server address used for an XML-RPC connection.
The Print Provider gets the full path of a queue name, i.e. the queue name of the ‘server\printer’ style, from Windows API and register it to the App Server. Thus, it really depends on Server or Windows implementation that how to handle localhost\printer and server-name\printer when localhost and server-name are the same machine.