“Help! I’m a PaperCut administrator and our school uses Lightspeed. Is there anything we need to configure to ensure our devices can successfully print with PaperCut Mobility Print?"
Some customers have reported issues when using PaperCut Mobility Print alongside Lightspeed solutions. Specifically, two components of Lightspeed — the Web Filter and Mobile Device Management (MDM) features — can interfere with Mobility Print’s communication. Below, we cover how these issues can affect the functionality of Mobility Print and the solutions customers have successfully implemented.
Web Content Filter blocks printer discovery Printer discovery fails when using the DNS discovery method when the Web Filter is active in Lightspeed. A common error observed is that the Lightspeed Relay Web Filter blocks the URL for discovering printers, rpc.pc-printer-discovery*.
Customers have been able to resolve this by either creating a policy to allow traffic on this URL or by adding the pattern rpc.pc-printer-discovery* to the exclusion list.
To do so, consult with Lightspeed support to add the following lines to the .pac (proxy auto-config) file used by the filter:
if (shExpMatch(url, "*cloudprint*")) { return proxy_no; } if (shExpMatch(url, "*pc-printer-discovery*")) { return proxy_no; } This ensures that the relevant printer discovery URLs are not blocked by the web filter.
Connection security error on iOS On iOS devices that are managed by Lightspeed MDM, users may encounter the error message: “The security of the connection could not be verified” when attempting to select a Mobility queue. This issue arises due to restrictions in Lightspeed’s Mobile Device Management (MDM) may be preventing the use of self-signed certificates in certain case.
By default, the Mobility Print server uses a self-signed certificate to encrypt communication.
To resolve this, we recommend follow these steps to set up Mobility Print with an SSL/TLS certificate .
You can also follow these instructions from Lightspeed to remove the MDM restrictions on an affected iOS device to confirm whether the certificate is indeed the issue.
Comments
0 comments
Please sign in to leave a comment.