Management tools not working with remote connect - ORF Forums

@rené.klomp: Hello René,

Both error codes indicate a connection error (0x00002EFD means "cannot connect", 0x00002EE2 means "connection timeout"), so I think the ORF Service is simply not listening on IP:6242. Please verify your remote access settings on the System / Remote Access page of the Administration Tool. Specifically,

* The Remote Access service should be enabled
* The Local Bindings list should contain an "All Interfaces:6242" binding or an IP-specific binding
* The remote host IP must be on the Allowed IPs list with "All Services" or "Only Remote Administration" permission.

If these look OK, please make sure to save your configuration just in case the changes you made previously were not applied for some reason.

In any case, the ORF Service must be specifically allowed through the firewall.

Did the above help?

@rené.klomp: Thank you, I am glad to hear the issue is now fixed.

@michael_n: Hello michael_n,

Have you checked the "Allowed Hosts and Services" list on the ORF server to see if the connecting host is allowed to connect? (System > Remote Access > Allowed IPs). You will need to ensure that the IP of the connecting client is listed (check for possible typos) as an allowed host in the ORF server's configuration : http://vamsoft.com/r?o-hto-adm-allowedipservices . If there is a proxy between the client and the ORF server, try to connect directly (without the proxy).

@michael_n: Can you try to telnet the ORF server from the client by running the following command in the Windows Command Prompt (or PowerShell)? What message do you receive?

telnet [IP-ADDRESS-OF-ORF-SERVER] [CONFIGURED-REMOTE-ACCESS-PORT]

For example:

telnet 192.168.251.77 6242

@michael_n: The error message indicates that the connecting client is not authorized to access the ORF service remotely. I recommend that you temporarily allow all connections from the "192.168.*" range to the ORF server (update the System > Remote Access > Allowed IPs list in the ORF Administration Tool - on the ORF server), save the ORF configuration (Ctrl + S) to apply the new settings, and try connecting again from the remote client.

@michael_n: I also recommend that you check the IP address of the remote client to make sure the correct IP range is added to the "Allowed IPs" list: CMD > ipconfig /all

@michael_n: Based on the screenshots, the server and the client might be on two different networks (192.168.0.0/24 and 162.168.0.0/24) or what is more likely that you might have added the wrong IP address to the Allowed IPs list. Try adding "*" (asterisk symbol) temporarily to the Allowed IPs list, save the configuration (Ctrl + S), and see if that solves the issue.

@michael_n: Have you saved the ORF configuration (Ctrl + S) after adding the new entries to the Allowed IPs list? If so, try restarting the ORF service, please.

Furthermore, please check the version of the Management Tools installed on the remote client and the ORF service: "Help > About ORF Fusion ...". They should be identical.

@michael_n: Please send us (to ) the following from the ORF server *and* the remote client and we are going to investigate the issue:

> The output of the following commands (run in CMD or PowerShell): ipconfig /all

> The ORF configuration files called orfent.ini, and the orfcs.ini* and orfcs.remote.ini* files - *if they exist. They can be found in the ORF program directory, (default: C:\ProgramData\ORF Fusion).

Thank you.