Ports required by Ephesoft

Topic/Category: Best practices

Applies to: All versions of Ephesoft

Issue: Ephesoft requires certain ports to be open in order for Ephesoft to function properly. Below is a grid with the port number, it’s purpose, whether inbound or outbound rules must be created, and which network protocol the firewall exception must be created with.

Ephesoft Ports

noPort #PurposeInbound/OutboundNetwork ProtocolWhat Servers to Enable it on
18080Web UIInbound and OutboundTCPAssigned WebUI Servers Only (Public)
221099LicensingInbound/OutboundTCP/UDPAll Servers (Internal Only)
38009Apache to Tomcat communicationslocal communication onlyN/AAll Servers (Internal Only)
48100OpenOffice to Tomcat communicationslocal communication onlyN/AAll Servers (Internal Only)
580Optional Web UIInbound/OutboundTCPAssigned Transact WebUI Servers or Admin Assigned HTTP IIS or Apache Servers Only (Public)
6443 & 8443SSL PortsInbound/OutboundTCPAssigned Transact WebUI Servers or Admin Assigned HTTP IIS or Apache Servers Only (Public)
78005Tomcat Shutdown PortInbound/OutboundTCPAll Servers (Internal Only)
850001-50005http (Advanced Web Scanner on client workstation)Inbound/OutboundTCPClient Workstations (Internal Only)
960001-60005https (Advanced Web Scanner on client workstation)Inbound/OutboundTCPClient Workstations (Internal Only)
108900Java Monitoring Service for TomcatInbound/OutboundTCPAll Servers (Internal Only)
1149152-65535RMI ports rangeUsed by RMI registry for communication between the stub and the remote objectTCP All Servers (Internal Only)

 

Documentation Main Page How To Articles | Downloads and Updates |