Using it as a Relay server, means that ALL traffic goes thru it?
Yes. RU Server is supposed to be a completely autonomous solution meant to replace our public servers for users who rather prefer to "go on their own". Besides, RU Server provides unique features not available in the public service, namely address book sync and authorization server.
In that case, that means that the fastest Internet conection will give me flawless performance on the Remote session?
Basically, yes. The closer your Viewers and Hosts are to the server, the better the performance should be. We recommend that you deploy the server on the Viewer side.
Don't hesitate to ask if you have other questions.
I can't have Viewer open all the time because I get too many "... is Online" pop ups. All connections are on broadband cable with no known network issues. Happens to different users. Popped up 3 times in the few minutes I've been drafting this message so far. (Probably over 10 popups during the rest of this drafting).
Make sure that you have version 220.127.116.11 installed on both ends (Viewer and Host). What you describe looks like an older issue (v 6.6 etc.).
The Last IP doesn't show the last IP that the user used, or were NAT'd behind. My best guess is that its one of your relay servers, but I don't know why you'd have a column dedicated to that when the last seen IP of the user would be more more useful.
Your guess is right. Actually this column was more intended for direct connection, rather than for Internet-ID connection. Still we already have this suggestion on our wish list and will soon make the IP address information to traverse through the server to the Viewer from Host and vice versa.
So now I think I should look into self-hosted to avoid this relay bounce.
This is a good idea. However reliable our public service is, your own self-hosted server will always win simply because you fully control its configuration (for your custom needs, such as ports etc.) and also because it may be located close to you which will significantly reduce the distance and number of hops the IP packets should travel.
For one Win10 machine, logging into it is SOOOOO slow. So many times I would get failed logins because the time between typing the password and the character registering in the windows 10 login box would be in SECONDS. No change after at least 3 version updates. You just can't work on lag that I haven't experienced since 1998.
The default screen size/ratio needs to be changed more often then not. With TV, I never have to mess with scaling, I just maximize the window or I snap to half screen. No needing to scroll vertical or horizontal bars by default except with Remote Utilities.
When you first connect to a remote computer the default value is "Normal", not "Stretched". However, if you change that value for a specific connection in your address book or on the fly during a session, the program will remember this setting for that specific connection/remote PC.
Also, you can set default connection properties that will be used for all newly created connections. In the Modes section you can set the View mode to your liking. Learn more about default connection properties on this page.
If I don't experience really laggy logins, I still experience laggy mouse movements. Was so frustrated when I had to use it today. I don't think that PC had a password set, so I don't know if that had the really laggy login and might just be same as issue 3 above.
Please, refer to what I said about performance and using the self-hosted server. Also, for the last couple of weeks we have implemented some fixes to our server software as well that should reduce the number of such issues. Finally, the upcoming version 6.9 is going to be more optimized in this respect so it should be faster both during the initial connection (authorization) and subsequent remote session (data transfer).
6. In previous versions, remote access broke by Windows updates, I believe. Requiring re-installation and manual intervention and lost headless access. But I'm guessing that was a hard lesson learned and will be prevented from happening again by installing the software in the appropriate places from now on.
This used to be a problem a few updates ago.
We are going to release version 6.9 very soon so stay tuned. Given some serious updates in this version we are going to run open beta testing first available for everyone.