Send Out Ptcp Stuff Again Charge Chrome Book and Ipad
Mobility Print system requirements
Server Requirements
| Hardware Requirements | |–|–| | CPU | Any x86-64 Processor (Intel or AMD)** | | Memory | 2GB or more | | Hard Drive | 3GB of free space or more |
| OS Requirements | |–|–| | Windows | Windows 8, 10, 11 / Server 2012, 2012 R2, 2016, 2019, 2022 | | Mac | macOS 10.14+ (Mojave) | | Linux |
- RHEL 6.0+
- SuSE 12.0+
- Debian 9.0+
- Ubuntu 14.0.4 LTS+
- Most Distros built on the previously mentioned versions
- Any distro that supports GNU glibc 2.11+ {{}} |
Additional Considerations
** Emulation has been reported to work on new Mac computers using the m1 Processor, but this has not been officially tested or developed for. Other devices that support ARM architecture, such as the Raspberry Pi, are not supported.
- Windows 'Desktop' class systems such as Windows 8, 10 and 11, 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.
- 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 12.0+
- macOS X 10.14+ (Mojave) 64-bit
- Windows 8.1+
- Android 6.0+
- Chrome OS with Chrome version 69+
*Please note that M1 Macs/ARM64 is not supported at the current time
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.
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 protocol | Server port (for printer discovery) | Job delivery protocol | Server port (for job delivery) |
---|---|---|---|---|---|
macOS | No | mDNS | Inbound: 5353 UDP Outbound: 5353 UDP | IPPS/HTTPS | 9164 TCP |
iOS | No | mDNS | Inbound: 5353 UDP Outbound: 5353 UDP | IPPS/HTTPS | 9164 TCP |
Android | Mobility Print App | mDNS HTTPS | Inbound: 5353 UDP Inbound: 9164 TCP Outbound: 5353 UDP | HTTPS | 9164 TCP |
Chrome | Mobility Print App | mDNS HTTP | Inbound: 5353 UDP Inbound: 9163 TCP Outbound: 5353 UDP | HTTP API (encrypted payload) | 9163 TCP |
Windows | Installer | mDNS HTTPS | Inbound: 5353 UDP Inbound: 9164 TCP Outbound: 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 protocol | Server port (for printer discovery) | Job delivery protocol | Server port (for job delivery) |
---|---|---|---|---|---|
macOS | Mobility Print App | HTTPS | Inbound: 9164 TCP Outbound: n/a | IPPS/HTTPS | 9164 TCP |
iOS | Configuration profile | HTTPS | Inbound: 9164 TCP Outbound: n/a | IPPS/HTTPS | 9164 TCP |
Android | Mobility Print App | HTTPS | Inbound: 9164 TCP Outbound: n/a | HTTPS API | 9164 TCP |
Chrome | Mobility Print App | HTTP | Inbound: 9163 TCP Outbound: n/a | HTTP API (encrypted payload) | 9163 TCP |
Windows | Installer | HTTPS | Inbound: 9164 TCP Outbound: n/a | IPP/HTTP | 9163 TCP |
Using DNS
Client | Client software? | Printer discovery protocol | Server port (for printer discovery) | Job delivery protocol | Server port (for job delivery) |
---|---|---|---|---|---|
macOS | No | DNS | Inbound: 53 UDP Inbound: 53 TCP Outbound: 53 UDP Outbound: 53 TCP | IPPS/HTTPS | 9164 TCP |
iOS | No | DNS | Inbound: 53 UDP Inbound: 53 TCP Outbound: 53 UDP Outbound: 53 TCP | IPPS/HTTPS | 9164 TCP |
Android | Mobility Print App | DNS HTTPS | Inbound: 53 UDP Inbound: 9164 TCP Outbound: 53 UDP | HTTPS API | 9164 TCP |
Chrome | Mobility Print App | DNS HTTPS | Inbound: 53 UDP Inbound: 9163 TCP Outbound: 53 UDP | HTTP API (encrypted payload) | 9163 TCP |
Windows | Installer | DNS HTTPS | Inbound: 53 UDP Inbound: 9164 TCP Outbound: 53 UDP | IPP/HTTP | 9163 TCP |
Cloud Print
Local (same host)
Client user context service | internal/localhost connection only |
---|---|
port 9165 TCP | localhost (127.0.0.1) |
Inbound
No firewall rules.
Outbound
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 |
Source: https://www.papercut.com/help/manuals/mobility-print/set-up/system-requirements/
0 Response to "Send Out Ptcp Stuff Again Charge Chrome Book and Ipad"
Post a Comment