PaperCut MF Ports

[administrator]

The main network TCP ports used by PaperCut are:

• 9191 for HTTP connections
• 9192 for secure HTTP/SSL connection
• 9193 for device RPC (only used for embedded copier/MFP solutions)

Google Cloud Directory
PaperCut NG and PaperCut MF will use Secure LDAP to communicate with the Google Cloud Directory service:

• 636 TCP (LDAPS), with outbound connections to:
  ldap.google.com

Note: make sure any firewall rules allow “any” as source port for the PaperCut server in this case. The source/client port is dynamically allocated, and not meaningful.


Directory Services
PaperCut NF and PaperCut MF can synchronise user accounts from a directory using LDAP

• 389 TCP (LDAP) or 636 TCP (LDAPS)

Mobility Print - Cloud Print (for server registration & peer-to-peer traffic
To register the server and notify it of incoming jobs

• 443 TCP to mp.cloud.papercut.com
• 8883 TCP to mqtt.googleapis.com

To orchestrate the peer-to-peer connection

• 3478 TCP & UDP to global.stun.twilio.com
• 443 TCP & 3478 UDP to global.turn.twilio.com

PaperCut MF Cloud Services (Integrated Scanning with Scan to Cloud and/or Cloud OCR)
For a PaperCut server to have content processed by PaperCut MF Cloud Services it must be able to form an outgoing connection to the following endpoints:

443 TCP (HTTPS), with connection to:

• https://*.papercut.com/*
• https://storage.googleapis.com/*

the following specific URLs are used, depending on your PaperCut version and PaperCut MF Cloud Services hosting region, in case you are unable to use a wildcard in the domain part:

443 TCP (HTTPS), with connection to:

• https://scan.cloud.papercut.com/*
• https://ocr.cloud.papercut.com/*
• https://scan.au.cloud.papercut.com/*
• https://ocr.au.cloud.papercut.com/*
• https://scan.eu.cloud.papercut.com/*
• https://ocr.eu.cloud.papercut.com/*
• https://scan.us.cloud.papercut.com/*
• https://ocr.us.cloud.papercut.com/*
• https://scan.papercut.com/* (legacy)

Integrated Scanning - Self-Hosted Document Processing (FKA On-prem OCR, locally hosted)

• 9181 TCP (HTTPS) inbound on the Self-Hosted Document Processing Server

Sign in with Google
To allow signing in with Google to the PaperCut web interfaces, the Application Server must be able to form an outgoing connection to the following endpoints:

443 TCP (HTTPS), with connection to:

• https://accounts.google.com/*
• https://oauth2.googleapis.com/*

Multi Function Devices
PaperCut MF uses a variety of port for connecting to copiers, MFPs and other devices. These are listed below by device.

Canon
Inbound (device connecting to PaperCut)

• 9191
• 9192
• 9193

HP
Inbound

• 9191
• 9192
• 9193

Outbound connections from PaperCut to the HP devices on port:

• 7627 (TCP/HTTPS)
• 80 / 443

Konica-Minolta
Inbound (device connecting to PaperCut)

• 9191
• 9192
• 9195 (Required for SHA2 on MF v18.3 onwards)

Outbound (connecting to the device)

• 50003
• 80/443

Kyocera
Inbound

• 9191
• 9192
• 9193

Ricoh SDK/J and Ricoh SmartSDK
Inbound

• 9191 (if configured to use port 9193 and Integrated Scanning)
• 9192
• 9193
• 51443 (for setup with Remote Operation Client)

Samsung
Inbound

• 9191 (if using custom logos)
• 9192
• 9193

Toshiba
Inbound

• 9191 TCP - for EWB and SOAP events
• 9192 TCP - secure messages for EWB and SOAP events
• 10389 TCP (LDAP) for SDK1 and SDK2 only
• 10636 TCP (LDAPS) for SDK1 and SDK2 only
• 162 UDP (SNMP traps) for SDK1 only

Outbound

• 161 UDP (SNMP) for SDK1 only
• 49629 TCP (HTTP) for SDK2, SDK3 and RD30 only
• 49630 TCP (HTTPS) for SDK2, SDK3 and RD30 only
• 50083 TCP (HTTP) for SDK3 only (for scanning)

Xerox
Inbound

• 9191
• 9192

Outbound

• 80
• 443