Last Updated on

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
1 8080 Web UI Inbound and Outbound TCP
2 21099 Licensing Inbound/Outbound TCP/UDP
3 8009 Apache to Tomcat communications local communication only N/A
4 8100 OpenOffice to Tomcat communications local communication only N/A
5 80 Optional Web UI Inbound/Outbound TCP
6 443 & 8443 SSL Ports Inbound/Outbound TCP
7 8005 & 8009 DB Ports Inbound/Outbound TCP
8 50001-50005 http (Advanced Web Scanner on client workstation) Inbound/Outbound TCP
9 60001-60005 https (Advanced Web Scanner on client workstation) Inbound/Outbound TCP
10 8900 Java Monitoring Service for Tomcat Inbound/Outbound TCP
11 49152-65535 RMI ports range Used by RMI registry for communication between the stub and the remote object TCP

 

Documentation Main Page How To Articles | Downloads and Updates |

Was this article helpful to you?

J.D. Abbey