1. You didn't accidentally pressed the Full Control / View toggle icon (it's the first icon on the toolbar in the Full Control mode). When it is pressed, you are in Full Control mode. When it isn't, you are in View only mode with mouse and keyboard not working.
2. Provided that #1 is not the case, does this happen all the time or do the keys work after you re-initiate the remote session?
It seems like the arrow keys issue occurs when tabs are disabled in Full Control mode (i.e. each session is in its own window). We managed to reproduce it and we'll be working to fix it in the nearest update. Thanks Larry.
Meanwhile, as a workaround the tabbed mode can be used. Sorry for any inconvenience :)
Yes, we understand. Although, it should be noted that it's unlikely that a signed executable is a huge factor that changes the attitude of antivirus programs towards programs they check. Normally, they have a whole lot of factors / parameters that they consider when they return their verdict.
Could you not embed the digital signature into the RUT licence key?
I'm not sure if it's a better way than creating online configurator, but I will add this idea to our idea bank anyway. Thanks! :)
Larry Gray wrote: One other thing to add about keyboard or remote control as a whole. At times I have several windows open and occasionally one of the remote hosts will timeout and go to login screen. I have to end the session and bring it back up in order to do any remote control. The "send ctrl-alt-del" function works, but then I can't type or click anything in the window unless I restart the session.
Is this happening in 100% of all cases or only in some cases?
Regarding the arrow keys bug - unfortunately, we couldn't reproduce it here. It certainly has something to do with a specific machine or configuration. Without remote access we won't be able to diagnose it. We could schedule a remote session, connect to your Viewer machine and from that machine connect to a remote machine using your Viewer and try to diagnose the issue.
john kumpf wrote: It was with your hosted service, the default. I dont have my own RU server running. And i have not tried this again since i posted so i dont have any more data on it. But thanks for looking into it.
That explains it. IPv6 doesn't work with our hosted service as of yet.