Network ports

Secure communication

All Printix communication inside and outside the network is secured with encryption and the use of HTTPS (SSL/TLS). Documents are stored encrypted until they expire or get deleted. Documents do not need to leave your network.

• HTTPS on TCP port 443

  Secure browser communication between the components and identity providers, such as Microsoft Entra ID, Google Workspace, Okta, and OneLogin.

These ports must be open within the network:

• SNMP on UDP port 161

  Access and collect information from printers through SNMP. Both SNMPv1 and SNMPv3 are supported. ICMP message requests and replies must be allowed on the local network, because the ping command is used to discover printers.

• RAW print on TCP port 9100

  Transfer print data to the printers. Computers with Printix Client must be able to reach the printer on the network to allow printing. Print data can also be sent through:

  • IPPS and TCP port 443, 631. Use of other port numbers is also supported.

  • IPP and TCP port 80, 631. Use of other port numbers is also supported.

  • LPR and TCP port 515. Use of other port numbers is also supported.

• TCP port 21335

  Forward print data to another computer running Printix Client. Encrypted. It is only used if a computer is used for bridging two known networks.

• TCP port 21336

  Secure communication to Printix Redirector on a Windows Server.

• UDP port 21337

  Printix Discovery Protocol is used to find computers running Printix Client. Not encrypted.

• UDP port 5353

  If mobile print is enabled, and is to be used with iOS/iPadOS phones and tablets, then Printix Client will broadcast AirPrint printers with the Bonjour networking protocol (Multicast DNS).

The Printix Client requires these ports to be open on the local computer:

• TCP port 21338

  Secure communication locally on the computer between the PrintixClient.exe and PrintixService.exe processes.

• TCP port 21339

  Local communication with HTTP to allow the PrintixService.exe to listen for print data from the Windows Print Spooler (spoolsv.exe) and Mac CUPS (org.cups.cupsd).

• TCP port 21343

  Local Secure communication with HTTPS to allow the PrintixService.exe to listen for print data from the Windows Print Spooler (spoolsv.exe). Enabled with Printix Windows Registry setting DisableHTTPPrinting.

If Printix Go is in use, these ports must also be open within the network:

• HTTP port 8091

  Printix Client using HTTP to the Fujifilm printer to check the presence of the plug-in.

• HTTPS port 58501

  Printix Client using HTTPS to manage the plug-in configuration settings on Fujifilm printers.

• TCP port 7627

  SOAP communication from Printix Client to Printix Go on HP printers.

• TCP port 21343

  Secure communication through HTTPS from Printix Go printers with Capture to the Printix Client. Applies to HP and Konica Minolta printers. Does not apply to Ricoh printers.

• TCP port 50003

  SOAP communication from Printix Client to Printix Go on Konica Minolta printers.

• TCP port 51443

  Secure communication through HTTPS from Printix Client for Windows to Printix Go on Ricoh printers. The communication happens during the installation, update, and uninstallation of Printix Go and is performed by the Printix Go Ricoh Installer (silently invoked by the Printix Client).

If Active Directory authentication is enabled, one of these ports must also be open within the network:

• Secure LDAPS on TCP 636

  Authentication of users with secure LDAPS.

• LDAP on TCP port 389

  Authentication of users with LDAP.

On Windows, the Printix Client automatically configures the required ports in the local Windows firewall. It does so by running the provided open_firewall.cmd file.