Resolving IP Manager Issues
When you launch the Efinity software, it creates two server instances on
localhost for the IP Manager. The IP Manager uses these server instances for
inter-process communications. These server instances use randomly chosen port numbers
based on preset upper and lower bounds. The server instances are:
- IPM_Server = 127.0.0.1:<port number>
- RPC_Server= 127.0.0.1:<port number>
If your computer has closed the default port ranges (for example, your IT department has closed ports for security reasons), the two RPC server instances cannot connect to localhost and the software issues the message IP Manager RPC Server Not Connected.
To resolve this issue you need to:
- Talk to your IT department about opening ports for the IP Manager.
- Set specific default ports for the software to use instead of a range (so the IT department only has to open 2 ports).
The software defaults to using the port range 49152 – 65535 because these ports are dynamic, private, or ephemeral ports. They are open for any application to use and are not reserved by the Internet Assigned Numbers Authority (IANA).
To change the default port range to specific ports:
- In a text editor, open the app_session.ini file, which is
located in the Efinity
bin directory (<install
directory>/bin). The contents
are:
[config] ipm_server_port_lower_bound = 49152 ipm_server_port_upper_bound = 65535 efxg_rpc_port_lower_bound = 49152 efxg_rpc_port_upper_bound = 65535 - Change the configuration to use a single port by changing the upper and lower
bound numbers. The software selects ports using the scheme port_lower_bound
<= port_number < port_upper_bound. Therefore, set the lower bound
as the port you want to use and the upper nound as the next higher number; the
software uses the lower bound number for the port setting. For
example:
[config] ipm_server_port_lower_bound = 53123 ipm_server_port_upper_bound = 53124 # Software uses port number 53123 efxg_rpc_port_lower_bound = 49153 efxg_rpc_port_upper_bound = 49154 # Software uses port number 49153 - Save the app_session.ini file and then re-launch the Efinity software.