Mobility Print system requirements
PaperCut NG/MF integration
Mobility Print integrates with PaperCut NG/MF versions 17.0.3 or greater.
The Cloud Print feature integrates with PaperCut NG/MF versions 17.0.3 or greater.
Server requirements
Do not install Mobility Print on a DNS server or Domain Controller.
Operating System
-
Windows Server 2019 / 2016 / 2012 / 2012 R2 / Windows 10* / Windows 8*
Note: Core, server, advanced server, enterprise edition, 64-bit edition, workstation, professional versions all supported.
All Windows 10 and Windows Server Operating Systems run PaperCut Software products as either x86, x32 or x64 applications on Intel or AMD CPU architectures. PaperCut Software products cannot currently run as ARM32 and ARM64 UWP applications on ARM Processors.
-
Mac OS X 10.12+ (for example, Sierra, High Sierra, Mohave)
-
Most modern Linux operating systems including:
-
Red Hat Enterprise Linux (6.0+)
-
CentOS (6.0+)
-
SuSE Linux (11.0+)
-
Ubuntu (10.04+)
-
Debian (6.0+)
-
Others supporting GNU glibc 2.11 or higher.
-
The 'desktop' class systems such as Windows 7, 8, and 10, allow only 10 simultaneous connections. This means that these systems should be used as a 'server' to host print queues only on networks where you expect less than 10 simultaneous print jobs to be processed.
Memory
-
2 GB or higher recommended.
Hard Disk
-
At least 3 GB of free space is recommended.
Internet connection is required to automatically update the software when new versions are available. For more information, see the How do I update my Mobility Print server? section in the FAQs.
Printer requirements
Mobility Print works with the vast majority of printers. The key requirement is that the printer has a print driver for the server host operating system (for example, a Windows Driver).
Mobility Print supports all printers that have drivers for modern Windows operating systems except label printers and plotters. This is because the drivers for label printers and plotters use non-standard page sizes. If you find any exceptions, or have problems, please let us know.
Client requirements
The client must have IPP enabled.
-
iOS 11.0+
-
macOS X 10.12+ (Sierra) 64-bit
-
Windows 7+
-
Android 4.4+
-
Chrome OS with Chrome version 69+
Firewall rules
Which protocols and ports to set up depends on the printer discovery method you are going to use.
Auto update
The following port and URL endpoints must be externally available for auto updating:
-
443 TCP (HTTPS), with connections to:
-
https://mobility-print.papercut.com/*
-
https://mobility-print-standalone.papercut.com/*
-
https://storage.googleapis.com/pc-mobility-print.appspot.com/*
-
Using mDNS
Client | Client Software? | Printer discovery | Print job delivery | |||
---|---|---|---|---|---|---|
Discovery Protocols | Mobility Print Server port | Delivery Protocols | Mobility Print Server Port | |||
Inbound | Outbound | |||||
macOS | No |
mDNS |
5353 UDP | 5353 UDP | IPPS/HTTPS | 9164 TCP |
iOS | No |
mDNS |
5353 UDP | 5353 UDP | IPPS/HTTPS | 9164 TCP |
Android | Mobility Print App |
mDNS |
5353 UDP |
5353 UDP | HTTPS | 9164 TCP |
Chrome | Mobility Print App |
mDNS |
5353 UDP 9163 TCP |
5353 UDP | HTTP API (encrypted payload) |
9163 TCP |
Windows | Installer |
mDN |
5353 UDP 9164 TCP |
5353 UDP | IPP/HTTP | 9163 TCP |
Using a known host
When setting up Mobility Print with a known host, the following port and URL endpoints must be externally available to be able to retrieve the client setup files:
-
443 TCP (HTTPS), with connections to:
-
https://www.papercut.com/api/product/mobility-print/latest/client/windows
-
https://www.papercut.com/api/product/mobility-print/latest/client/macos
-
https://www.papercut.com/api/product/mobility-print/latest/client/android
-
https://ios-profile-signing-dot-pc-mobility-print.appspot.com/sign-profile/v1
-
Client | Client Software? | Printer discovery | Print job delivery | |||
---|---|---|---|---|---|---|
Discovery Protocols | Mobility Print Server port | Delivery Protocols | Mobility Print Server Port | |||
Inbound | Outbound | |||||
macOS | Mobility Print App |
HTTPS |
9164 TCP | n/a | IPPS/HTTPS | 9164 TCP |
iOS | Configuration profile |
HTTPS
|
9164 TCP | n/a | IPPS/HTTPS | 9164 TCP |
Android | Mobility Print App |
HTTPS
|
9164 TCP |
n/a | HTTPS API | 9164 TCP |
Chrome | Mobility Print App |
HTTP |
9163 TCP | n/a | HTTP API (encrypted payload) | 9163 TCP |
Windows | Installer |
HTTPS |
9164 TCP | n/a | IPP/HTTP | 9163 TCP |
Using DNS
Client | Client Software? | Printer discovery | Print job delivery | |||
---|---|---|---|---|---|---|
Discovery Protocols | Mobility Print Server port | Delivery Protocols | Mobility Print Server Port | |||
Inbound | Outbound | |||||
macOS | No |
DNS
|
53 UDP 53 TCP |
53 UDP 53 TCP |
IPPS/HTTPS | 9164 TCP |
iOS | No |
DNS |
53 UDP 53 TCP |
53 UDP 53 TCP |
IPPS/HTTPS | 9164 TCP |
Android | Mobility Print App |
DNS |
53 UDP 9164 TCP |
53 UDP | HTTPS API | 9164 TCP |
Chrome | Mobility Print App |
DNS |
53 UDP 9163 TCP |
53 UDP | HTTP API (encrypted payload) | 9163 TCP |
Windows | Installer |
DNS |
53 UDP 9164 TCP |
53 UDP | IPP/HTTP | 9163 TCP |
Cloud Print
Inbound
No firewall rules.
Outbound
If your Mobility Print server relies on a proxy server for its outbound internet connection, then Cloud Print will not work for you.
To register the server and notify it of incoming jobs | |
---|---|
port 443 TCP | mp.cloud.papercut.com |
port 8883 TCP | mqtt.googleapis.com (notification service) |
To orchestrate the peer-to-peer connection |
|
---|---|
port 3478 TCP port 3478 UDP |
global.stun.twilio.com |
port 443 TCP port 3478 UDP |
global.turn.twilio.com |