Choose your language

Choose your login

Contact us

Mobility Print System Requirements

This page applies to:

Server Requirements

Hardware Requirements

CPU: Any 64-bit Processor (Intel or AMD)**

Memory: 2GB or more, based on printing volume.

Hard Drive: 3GB of free space or more, based on printing volume.

OS Requirements

Windows: Windows 10, 11, Server 2016, 2019, 2022

Mac: macOS 11+ (Big Sur)

Linux:

  • RHEL 6.0+.
  • SuSE 12.0+.
  • Debian 10.0+.
  • Ubuntu 14.0.4 LTS+.
  • Most distributions built on the previously mentioned versions.
  • Distribution need to support GNU glibc 2.11+ and kernel version 2.6.32 or later, adhering to vendor supported distributions is recommended and will achieve the requirements.

Additional Considerations

  • There are no known issues with Mac devices using the M series (e.g. M1 / M2) processors, but this has not been officially tested or developed for. Emulation (Rosetta) will be used since the app is not written for Apple Silicon. Please see Known Issues when upgrading macOS and iOS for more information.
  • Devices that support ARM architecture, such as the Raspberry Pi, are not currently supported.
  • Windows Desktop class systems such as Windows 10/11, allow only 20 simultaneous connections. This means that these systems should only be used as a “server” to host print queue on networks where you expect less than 20 simultaneous print jobs to be processed.
  • An 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

  • iOS 15.0+
  • macOS 11+ (Big Sur) (64-bit)
  • Windows 10+
  • Android 10.0+
  • ChromeOS with Chrome version 69+

Additional Considerations

  • There are no known issues with Mac devices using the M series (e.g. M1 / M2) processors, but this has not been officially tested or developed for. Emulation (Rosetta) will be used since the app is not written for Apple Silicon. See Known Issues when upgrading macOS and iOS for more information.
  • Other devices that support ARM architecture, such as the Raspberry Pi, are not currently supported.
  • Administrator level permissions are required in order to install and use the Mobility Print Cloud client .

PaperCut NG/MF integration

Mobility Print integrates with PaperCut NG/MF versions 17.0.3 or greater.

The Mobility Print Cloud Print feature integrates with PaperCut NG/MF versions 17.0.3 or greater.

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

ClientClient software?Printer discovery protocolServer port (for printer discovery)Job delivery protocolServer port (for job delivery)
macOSNomDNSInbound: 5353 UDP
Outbound: 5353 UDP
IPPS/HTTPS9164 TCP
iOSNomDNSInbound: 5353 UDP
Outbound: 5353 UDP
IPPS/HTTPS9164 TCP
AndroidMobility Print extensionmDNS
HTTPS
Inbound: 5353 UDP
Inbound: 9164 TCP
Outbound: 5353 UDP
HTTPS9164 TCP
ChromeMobility Print extensionmDNS
HTTP
Inbound: 5353 UDP
Inbound: 9163 TCP
Outbound: 5353 UDP
HTTP API (encrypted payload)9163 TCP
WindowsInstallermDNS
HTTPS
Inbound: 5353 UDP
Inbound: 9164 TCP
Outbound: 5353 UDP
IPP/HTTP9163 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
ClientClient software?Printer discovery protocolServer port (for printer discovery)Job delivery protocolServer port (for job delivery)
macOSMobility Print AppHTTPSInbound: 9164 TCP
Outbound: n/a
IPPS/HTTPS9164 TCP
iOSConfiguration profileHTTPSInbound: 9164 TCP
Outbound: n/a
IPPS/HTTPS9164 TCP
AndroidMobility Print AppHTTPSInbound: 9164 TCP
Outbound: n/a
HTTPS API9164 TCP
ChromeMobility Print AppHTTPInbound: 9163 TCP
Outbound: n/a
HTTP API (encrypted payload)9163 TCP
WindowsInstallerHTTPSInbound: 9164 TCP
Outbound: n/a
IPP/HTTP9163 TCP

Using DNS

ClientClient software?Printer discovery protocolServer port (for printer discovery)Job delivery protocolServer port (for job delivery)
macOSNoDNSInbound: 53 UDP
Inbound: 53 TCP
Outbound: 53 UDP
Outbound: 53 TCP
IPPS/HTTPS9164 TCP
iOSNoDNSInbound: 53 UDP
Inbound: 53 TCP
Outbound: 53 UDP
Outbound: 53 TCP
IPPS/HTTPS9164 TCP
AndroidMobility Print AppDNS
HTTPS
Inbound: 53 UDP
Inbound: 9164 TCP
Outbound: 53 UDP
HTTPS API9164 TCP
ChromeMobility Print AppDNS
HTTPS
Inbound: 53 UDP
Inbound: 9163 TCP
Outbound: 53 UDP
HTTP API (encrypted payload)9163 TCP
WindowsInstallerDNS
HTTPS
Inbound: 53 UDP
Inbound: 9164 TCP
Outbound: 53 UDP
IPP/HTTP9163 TCP

Cloud Print

Local (same host)

Client user context serviceinternal/localhost connection only
port 9165 TCPlocalhost (127.0.0.1)

Inbound

No firewall rules.

Outbound

To register the server and notify it of incoming jobs 
port 443 TCPmp.cloud.papercut.com
port 443 TCPCurrent: mqtt.notifications.cloud.papercut.com
(The notification service sends both HTTP & HTTPS through port 443)
Deprecated: mqtt.googleapis.com
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

Comments