Would these problems have affected a self hosted RU server? I had some problems connecting to hosts the past few days but I think I figured it out that I was inadvertently exceeding the license limit by using my single PRO license on Linux Viewer to connect to my Windows PC which has the same PRO license to then connect to hosts using my self hosted server and shared address book. I just re-read the EUA licensing and realize I was probably not supposed to be doing that, and checking the logs on my server saw talk about licensing error exceeding limits or something like that and after logging out all but one computer from the shared address book that allowed me to connect to hosts again, so long as only one Viewer is in use at a time, although, I did notice by signing out of Linux Viewer I can still control the Windows Viewer PC with a direct LAN connection, so I can still use it the way I like to. My bad! I wasn't trying to break the rules on purpose, I just find the Windows Viewer is much more reliable at maintaining multiple host connections than the Linux Viewer is, and I prefer to use Linux so that's the only reason I was using the program that way.
Although not the most time efficient or reliable way, with the current Windows and Linux/Mac Remote Utilities versions available, by the application of Virtual Machines it is possible to use the Remote Utilities Windows Viewer from Mac or Linux to transfer files to other native or virtual Windows computers . You can run the Windows Viewer on a virtual Windows machine on Mac or Linux and connect to other virtual or native Windows machines. There is a very fine open source program called Syncthing that accomplishes file transfers between computers of any O/S with no intermediary storage servers either by LAN or over the internet.
Obviously the scenario I just described has it's flaws and limitations and isn't as easy or flexible as having Windows version features on the Mac/Linux version.
I'm with you in the need of a completed native Linux/Mac Remote Utilities Host and Viewer that has all of the Windows features, but for now we have to work with what is available, or use another remote access program. With some creativity, even when the direct route isn't there, there is usually a roundabout way of accomplishing a goal.
I'm very pleased with the 1.0.12.q Beta 12 upd ate. In my experience the program has ceased it's periodic crashes and the auto-reconnect feature makes this an essential update over all previous Linux Viewers. Good things come to those who wait.
I was wondering if the bug that caused the Linux Viewer to corrupt data while editing a remote address book was resolved? I have not tested this myself yet, I just remember it being an issue for me in the past and the solution for me was to se t the Linux Viewer user account to Read Only and use the native Windows Viewer to manage the remote address book.
Thank you for the update. I appreciate the attentiveness of the RU team. The programs keep getting better. I used this guide to migrate my self hosted server from a native Windows 10 machine to a virtual Windows 10 machine running under Manjaro Linux using Virtualbox. Then, on that same computer, I created another virtual Windows 10 machine to be my "address book keeper" with which is the only user with write privileges over the address book. This seems to work great. As long as I keep the Linux viewers as Read Only, they don't cause me any problems. Thanks again for all you (and team) do.
One idea I have been pondering for some time now is I would like to eventually move the self hosted remote utilities server to a virtual machine running within a Linux computer. I have a Linux computer that runs continuously that would be a good candidate for this project and maybe trying to switch the RU server to another computer, virtual or not, would reveal something about the original problem.