cosmos's community posts

Hello Polina,

Polina Krasnoborceva wrote:
Could you please clarify if there is any antivirus/firewall software installed on the RU Server machine?  In case if there is, then the issue might be caused by the software blocking the rutserver.exe. We highly recommend that you add the RU Server folder  C:\Program Files (x86)\Remote Utilities - Server\  to the antivirus exceptions list.

This is a Windows 7 SP1 VM. No antivirus was running from the start. I used to have the Microsoft firewall enabled, but I've disabled it as well.

Also please check that the outbound ports required for the RU Server are not blocked/used by some other software. For more information on what ports are required to be open for the RU Server please refer to  this page .

From what I understood reading that page, basically inbound port 5655/tcp should be open. This is what we have done from the start. However outgoing access to port 5655 (for viewer or host access) [b]was blocked. The reason was that the viewers and hosts are not accessible from the relay: only the viewer/host can connect to the relay, the other way is not allowed.

In addition, could you please clarify what version of Remote Utilities do you use? If you use the 6.10.10.0 version or older versions, then please try updating the RU Server to the latest version - 2.9 Beta 1 and see if this helps to resolve the issue. The 2.9 Beta 1 version is available for the download on this page .

We are using the latest releases 6.10.10.0 for viewer and host and the latest stable relay version.

When updating RU Server please make sure to update both Viewer and remote Hosts to the corresponding 6.12 Beta 1 version as well - the version mismatch might lead to performance issues or some features not working. You might try updating just one of the remote Hosts and one Viewer or even use the portable Viewer first to see if the issue still occurs when using the updated version of Remote Utilities.

We could try to update the relay only, and also some clients. But upgrading all the clients is difficult currently.  Would there be a problem if we did not change the viewer and host, but only upgraded the relay to 2.9 beta 1?

I'm currently testing RU relay on Windows 7 SP1 64bit VM (ESXi), with 3Gbytes of RAM. Nothing runs on this VM, apart from the relay. There are around 300 hosts ready to be connected to ("idle connections" on the relay administration). There around 20-30 systems being remote controlled (which corresponds to the double number of lines on the "active" panel).

The problem is that the relay seems to freeze. At that point all remote sessions are halted. The only way to get out of this is to restart the service itself. Nothing is logged in the error and connection logs of the relay server.

Task manager on this VM shows that resource usage (RAM, disk, network) is very low. So it doesn't seem like a hardware issue.

As it is, this does not look stable for extensive use, which would be a blocker for me... Any ideas on what to look for?

Polina Krasnoborceva wrote:

Could you please let us know if there are some apps installed on the Huawei mediapad T5 that might have some control over the network?

I've got  [censored] quicksupport installed.

In addition, could you please provide us the full mobile Viewer logs from the Huawei tablet for examination?

The log contains only lines in the form I've written above. No other log lines whatsoever.

Also please let us know if you have already tried reinstalling the app on the Huawei tablet.

Ok, here's the crazy part. I uninstalled your app, after uninstalling the teamviewerQS application. I then reinstalled RU and it worked just fine!

I'm really buffled why this happened. I can't reproduce the issue anymore.

Hello Polina,

the connection was setup correctly. I'm using the exact same configuration with my mobile phone in fact. But for some reason, it does not try to connect via the custom relay on the Huawei tablet.

I've been trying all sorts of RU connections and I'm extremely satisfied. The relay functionality is especially excellent so far!

Today I tried to connect to a Windows host, via a custom relay, using a Huawei mediapad T5. Although I configured it to use my custom relay server, it does not use it. Instead, it constantly tries to use your own relay server, as I can see from the logs:

... Method "Connect" - OK. ID-from-custom-relay connected to ID server: id.remoteutils.com.
.. Connection to "ID-from-custom-relay" failed.

Note that I can connect to the same host using my Oneplus 6 Android phone just fine.

FYI, this is Huawei Mediapad T5 with 4Gb of RAM, running Android 8.

I feel really stupid, I did not see the following part (bold made by me):

Polina Krasnoborceva wrote:
For the scenario you've described above, you can also use  Portable Viewer  - it provides the same functionality as regular Viewer but doesn't require installation. The only difference is that Portable Viewer stores all files in a single folder that you can upload a Dropbox folder, Google Drive or even USB flash drive, so you always have access to this Viewer.

Did that, works awesome! Case closed. Thanks again!!!

Polina Krasnoborceva wrote:

Please note that the address book will not be copied to another machine along with the settings. In order to copy the address book please refer to  this page .

I see a file connections_4.xml in the same appdata directory, can't I just copy it to the other system?

Good morning,

perhaps you should try to recreate the issue:

* Install viewer in a LAN that has both IPv4 and v6
* Create a one-click host using the online configurator and check use IPv6
* Install this host in the same LAN
* Connect to the system directly over IPv6, should work
* Try to connect to system directly over IPv4, does it work?

Polina Krasnoborceva wrote:
Could you please let me know if you're able to establish a connection using the IPv4 address to the Host when the  Use IPv6  checkbox is  disabled ?

No, it did not change anything. I could see that there was an IPv4 listener but I could not connect.

In addition, please clarify if you have selected the Use IPv6 checkbox in the Host Settings -> Network -> Port tab only or if the checkbox is also ticked in the following location:
Right-click on the connection in the main Viewer window and select  Connection Properties , navigate to the  Network  tab:
   
If this checkbox is not selected, please try to enable it and see if the issue persists.

I have uninstalled the one-click host which had IPv6 enabled, sorry. Initially it was enabled in both places. I could not connect via ipv4. I deselected it and still couldn't connect...

I've created a one-click custom executable, having enabled IPv6 in the settings. If I understand correctly, it allows IPv6 traffic in addition to IPv4. If not, then the following is a feature and not a bug, no need to fix anything.

I've installed this on a system on a LAN that has both IPv4 and IPv6 enabled. I can connect to the host just fine with Internet-ID. I can also connect to it using a fe80 IPv6 address. I can't connect to it using IPv4, even though I see that a listener does exist on 5650/tcp4.

Can you try to reproduce this?