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
no Port # Purpose Inbound/Outbound Network Protocol What Servers to Enable it on
1 8080 Web UI Inbound and Outbound TCP Assigned WebUI Servers Only (Public)
2 21099 Licensing Inbound/Outbound TCP/UDP All Servers (Internal Only)
3 8009 Apache to Tomcat communications local communication only N/A All Servers (Internal Only)
4 8100 OpenOffice to Tomcat communications local communication only N/A All Servers (Internal Only)
5 80 Optional Web UI Inbound/Outbound TCP Assigned Transact WebUI Servers or Admin Assigned HTTP IIS or Apache Servers Only (Public)
6 443 & 8443 SSL Ports Inbound/Outbound TCP Assigned Transact WebUI Servers or Admin Assigned HTTP IIS or Apache Servers Only (Public)
7 8005 Tomcat Shutdown Port Inbound/Outbound TCP All Servers (Internal Only)
8 50001-50005 http (Advanced Web Scanner on client workstation) Inbound/Outbound TCP Client Workstations (Internal Only)
9 60001-60005 https (Advanced Web Scanner on client workstation) Inbound/Outbound TCP Client Workstations (Internal Only)
10 8900 Java Monitoring Service for Tomcat Inbound/Outbound TCP All Servers (Internal Only)
11 49152-65535 RMI ports range Used by RMI registry for communication between the stub and the remote object TCP All Servers (Internal Only)

 

Documentation Main Page How To Articles | Downloads and Updates |

Was this article helpful to you?

J.D. Abbey