Main Communication Ports
If you need to adjust your firewall, it is recommended to allow MyQ processes in the firewall and not particular ports. If you allow particular ports, MyQ may stop working if:
you change port settings in MyQ, or
you upgrade to a newer version and the port specification has changed.
Terminal packages may use additional ports. Check the particular terminal package specification for details.
Printer Status
Make sure to create an exception that allows ICMP Echo Requests/Replies (Ping) through your Windows Firewall, as MyQ uses it by default to check the printers' status.
Incoming Ports
The server is listening on the following ports (does not include private ports):
Protocol | Port | Configurable | Description |
---|---|---|---|
TCP | 21 | Yes (WebUI) | FTP protocol for receiving scans(1). The server runs only in passive mode and each data connection runs over a dynamic port in the 49152 - 65535 range. |
TCP | 25 | Yes (WebUI) | SMTP over StartTLS(2) for Scan Management function, receiving email notifications from printers, and for receiving emails with jobs. |
TCP | 443 | Yes (Easy Config) | HTTPS protocol for:
Previously, this port was 8090 and it is preserved as such for upgraded installations. |
TCP | 515 | Yes (WebUI) | LPR protocol for print job transmission to the MyQ server. |
TCP | 587 | Yes (WebUI) | SMTPS protocol. Used in the same scenarios as SMTP. |
TCP | 9100 | Yes (WebUI) | RAW protocol(3) for print job transmission to the MyQ server. |
UDP | 11112 | No | Communication with MyQ Desktop Client (MDC) 10.0 and lower. The answer is returned on a dynamic port in the 49152 - 65535 range. Not required with MDC 10.2+. |
(1) FTP ports might not be required for newer embedded terminals (the majority of the latest 8.2+ terminals except for Epson) where scanning can be performed over HTTP. The dependency in certain situations is based on the particular device models within your organization. Since MyQ 10.2 Print Server, the FTP server can be also completely turned off in the Settings – Network section of the MyQ Web Admin Interface.
(2) Regarding the requirements for SMTP ports, the MyQ SMTP Server can be turned off in MyQ Print Server’s Settings – Network, and these incoming ports closed as well since MyQ 10.2. This is possible if you do not intend to use MyQ Print Server as an SMTP server in your MFDs to redirect email communication from the device for the Scan to Me feature on the device’s native panel.
(3) RAW ports are required only when queues using them exist. RAW reception for a queue is configured in Queues – queue’s detail – Job Receiving – Jobs via RAW protocol.
PM Server
Protocol | Port | Configurable | Description |
---|---|---|---|
TCP | 631 | No | Port for Mobile print via IPP. |
TCP | 717 | No | Port for Mobile print via IPPS. |
TCP | 9090, 9091 | No | Necessary for remote setup of Kyocera embedded terminals. |
TCP | 9092 | No | Felica reader |
TCP | 9093 | Yes (WebUI) | Authentication / Authorization. |
TCP | 9094 | No | Driver access, mobile access. |
TCP | 9095 | Yes (WebUI) | Spooler service. |
TCP | 9097 | Yes (WebUI) | Log information event. |
TCP | 9098 | Yes (WebUI) | Job status event. |
TCP | 9099 | Yes (WebUI) | Thrift access. |
TCP | 9101 | No | User session service. |
Outgoing Ports
The server is connecting to the following ports (does not include localhost connections):
Protocol | Port | Description |
---|---|---|
TCP | 443 | HTTPS port for:
|
TCP | 515 | LPR protocol for print job transmission from MyQ to printing devices. |
TCP | 631 | IPP protocol for print job transmission from MyQ to printing devices. |
TCP | 9100 | Raw protocol for print job transmission from MyQ to printing devices. |
TCP | 10040 | MPP/MPPS protocol for print job transmission from MyQ to printing devices. |
You can also setup additional services that require further configuration and their port will often differ:
Protocol | Port | Default | Description |
---|---|---|---|
TCP | Custom | 110 | Connection to email server via POP3 protocol for receiving jobs via email. |
TCP | Custom | 143/993 | Connection to email server via IMAP/IMAPS protocol for receiving jobs via email. |
TCP | Custom | 25/465/587 | Connection to SMTP server for sending outgoing emails from MyQ. |
TCP | Custom | 389/636/1812 | Connection to Authentication server(s) (LDAP, Radius, ...) for user authentication/synchronization. |
TCP | Custom | 8093 | Connection to MyQ Central Server. |
UDP | Custom | 161 | SNMP protocol for communication with printing devices. Answer from printer is returned on a dynamic port. |
TCP | Custom | - | Connection to External credit account. |
As for outgoing SMTP ports, port 587 is used for email transmission via Microsoft Exchange Online or Gmail (in Settings – Connections); in the case of the Classic SMTP Server method, the connection and port are configured in Settings – Network.
MyQ can connect to dynamic ports in the following contexts:
Protocol | Port | Description |
---|---|---|
UDP | Dynamic | Communication with MDC (Former SJM and SPS). The port range is 49152 - 65535. Not required with MDC 10.2+. |
Embedded Packages Ports
Kyocera | |
If SSL is on, it's used for the following events: | Events are notified internally to the embedded application. No network communication is used. |
MyQ Server (Protocol: Port - Description) |
|
Package (Protocol: Port - Description) |
Kyocera 8.0+ |
Printer (Protocol: Port - Description) |
Note: Other ports used by the printer (common for all printers. Eg. 9100 for RAW printing, etc.). |
Pay attention to the Incoming Ports section, specifically the PM Server since it is an essential component for configuring Kyocera devices remotely, communicating with Kyocera or Kyocera Lite embedded terminals, and providing Kyocera-specific features supported by the vendor’s print drivers.
HP | |
If SSL is on, it's used for the following events: | All types of events go through SSL. |
MyQ Server (Protocol: Port - Description) |
|
Package (Protocol: Port - Description) |
|
Printer (Protocol: Port - Description) |
|
Toshiba | |
If SSL is on, it's used for the following events: | All types of events go through SSL. |
MyQ Server (Protocol: Port - Description) |
|
Package (Protocol: Port - Description) |
|
Printer (Protocol: Port - Description) |
|
Xerox | |
If SSL is on, it's used for the following events: | Always SSL |
MyQ Server (Protocol: Port - Description) |
|
Package (Protocol: Port - Description) |
|
Printer (Protocol: Port - Description) |
|
Canon | |
If SSL is on, it's used for the following events: | Events are notified internally to the embedded application. No network communication is used. |
MyQ Server (Protocol: Port - Description) |
|
Package (Protocol: Port - Description) |
|
Printer (Protocol: Port - Description) |
Note: Other ports used by the printer (common for all printers. Eg 9100 for raw printing, etc.). |
Ricoh | |
If SSL is on, it's used for the following events: | Events are notified internally to the embedded application. No network communication is used. |
Printer (Protocol: Port - Description) |
Note: Other ports used by the printer (common for all printers. Eg 9100 for raw printing, etc.). |
Sharp | |
If SSL is on, it's used for the following events: | All types of events go through SSL. |
MyQ Server (Protocol: Port - Description) |
|
Package (Protocol: Port - Description) |
|
Printer (Protocol: Port - Description) | Any port from the <0-65535> range. Default:
|
Epson | |
If SSL is on, it's used for the following events: | All types of events go through SSL. |
MyQ Server (Protocol: Port - Description) |
|
Package (Protocol: Port - Description) |
|
Printer (Protocol: Port - Description) |
|
Pay attention to the Incoming Ports section, specifically the FTP server since only selected Epson devices support scanning over HTTPS, and that support is limited, thus using FTP might be required.
Some of the above mentioned ports can be changed in case of conflicts with other applications.
Conflicts of the communication ports with other software will be revealed by the Windows socket error 10048 error message.