Conrad Sallian's community posts
Connection issue
If there multiple terminal sessions (i.e. there is a terminal server running on the remote PC) then you can switch to a specific session. However, even in that case you'll still connect to the console session first and have to use a terminal session switch icon on the Full Control mode toolbar.Dmitri wrote:
Ok, fixed, I had to add users who is enabled to login.
And now question - despite of security mode - viewer always connects to currently active user account...
Is there any way to connect viewer to specific user account? Not to the active one?
Please, note that it's only the existing terminal sessions that you can connect to. Remote Utilities cannot create terminal sessions for you, i.e. it cannot act as a terminal server itself.
Connection issue
If you can connect from another Viewer then the Host is ok, and the issue may have been on the Viewer side, not the Host's.
In this case a corporate/perimeter firewall is often to blame. You might have certain outbound ports blocked on the corporate firewall level. You need to make sure they are open and that our relay server is accessible. This documentation can help:
https://www.remoteutilities.com/support/docs/ports-used-by-remote-utilities/#public
Let me know if you figure out the cause for the issue. Thanks.
Connection issue
Thank you for your message.
Could you please clarify if this is through Remote Utilities or you mean something else?Host setup is OK - I have no any issues to connect to this host from another computer (located in a different place).
Looking forward to your reply.
[Resolved] Linux Server
An RU Server for Linux is certainly on our wish list. Perhaps, even with limited functionality at first, like for example with relay capabilities only.
As for your offer, thank you very much. I'm not sure though it is possible because the source code is proprietary and not to be published or otherwise distributed. But thank you anyway!
Android App Comments
Thank you for your message.
Sorry for the inconvenience. We are planning on updating the mobile client in a few months - it will be completely revamped, with new full-fledged address book, a new connection mode (at least Power Control) and a few more important features. We will make sure that the cursor issue is also fixed.
Don't hesitate to ask me if you have other questions.
Detect remote connection
WinNT security functionality failure - viewer can no longer long on
WinNT security functionality failure - viewer can no longer long on
Thank you for your report. It has been forwarded to our engineers for testing and examination. Since we cannot exactly reproduce your environment here, perhaps your help would be needed for us to diagnose the cause of the issue. I'll get back to you soon with clarifying questions.
Thank you.
Version 6.5 BETA
Hello Keith,Keith Hay wrote:
Is there any specific reason that the remote screen response is significantly slower with Windows 10. I was hoping that the Beta would help improve the response time. It is particularily noticeable on any type of Win10 "system" screen/dialogs such as the login or lock screens. For example, It fairly consistently takes 20-30 seconds for the lock screen to respond to a mouse click or enter key. Once your in an application( e.g. MSWord) it seems to get better, but response is still a little more laggy than Win7 was. We're seeing this on multiple hosts and clients, even when accessing on fullspeed cable internet. We're running via internet-id using the free id server. We've already hit the common spots by dropping the color depth to 8 bits, and turning off Aero, and removing wallpaper. Its almost like Win10 does some type of "mode switch" when display system dialogs that causes huge delay..
Anyone else seeing this type of performance anomally or have further suggestions?
Keith
Could you try to enable "Use legacy capture mode" in the Host settings (Settings for Host -> Options) on one of the Hosts, and see if there is any difference with other Hosts, preferably its peers on the same network.
Looking forward to your reply.