I was guessing it could be some missing port forward, is TCP 5655 enough?? No more ports needed??
Yes, this is the default communication port. There is also an administration port but it's only used if you are using the Admin console on the computer and the actual running service on another computer, which is seldom a scenario. Here is more information about RU Server ports https://www.remoteutilities.com/support/docs/ports-used-by-ruserver/
But after Matt's workaround, I think this is not the core of problem.. I also assume you're testing it on LAN, I'm trying to make it work on the internet
Yes, we would still want to get to the root of the problem and fix it if possible. Could you please do the following:
0. Make sure that you installed the latest server version. As of this writing it's version 126.96.36.199.
1. Create several books on your server (or just re-use the ones from your previous test if there's no confidential information in them).
2. Reproduce the problem.
3. Copy all the books from the server - they are stored in C:\Program Files (x86)\Remote Utilities - Server\data\ as xml files.
4. Export the registry entry HKEY_LOCAL_MACHINE\SOFTWARE\Usoris\Remote Utilities\MiniInternetId
Zip the books and the reg file and send them to us to firstname.lastname@example.org . We will examine the files and see if they can give us a clue.
I mean: I can give you access to my 'server' (Win10) if you want to try the 'buggy' configuration, we have TCP 5655 and 3389 (RDP) forwarded. Directory structure and users can be deleted as well as two saved test connections..
No need for remote access for now, let's see if we can figure out the problem from the files above.