Pauline's community posts

Hello Corey,

Thank you for your message.

Yes, this is a false positive detection. Unfortunately, we don't have much control over how various antivirus software treats our program. However, if you can't add it to the allow list at the moment, we encourage you to submit a false positive report to your a/v vendor, so they can clear the detection as soon as possible. You can follow this guide to submit a false positive report.
In addition, you can also try our latest public beta release to see if using it might help to resolve the issue. You can find more information on the beta release and downloadable files on this page.

Hope that helps.

Hello Anna,

Thank you for your message.

We recommend allowing access to id.remoteutilities.com, rather than a specific IP address, since it might prevent you from accessing our server infrastructure properly. To ensure a smooth and secure experience with Remote Utilities, we recommend simply enabling the program on the application level within your firewall settings, rather than attempting to whitelist specific intermediate server IP addresses. This approach will allow Remote Utilities to function optimally while still maintaining the security of your network.
As an alternative, especially if your company has some stricter policies in place, consider using self-hosted RU Server instead. RU Server can be used in isolated environments and also offers a number of additional features, such as address book sync, authentication, etc. You can download an installation file for the RU Server on this page.

Hope that helps.

Hello Benny,

Thank you for your message.

Unfortunately, we weren’t able to reproduce this issue for now. However, I’ll forward it to our developers to see if they can provide any additional feedback on this or if they might need some additional information.

We will keep you updated.

Hello,

Thank you for your message.

We will contact Avast a/v team and let them know about this, so they can remove the detection. In the meantime, please feel free to submit a false positive report to Avast as well, since this can help to speed up the process. Here’s a guide on how to submit a false positive report.

Hope that helps.

Hello Johnny,

Thank you for your message.

Unfortunately, Agent for Mac/Linux is currently in beta testing stage and does not have logging available at the moment. However, we definitely will add logging feature in the subsequent updates. You can see the full list of features currently available for Mac/Linux Agent and Viewer on this page.

Let us know if you have other questions.

Hello Bruce,

Thank you for your message.

Please make sure that your Host installation folder is added to the exception list of your antivirus/firewall software and ports used by Remote Utilities are allowed as described in this troubleshooting guide.
You can also try fully uninstalling and then re-installing Host following this guide.

If the steps above do not help and the issue persists, please let us know.

Hello Carlo,

I’m glad to hear it works for you now!

Please feel free to contact us if the issue reoccurs or if you have any other questions.

Thank you!

snk-nick,

You can send us the latest Host logs from one of your remote Hosts that should be using your RU Server. In addition, please also send us the full file that you've quoted in your first message, so I can forward it as well.

Thank you.

snk-nick,

Could you please send us the full Host log file for a review? I will forward it to our developers, so they can examine it and provide feedback. You can send it to support@remoteutilities.com.

Looking forward to your reply.

Hello Carlo,

Thank you for your message.

Could you please verify if you’re using the latest Remote Utilities version 7.2.2.0? Are you able to locate the Host log files and send us the most recent logs from at least one of your Host machines? You can send it to support@remoteutilities.com for examination.

Looking forward to your reply.