Pauline's community posts

Hello,

Thank you for the clarification.

From what I understood reading that page, basically inbound port 5655/tcp should be open. This is what we have done from the start. However outgoing access to port 5655 (for viewer or host access) was blocked. The reason was that the viewers and hosts are not accessible from the relay: only the viewer/host can connect to the relay, the other way is not allowed.

Yes, you are absolutely right, on the RU Server's side, you need the inbound TCP 5655 port to be opened, not the outbound.

We could try to update the relay only, and also some clients. But upgrading all the clients is difficult currently. Would there be a problem if we did not change the viewer and host, but only upgraded the relay to 2.9 beta 1?

Of course, we actually suggest not to update all of the remote Hosts and Viewers at once, it's best to update just one remote Host and one Viewer (or even use the Portable Viewer and Agent). However, please note that if you update the RU Server, then it's best to update Viewer and Host as well since the version mismatch might also cause other performance issues and some features not working.

Please let us know if the issue persists after updating Remote Utilities to the Beta version.

Hello Keith,

Thank you for the clarification.

The Viewer is built for the 64-bit systems since it's also possible for the 64-bit systems to run applications built for the 32-bit systems. Unfortunately, it's not possible to run the 64-bit applications on the 32-bit systems. Sorry for the inconvenience.
However, we might release a separate Viewer built for 32-bit based systems in the future.

Please let us know if you have more questions.

Hello,

I'm glad to hear we were able to help!

Can you change 'menu name' to another like 'Custom client wizzard'?

Could you please clarify if you mean the Agent's title text that is shown on the title bar of the Agent window?

If this is the case, then this text can be customized on Step 3 - Advanced options of the configuration process -> Integrate your logo tab. You can also preview how the customized Agent window looks by clicking the Preview button on the same tab.

Please let us know if you have more questions.

Hello Damian,

Thank you for the clarification.

Unfortunately, it seems that the issue is rather on the remote Host's side and not on the Viewer's side.
In order to isolate the issue, could you please try connecting to the remote Host using the Portable Viewer and see if you're able to connect this way? The Portable Viewer is available for the download on this page.

Looking forward to your reply.

Hello Mike,

I'm glad to hear we were able to help!

Please feel free to post another message if you have more questions. We're happy to assist!

Hello,

Thank you for your message.

Could you please clarify if there is any antivirus/firewall software installed on the RU Server machine?  In case if there is, then the issue might be caused by the software blocking the rutserver.exe. We highly recommend that you add the RU Server folder C:\Program Files (x86)\Remote Utilities - Server\ to the antivirus exceptions list.
Also please check that the outbound ports required for the RU Server are not blocked/used by some other software. For more information on what ports are required to be open for the RU Server please refer to this page.

In addition, could you please clarify what version of Remote Utilities do you use? If you use the 6.10.10.0 version or older versions, then please try updating the RU Server to the latest version - 2.9 Beta 1 and see if this helps to resolve the issue. The 2.9 Beta 1 version is available for the download on this page.
When updating RU Server please make sure to update both Viewer and remote Hosts to the corresponding 6.12 Beta 1 version as well - the version mismatch might lead to performance issues or some features not working. You might try updating just one of the remote Hosts and one Viewer or even use the portable Viewer first to see if the issue still occurs when using the updated version of Remote Utilities.

Please let us know if the issue persists.

Hello Keith,

Thank you for your message.

The Exec format error usually means that Ubuntu wasn’t able to interface correctly with the binary, i.e. that it’s designed for a different chipset than your kernel currently supports. Could you please clarify which CPU arch your Ubuntu have - is it 32-bit or 64-bit?
Please type arch in a terminal window to find out whether your system is 32-bit (result is i686) or 64-bit (result is x86_64).

Looking forward to your reply.

Hello,

Thank you for your message.

Could you please clarify if I'm right in assuming that you want to use a few different Agents that point to a few different self-hosted RU servers? Or if you mean that you want to change the public Internet-ID sever to the custom Internet-ID server prior to running the Agent?
If this is the case, then, please consider configuring custom Agents using the MSI Configurator tool. This way, you will be able to customize Agent by adding your logo and welcome text and pre-configure Agent settings, including specifying your custom Internet-ID server.

In case if you mean something else, then could you please elaborate a bit more on the suggested feature?

Hope that helps.

Hello Mike,

Thank you for your message.

If I disable everything except the Remote Utilities - Host in her machines 'Services' tab will I still have access?

Yes, this should work. The issue you've encountered occurred because of all the services being turned off, including the Host service, as its service must be running on the remote Host PC in order for the Host to work properly.
In addition, when turning off the services and rebooting the remote computer, please make sure that rfusclient.exe and rutserv.exe system processes are running on the Processes tab of the task manager.
Also, here's a related KB article that might be useful in your scenario.

Hope that helps.

Hello Damian,

Thank you for your message.

Could you please let us know what version of Remote Utilities do you use? Please make sure that you update Viewer and Host to the most recent version - as of this writing, it's 6.10.10.0 or 6.12 Beta 1 version.

In addition, before we proceed to further troubleshooting, please try referring to this KB troubleshooting guide and see if any of the solutions listed there help to resolve the issue.
Namely, we recommend that you check if the required outbound ports are opened and not blocked by your firewall/not used by another software. For more information on the required ports please refer to this Documentation page.

Please let us know if the issue persists.