This article is only applicable if you are running PaperCut NG/MF version or .
Starting from version , Print Provider sends host HTTP header by default when communicating with the PaperCut NG/MF Application Server.
Print Provider cannot communicate with the PaperCut NG/MF Application Server and Site Server when a content filter service is used
Some firewalls with a content filter service block communication between the PaperCut NG/MF Application Server (and Site Servers) and Print Providers.
Content filtering services require a specific HTTP header (Host: <host>:<port>).
<host> is the domain name of the server
<port> is the TCP port number that the server is listening to.
However, packets sent by the Print Provider to the (PaperCut NG/MF Application Server and Site Servers) do not contain that header. This means the content filtering service rejects the packets.
If this happens, your secondary servers and Direct Print Monitors will not work, and printers will not show up on the Printers tab in the PaperCut NG/MF Admin interface. If this happens, check the Print Provider log in the following location for errors:
A common error message indicating this problem is:
ERROR: error while waiting for socket data - A (Error: 10054)
Why don’t we just send this header by default?
This change was introduced in 18.1.3. To avoid changing HTTP traffic for thousands of sites with unique network configurations, we introduced it as an opt in change. In the future, this setting will be switched on by default.
Modify the Print Provider configuration as follows.
1. In a text editor, open the following configuration file:
2. Add the following key and value to the file:
3. Save the file.
4. Restart the PaperCut Print Provider service.
5. Open the Print Provider log:
6. Check for errors and confirm that the secondary server is monitoring the printers.