Conrad Sallian's community posts

Hello Shane,

Thank you for the screenshots. We've just checked the file again with the most recent definitions and there was no detection. Here is a screenshot of the definitions version:



Feel free to refer to this article on Microsoft website on how to get the most recent updates.

P.S. You can place screenshots directly in the post using the 'upload image' link under the text field.

Hello Shane,

Thank you for your message.

Judging by the screenshot, this appears to be an issue that previously occurred with Windows Defender. However, Microsoft has informed us that the issue has since been resolved.

Please make sure your Windows Defender is up to date to apply the fix. If the issue persists after updating, please let us know.

Hello Hal,

If the inbound TCP port 5650 is open on the Host PC, the Host service is running, and the Viewer and Host are in the same subnet, there shouldn’t be any reason why the connection wouldn’t work—except, perhaps, interference from security software.

Hello Hal,

With a direct connection, it’s a different story—you do not need to check connectivity with the ID server at all. For direct connections, Internet-ID is not required, and you don’t even need to enable it in the Host settings if you plan to connect directly.

When direct connection issues arise, they are usually related to local IP addressing (routing/traversing) and port configuration. For instance, if the Viewer and Host are on the same network but different subnets—i.e., separated by a router—you’ll need to set up a port forwarding rule on that router. Without this, the Viewer cannot reach the Host via direct connection.

Additionally, make sure the listening port on the Host computer (5650 by default) is not blocked by Windows Firewall or any third-party firewall on that machine.

Have you already referred to the Knowledge Base article “Direct connection not working”? It lists all possible reasons why a direct connection might fail.

Let me know if you need further help.

Hello Hal,

Thank you for the logs. There are the following errors:

Socket Error # 11001 Host not found.(EIdSocketError)

Usually it means that the Host computer cannot find the ID server. Here is a related knowledge base article: https://www.remoteutilities.com/support/kb/socket-error-11001-host-not-found/

Hope that helps.

Hello Hal,

Feel free to send us your Host log files to support@remoteutilities.com for examination. You can zip the files before sending.

The Host keeps its logs (as html files) in this folder: C:\ProgramData\Remote Utilities\Logs

Note: the 'Program Data' folder is hidden in Windows by default. You should first enable 'Show hidden folders' in Windows Explorer.

Hello Hal,

Thank you for your message.

It looks like you cannot connect to the new PC where the Host installed. Depending on whether you connect using a direct connection or INternet-ID connection, one of these troubleshooting guides may help:

Can't connect using direct connection

Can't connect using Internet-ID

Hope that helps.

Hello Martin,

This is something we are currently working on. We apologize for the long wait, but we’ll do our best to release the first Host beta to you very soon.

Hello Tom,

Could you please clarify what specific notification option you are referring to.

Looking forward to your reply.

Hi Emilio,

The "via the Internet" part is not a strict requirement. If you use a VPN or tunnel, you can work through that just as well. Since most use cases involve Internet access, our documentation focuses on that, but VPNs and tunnels work too.

The primary requirement is that both Hosts and Viewers must be able to directly access RU Server.

Hope that helps!