skip to primary navigationskip to content
 

Network requirements

This page provides information to enable an institution to permit Managed Print Service (DS-Print) network traffic across the institution’s local network.
  • Cambridge University Data Network, since April 2015 DS-Print traffic between institutions and CUDN is enabled by default
  • Managed Cluster Service, DS-Print traffic is permitted on institutions' MCS VLAN
  • Wireless, DS-Print is enabled across eduroam and UniOfCam. No further configuration is required by the institution unless the wireless access is managed by the institution, in which case it will be required to ensure DS-Print traffic is permitted.

The following information details protocols and ports required to permit traffic enabling DS-Print service to function on the institution’s local network.

Please note, while institutional use of a NAT (Network Address Translation) environment is permitted by UIS subject to conditions, only hosts emitting network traffic onto the Cambridge University Data Network (CUDN), i.e. outside the institutional LAN, using unique IP address assigned and maintained by IP-register are supported by DS-Print.

UIS Firewalls and Network Address Translation Technical guide

DS-Print Network Traffic Flows v1_4

Ports shown in 'network traffic flows' diagram are used as follows

Protocol/port(s) Functional protocol Purpose
UDP/161 SNMP Monitoring of printer
TCP/9100 RAW Raw printing data
TCP/9191+9192 PaperCut PaperCut administration/communication
TCP/445 SMB

Microsoft printing used by Windows clients, also used by Mac OS X and Linux; also used for Windows driver download

 

Traffic - Institution to UIS
Destination hosts and ports used for communication from institutional network to Desktop Services server network

Host(s) Protocols/ports
172.16.3.64 TCP/9191+9192

131.111.3.3
131.111.3.4
131.111.3.247

TCP/445

 

Traffic - UIS to Institution
Destination hosts and ports used for communication from Desktop Services server network to institutional network

Host(s) Protocols/ports
172.16.3.64 UDP/161

131.111.3.3
131.111.3.4
131.111.3.247

TCP/9100 + UDP/161

 

Additional Konica Minolta MFD network configuration

Traffic - UIS to Institution
PaperCut MF uses a variety of ports for connecting to MFDs

Protocol/port(s) Functional protocol Purpose
TCP/50003 PaperCut PaperCut administration/communication with Konica OpenAPI using SSL
TCP/80 HTTP Access device web interface
TCP/443 HTTPS Access device web interface

 

Additional Sharp MFD network configuration

Traffic - UIS to Institution
PaperCut MF uses a variety of ports for connecting to MFDs

Protocol/port(s) Functional protocol Purpose
TCP/80 HTTP Access device web interface

 

Additional Kyocera MFD network configuration

Traffic - UIS to Institution
PaperCut MF uses a variety of ports for connecting to MFDs

Protocol/port(s) Functional protocol Purpose
TCP/9193 PaperCut PaperCut administration/communication

 

Optional network configuration

Optionally, institutions can permit traffic from the UIS public staff subnet, and traffic from the Desktop Services core network. The purpose is to enable members of DS-Print team to access institutional printers for support and investigative tasks.

Protocol/port(s) Functional protocol Purpose
UDP/161 SNMP Monitoring of printer
TCP/9100 RAW Raw printing data
TCP/9191+9192 PaperCut PaperCut administration/communication
TCP/9193 PaperCut PaperCut administration/communication with Kyocera
TCP/50003 PaperCut PaperCut administration/communication with Konica OpenAPI using SSL
TCP/445 SMB Microsoft printing used by Windows clients, also used by Mac OS X and Linux; also used for Windows driver download
TCP/80 HTTP Access device web interface
TCP/443 HTTPS Access device web interface

 

Traffic - UIS to Institution
Destination hosts and ports used for communication from Information Services public staff subnet to institutional network

Host(s) Protocols/ports

131.111.56.0/23
172.16.3.64
131.111.3.3
131.111.3.4
131.111.3.247

All listed in above table