Conrad Sallian's community posts

It is the IP address of one of our Internet-ID servers, in California.

You see this IP address because:

1. You use Internet-ID connection type.
2. The Internet-ID relay server infrastructure (a relay server) is our public one. You can see that in connection Properties -> General tab, under the "internet-ID" radio button.  

The fact that the remote PC is in your LAN has nothing to do with this. If you need to use direct connection within your LAN , that is - without an intermediary server in-between - simply select the "Direct connection" radiobutton in connection properties and specify the local IP address or hostname of your computer/server.

Hello Jason,

What IP is this? This server is local to my LAN, and that IP doesn't match my external IP.

Is it from the "Last IP" column?

I see. Before we try to diagnose I recommend that you install the latest beta, you can take it from here https://www.remoteutilities.com/download/beta.php . If it's a bug, it well may have been already fixed in the beta. If the problem persists even with the beta, we'll see further what it might be.

Please, make sure that you upgrade both parts - i.e. Viewer and Host - to avoid version mismatch.

Hello,

Thank you for your message.

Have you tried to restart the remote PC after Host installation?

Hi Peter,

You are welcome. I can assure you that we'll do our best to report as many false positives as we can and reduce the number of them to a minimum or even zero. Reporting false positives on our software to a/v software companies is an ongoing work that we do on a regular basis.

Don't hesitate to post here if you ever need any assistance.

Hi Peter,

No, you don't have to go anywhere to activate it, of course. The host should run upon installation and even restart is not needed in most cases.

This looks like antivirus software activity. Before you reinstall the Host, could you please add the Host installation path to your AVG exceptions list. The path is C:\Program Files\Remote Utilities - Host\* . Asterisk means "any file within the folder". If you have a 64-bit system your path will be C:\Program Files(x86)\Remote Utilities - Host\*

Also, I recommend you use the latest beta. You can download it here https://www.remoteutilities.com/download/beta.php

Hello Peter,

Thank you for your post.

Looks like the Host service won't start for some reason or installation got corrupted somehow. Could you tell me what the operating system is on the Host PC and which product version you use (stable or beta)?

You might also want to try to complete wipe the Host installation and re-install from scratch. See this documentation page. Note that if you are using the current beta version the registry key with Host settings is located here HKEY_LOCAL_MACHINE\SOFTWARE\Usoris\

Hope that helps.

Hello Kenny,

Thank you for your message.

Could you please clarify what specific registry entry did you delete?

Hello Dmitri,

Dmitri wrote:

Ok, fixed, I had to add users who is enabled to login.
And now question - despite of security mode - viewer always connects to currently active user account...
Is there any way to connect viewer to specific user account? Not to the active one?

If there multiple terminal sessions (i.e. there is a terminal server running on the remote PC) then you can switch to a specific session. However, even in that case you'll still connect to the console session first and have to use a terminal session switch icon on the Full Control mode toolbar.

Please, note that it's only the existing terminal sessions that you can connect to. Remote Utilities cannot create terminal sessions for you, i.e. it cannot act as a terminal server itself.

Hello Dmitri,

If you can connect from another Viewer then the Host is ok, and the issue may have been on the Viewer side, not the Host's.

In this case a corporate/perimeter firewall is often to blame. You might have certain outbound ports blocked on the corporate firewall level. You need to make sure they are open and that our relay server is accessible. This documentation can help:

https://www.remoteutilities.com/support/docs/ports-used-by-remote-utilities/#public

Let me know if you figure out the cause for the issue. Thanks.