The following are TCP and UDP destination port numbers (sometimes referred to as sockets) on the HP Jetdirect print servers.
Some users may need to print through a router or a firewall and may need to allow access to these destination ports on a Jetdirect through those devices.
Some of these ports (as well as protocols) can be disabled on certain HP Jetdirect print servers using the Jetdirect Embedded Web Server, Telnet, or HP Web Jetadmin software. This capability depends on the model of the Jetdirect as well as the firmware version of the print server.
For more information on enabling the ports of a Jetdirect, see the manuals for your specific print server (most are available on hp.com) - specifically the sections on using Telnet.
Click here to go to the Support and Drivers web page on hp.com
Note that there are many different print servers and, unfortunately, many of the older print servers never had electronic versions of their manuals to make available on the Web.
Jetdirect TCP and/or UDP ports
•20 and 21 TCP port for FTP. These ports can be use to FTP files directly to Jetdirect print servers. HP Jetdirect listens on TCP port 20 for FTP connection requests. Port 21 is the control port, which the Jetdirect will listen on for the initial connection. After the connection is established, in active mode FTP, a data connection will be made from port 20. Up to three simultaneous FTP sessions can be active at the same time.
•23 TCP port for Telnet. This port can be used for remote configuration of the HP Jetdirect device when there are no other configuration methods or it can be used to check the current configuration.
•25 SMTP port for E-mail. Newer HP Printers and Multi-Function Devices have the capability of sending e-mail alerts directly from the device.
•53 UDP and TCP ports for DNS. Allows MFP devices to resolve hostnames for use with Digital Sending functions.
•67 and 68 TCP ports for DHCPv4 and BOOTP (they use the same client and server ports). Port 67 is the BOOTP Server and port 68 is the BOOTP Client.
•69 TCP port for TFTP. This port is used for configuration and upgrading the Jetdirect firmware.
•80 TCP port for HTTP for EWS (Embedded Web Server). HP Jetdirect devices have an embedded Web page in the firmware which can be accessed through this port. The Embedded Web Server page allows a user to configure the HP Jetdirect using a supported browser.
•88 TCP and UDP for Kerberos. Used by HP LaserJet MFP devices for Kerberos authentication (if configured).
•161 UDP port SNMP. This port can be accessed by any SNMP Management utility. HP Jetadmin and HP Web Jetadmin use SNMP to configure and query the status of HP Jetdirect devices.
•162 UDP port for sending SNMP traps. This port can be used when the network is configured to capture trap information. Many SNMP Management utilities can be configured to capture traps. The Jetdirect's SNMP trap destination IP address and this port number can be configured using Web Jetadmin or Telnet.
•280 UDP/TCP port for HTTP Management. Used by embedded web service and IPP printing.
•389 TCP port for LDAP. Allows MFP devices to perform address lookups.
•427 UDP port for SLP (Service Location Protocol). Newer HP Jetdirect devices use the SLP (Service Location Protocol) packet type for advertising their services. Some HP software utilities use multicast and SLP to automatically discovery and automatically install a printer on the network.
•443 TCP port for SSL. When enabled, SSL/TLS provides confidentiality, data integrity, and authentication for the communication between a Web browser and the Jetdirect Web server. Although ports 80, 280, or 631 continue for IPP (Internet Printing Protocol) use, other insecure communications are ignored.
•514 UDP port for Syslog. Allows the Jetdirect to connect to a syslog server.
•515 TCP port for LPD. This port can be used when printing with LPD (for example, from UNIX ®)) or using the Microsoft ®) LPR port monitor. While port 515 is the listen or destination port, TCP ports 721-731 are the source ports on the host machine.
•547 UDP for DHCPv6.
•631 TCP port for IPP. IPP is an Internet Printing Protocol implementation available on HP Jetdirect devices that can be utilized by CUPS-based printing or Windows Internet Printing (ex: printer port is http://printservername/printername/).
•636 TCP port for LDAP over SSL. Allows MFP devices to perform address lookups with LDAP servers that require an SSL connection.
•1230 TCP for NTP (Network Time Protocol)
•1782 TCP port for Jetsend. HP has implemented a proprietary process wherein documents or digital pictures can be sent through the network to a printer for automatic printing. This requires proprietary Jetsend software with newer HP Jetdirect devices.
•1783 and 1784 TCP port for Digital Send Management. Used by HP Digital Send Software to communicate between the DSS server and the MFP device.
•2049 UDP for WJA NFS. NFS port used by HP Web Jetadmin for font and macro uploads to devices.
•3702 UDP for WS-Discovery.
•5353 UDP port for Bonjour (mDNS). Bonjour is typically used for IP address and name resolution, where a conventional DNS server is not available.
•9100 TCP port is used for printing. Port numbers 9101 and 9102 are for parallel ports 2 and 3 on the three-port HP Jetdirect external print servers.
•9280 TCP for scanning with the Embedded Web Server (9281 and 9282 for parallel ports 2 and 3 of the multi-port print servers). When attached to a device with scanning capabilities, the Embedded Web Server will allow a user to remotely scan documents.
•9290 TCP for raw scanning to peripherals with IEEE 1284.4 specifications. On three port HP Jetdirects, the scan ports are 9290, 9291, and 9292. (When you connect to a raw scan port, the scan gateway sends back "00" if the connection to the peripheral's scan service was successful, "01" if somebody else is using it, and "02" if some other error, for example, the supported peripheral is not connected. Ports 9220, 9221, and 9222 are the generic scan gateway ports currently only usable on 1284.4 peripherals.)
•34861 and 34862 UDP for WJA. Used by HP Web Jetadmin for font and macro uploads to devices.