Conrad Sallian's community posts

Hi Johnran,

Could you please clarify which specific message you’re seeing? There are two possible pop-up alerts, both described here:

https://www.remoteutilities.com/support/docs/first-connection-warning/

The persistent alert is only shown to users of the free license — it does not appear for commercial license users.

The temporary alert, if that’s what you’re referring to, appears only once and only under certain conditions — namely, if you're using a configured Host package and connecting via Internet-ID (this alert doesn’t show for direct/LAN connections). Once the OK button is clicked, it will not appear again for that Host.

This alert is an important part of our privacy safeguards and helps distinguish Remote Utilities from rogue/malicious remote tools. Without such measures, Remote Utilities might be falsely flagged and blocked by antivirus software, preventing it from working properly.

Let me know which message you’re seeing and I’ll be happy to assist further.

Hello Cory,

Thank you for your message.

Our Mac version is currently in development, and we plan to provide a beta version for open testing as soon as possible. While we don't have a specific release date yet, we’ll be sure to announce it once it's ready.

Hello,

Thank you for your message.

We are currently planning a 7.x.x.x release with quite a few changes. 8.0 release is at a more distant future.

Hi Douglas,

Ping won’t necessarily work because the ping command may be blocked on the server depending on its security settings.

It is confirmed that the connections were not refused at the servers?

They were not—why would they be? Besides, according to your logs, the Host service is clearly running and sending connection attempts, but they can’t get through.

And bear in mind two other machines on this internal network are working as they always have even though they suffered a power cycle also.

Are they also accessing the Internet via the same ISP?

Hi Douglas,

No connection.
I've added a rule to insure port 5655 allows a connection outbound.
No connection.
I have sent you the log file.
Any clue now on why?

If the Host is working (the service is running), there’s an Internet connection on the Host side, and there’s still no connectivity with RU public servers, the most probable cause is security software blocking outbound access for Host. In this case, it’s not necessarily the endpoint software — it could be a perimeter firewall (especially in an organization) or the ISP. That should be the first thing to check.

None of these have any option for reinstall.
Often a "check for updates" appears in things like the "about Remote Utilities"
Is this an oversight or is it quite impossible for this service to manage downloading and
running an update of itself?

It is not an oversight — it is intentional. Why? To avoid the loss of control over the update process and prevent a situation where remote Hosts are updated to a newer version than the Viewer, which might break some functions. The Viewer is supposed to orchestrate the updating process — both for itself and for the remote Hosts.

Hosts can be updated from the Viewer side in multiple ways, one of which is called "Simple update," which essentially sends an update command to the Host for the Host to self-update.

Hope that helps.

Hello Douglas,

Why Port 443?
I've only heard of port 5655.

This is a fallback port used instead of 5655, in case port 5655 is unavailable for any reason. Ports used by Remote Utilities.

Hi Rick,

Yes, we've just renamed the license for clarity.

Thanks.

Hello Geoff,

Thank you for your message.

Is there any specific information or a screenshot as to what parts are blocked? There's also a post on the subject in the Microsoft community here.

Hello Russ,

Thank you for your message.

You could open (e.g. via File Transfer) the C:\Program Data\Remote Utilities\Logs\ folder on the remote computer. These are the Host logs and if Internet-ID is enabled the Host's Internet-ID is reported in them. In a line like this:

Relay node: OK ID: xxx-xxx-xxx-xxx; Port: 5655; Try count: 1

Hope that helps.