Community

Hello Nijel,

I installed 6.12 Beta 2 host and the typing problem seems to be resolved now.

I'm glad to hear that we were able to help and it works for you now!

I was unable to reproduce the crash but I will keep launching viewer from linux terminal each time I use it & will hopefully have something to share soon.

In case if you will be able to reproduce the issue once again, please feel free to send us the terminal output. You can send it to support@remoteutilities.com or create a ticket and attach the file to the ticket.

Please let us know if you have more questions.

Hello Yann,

Thank you for your message.

I therefore upgraded from the 6.10.10 version to the beta 6.12.2b2, but it still shows 'Upgrade required'.

This is actually expected behavior as it is a newer beta version of Remote Utilities. In our future updates, we'll make the program update Hosts' version information immediately during the online status check without the user having to log in on the Hosts at all. Could you please let me know if you've logged on to the remote Host after updating it?

I also lost connection during the update and had to complete it manually on the remote machine.

Perhaps, the disconnect occurred due to the remote Host service being restarted after the update (which is required). Could you please confirm if you've waited for approximately 10-15 seconds for the remote Host service to restart before trying to reconnect to the Host?

Looking forward to your reply.

Hello Yann,

Thank you for your message.

I checked with our developers and they confirmed that the "update is required"  displaying in Viewer for the latest 6.12 Beta 2 version is expected behavior. Sorry for the inconvenience.

I face some disconnections after a bit of inactivity on the host (I connect through Internet-ID not direct IP, I'm on the same local network). It happened several times that when re-connecting I had some crashes from the viewer.

In case if your Viewer and Host are on the same LAN, then please note that it's recommended to use Direct connection as it's always more stable and faster than the Internet-ID connection. In addition, please note that even if you use Internet-ID connection, but there's a direct route available between Viewer and Host then it will be used automatically because of the direct route detection mechanism implemented in the program.
As for the disconnects please try referring to this troubleshooting guide to see if any of the solutions listed there help to resolve the issue. Namely, we'd recommend that you check if there is any antivirus/firewall software installed on the remote Host machine that might be blocking ports/Remote Utilities. If this might be the case, then please try whitelisting Remote Utilities as described in this guide.
In addition, in case if the solutions above did not help, please feel free to send us Host connection log files for examination. You can send the logs to support@remoteutilities.com.

Hope that helps.

Hello,

Thank you for your message.

I do not have admin rights on that PC. So I installed RemoteUtilities host without admin rights.

Could you please clarify if you mean Agent? If this is the case, then could you please clarify if you mean that you cannot log in to a Windows user when connecting to the locked remote machine?
If this is the case, then please note that this is not how the Agent is supposed to be used - in the described scenario, the Host module should be used instead (however, please note that administrative privileges are required in order to install the Host).

Hope that helps.

Hello,

Thank you for your message.

I've checked on this with our development department just in case - unfortunately, not proceeding to the screen with the password field is expected behavior. You can only log in to a locked Windows user when using Host, it wouldn't work for the Agent module as it's meant to be used for spontaneous remote support and can be run by a standard Windows user.

Sorry for the inconvenience.