Conrad Sallian's community posts

Hello Matthew,

Yes, you can. First, let me tell you just in case that a "hardware-bound" ID had only briefly been introduced in one of the previous updates. But then we realized that it was a bad idea and cancelled that change. So currently the Internet-IDs are not hardware-bound. Even if two machines are perfect clones of each other their IDs will be different.

Here is how to get a unique ID automatically on each cloned machine with a pre-installed Host:

1. Configure your custom Host (Standard MSI) using the MSI Configurator. Make sure that you enable "Generate Internet-ID" option and send ID via email etc. on the 3-rd step of the configuration process.

2 Run the Host installation. In the "Installation options" step UNcheck  "Launch Remote Utilities - Host after installation...".

3.  When the Host has been installed copy the program files and export the Host's registry entry with the settings (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Usoris\Remote Utilities Host ) and embed them into your system image.

The trick is that you install the Host but not run it yet (to avoid generating Internet-ID too early). The first run of the Host should happen when the cloned system runs/starts up the first time rather than during the image creation.

Let us know if this workaround works for you.

Hello Chad,

We are not sure what might be causing this, apart from possible routing/network issues on the Hosts' side. Do you have a system administrator on those site/sites who could check connectivity with your server and figure out the bounces?

Hello John,

You should update the software to the most recent version. Also, please check this knowledge base article https://www.remoteutilities.com/support/kb/invalid-registration-key-when-registering-remote-utilities/

Hope that helps.

Hello Michael,

Do you use a self-hosted server as well? If so, yes - feel free to test out the new 64-bit version and see if it helps fix the problem.  

Thanks.

Hello,

Here is an instruction I mentioned earlier:
https://www.remoteutilities.com/support/kb/how-to-collect-data-for-diagnosing-connectivity-issues/

It will save all of us time when figuring out the problem. Note that Remote Utilities is software of "dual nature". A connection involves at least two and sometimes (in case of ID connection) - three modules including an ID server. So we need logs from all of the modules along with the date and time of when the issue happened.  

Thank you.

Hello Jon,

The Viewer log alone won't help us figure out the issue. We also need the Host's log and other information. If you wait a bit we will come up with  a detailed instruction in our knowledge base on how to collect the necessary logs and what to send to us. I will provide a link to the knowledge base article later today or tomorrow.

Is there a way I can download an older copy of the viewer, as some have stated running an older version fixes this issue?

Downgrading to an older version is not recommended. Besides, before we examine your complete logs we cannot be sure if your issue is the same as the one reported in this thread.

Let me draw an analogy - a high human body temperature is a sign that something is wrong, but it can be caused by many factors (specific illnesses). The same is true about a connectivity problem - on the surface it looks the same, but the cause might be different in each case, although there are not many of them actually.

Hello Greg,

Thank you for the details.

- With remote machines at two locations, the issue seems to be much worse at the location that has a lower bandwidth, and less stable connectivity.

This might be a factor.  

- At this "worse" location (Eastern US time-zone), the problem is almost non-existent prior to 12:00 or 13:00, at which point it gets quite bad and remains so until around ~19:00. Weekends are usually problem free. I've wondered if net usage in local geographic area is a factor.

Yes, perhaps. Our servers can sustain far more load than they experience now so it is very unlikely that the time of day has any significance when it comes to servers themselves.

- It's a far less desirable configuration, but if I establish a VPN connection to this "worse" location, and connect to the remote station by local IP instead of Internet-ID, the issue is reduced (eliminated?).

Direct connection is a totally different thing than Internet-ID.

Hello Chad,

Currently, we are working on a 64-bit server version and it is already available for testing. I recommend that you replace your current server with a 64-bit version and test to see if you still have issues. Here is how:

1. Back up your server installation folder - just copy it elsewhere  

C:\Program Files (x86)\Remote Utilities - Server

2. Back up (export) server's registry entry

HKEY_LOCAL_MACHINE\SOFTWARE\Usoris\Remote Utilities\MiniInternetId

3. Stop the server process in Windows Task Manager - look for "Remote Utilities Server (32bit)".

4. In the server installation folder run uninstall.cmd as administrator.

5. Download new files and replace the files in the server installation folder.

6. In the server installation folder run install.cmd as administrator.

7. Restart the computer. Make sure that the server process is running (it may say "RMS" in this test build).

Your server logs and data should stay intact. Please, test the new build for a while and let us know of the results.

Thanks.

Hi Michael,

Yes, of course, whatever is more convenient to you.

Chad Brandenburg wrote:

I am constantly getting drops, did a constant ping, and never took errors and was constantly around 30ms or less.. But sites just randomly disconnect for no reason.

Hello Chad,

I would recommend that you create a separate thread/topic devoted to self-hosted server connectivity issues. Or you can join this topicthat reports a similar issue.  We need to keep self-hosted server issues separate from public server issues as they are dealt with differently.

Thanks.