Conrad Sallian's community posts

Hi Michael,

Thank you for the report. Could you let us know which Remote Utilities IP address Norton is flagging? We would like to contact them about this as well.

Hi David,

Thank you for your message. We also responded via the ticket system, but we will reply here as well just in case.

This may have been caused by a temporary switch to a different primary server, but now that maintenance is complete, we will be reverting back. Either this issue will resolve on its own, or, if not, we will submit a false positive report to AVG.

Thank you for your patience.

Here is a result of DNS propagation test from multiple locations:

https://dnschecker.org/#A/id.remoteutilities.com

All point to an updated IP address.

If it's possible, try checking how the id.remoteutilities.com resolves on both sides - Viewer and Host. If you still cannot connect, there's a good chance that the DNS still uses a cached value and haven't updated yet.

Hello,

Our servers were back online almost immediately. Please, flush the dns resolver cache on the Viewer computer , that should help.

Sorry for the inconvenience.

Hello Dax,

Thank you for your message.

Someone will only be able to access a remote system if they have access to your Viewer app on that specific computer. Remote Utilities keeps its address book locally, not in the cloud.

If this is an issue, you can additionally encrypt your address book with a password that only you know. Here is how: https://www.remoteutilities.com/support/docs/encrypting-address-books/

This will let you save your passwords without worrying that your address book can be accessed by someone else.

Hello,

We've released an update including RU Server update 3.5.5.0. Download page.

Thanks.

Hello,

Thank you for your message.

Cloud connection for version 6.x.x.x for free licenses has long been disabled. If you use a free license please, download and install version 7.

Hope that helps.

Hi Simon,

Please, try the new update - beta 26 released yesterday and let us know if the issue persists. Thanks.

Hello everyone,

Yes, it is our server at 172.241.164.247. RU uses end-to-end encryption, and the servers simply relay the encrypted traffic. They cannot inspect forwarded packets and do not store any data.

The reason for this alert is banal and very typical for the modern “security industry”. Apparently, someone was “hacked” using social engineering methods, which in this case simply means they voluntarily installed RU, gave their access credentials to a fraudster/attacker, and the attacker connected to their computer using RU. The victim then complained to their ISP, the ISP submitted an “abuse report” to the hosting provider Leaseweb, and that was enough for the IP address to be labeled as a “botnet server”, despite the fact that it is used by hundreds of thousands of perfectly legitimate connections.

I don't know if it's possible to guarantee the ip-addresses are actually official RU servers. I

It is possible. Just ask here and we will answer. However, we will not disclose our entire infrastructure because we do not want it to be DDoSed or otherwise targeted. That is quite understandable.

Do not hesitate to ask if you have any questions.

Hello everyone,

We've updated the macOS and Linux versions to beta 24. A final release will follow soon once we implement the file manager (File Transfer mode), which is our current top priority.