Conrad Sallian's community posts

Hello Brad,

Have you tried to restart the remote machine?

Hi Gregg,

Yes, most likely it will.

Hello Derek,

I'm glad to see you figured out the issue. Let us know if you need any assistance in the future.

Thanks.

Hi Justin,

Unfortunately, we couldn't reproduce the issue. Please, try the following:

1. Completely uninstall Host (including removing it's related folders and registry entries) as described here.

2. Restart the machine.

3. Install the Host. Make sure that you have full admnistrative privileges. Also, make sure you don't change the default installation locations.

Hope that helps.

Hello Frank,

We need to take a look at the log files to better diagnose the issue. Feel free to send us the Host log files to [email protected] .

Here is how to locate the logs https://www.remoteutilities.com/support/docs/host-log/

Hello,

Unfortunately, we couldn't reproduce the issue. Could you tell us what additional options in the Execute mode window you enable/use?

Hi John,

Sorry, forgot to update you on the status yesterday. MalwareBytes promised that the issue would be fixed in the next update. Here is the related forum thread.

Hi Michael,

The response from the Dev's seems like an easy (lazy) answer, but I couldn't say what the "Full Control" connection is actually using, assuming it's NOT just RDP.

The Full Control mode is Remote Utilities's own connection mode that allows you to view the remote screen, manipulate the mouse cursor and send keystrokes.

RDP is Microsoft's technology and the acompanying software (Remote Desktop Services) that does the same.

The RDP mode that you can see in Remote Utilities Viewer simply runs the Microsoft's RDP client, nothing more. This has been added long ago for convenience - many admins prefer using RDP in many situations even if they have an RU license.

It should be noted that sometimes people use the word 'rdp' (as a verb) even if they don't actually use RDP (the technology). They may say that they 'rdp to a remote computer' meaning that they are actually using whatever remote control software they have at that moment, including Remote Utilities' Full Control mode. That may produce some confusion.

I found this post as I now have 3 Pro licenses and was researching why 1 out of 10 times it won't let me connect to the session when I connect in "Full Control" mode.

We should examine the Host logs to tell why this might be happeing. This can be as well a network/connectivity issue which has nothing to do with terminal sessions.

Thanks.

Hello Pathompong,

Unfortunately, our trial period only lasts 30 days. I'm sorry for that.

Hi John,

Although if this is related, how can it be that I have no problems to connect to the laptop that works fine, yet connecting to the desktop PC is unworkably slow and with both having an Internet-ID connection?

If this is about Full Control and/or View only mode it could be something with screen capture on that machine. For example, outdated graphics card driver.

There is a simple test. Try connecting to both machines not in the Full Control mode, but in the File Transfer mode. And check how fast the remote folders open, files are transferred etc. I'm sure you won't notice any difference as compared with the laptop.

Also, you can try enabling the "Use legacy capture mode" option. It's in the Other tab of the Host settings.

Both these hosts have access to a router directly on optic fibber internet connection (10,000mbps) both are in the same room and both using the same internet. The only difference is one is a laptop and the other a desktop PC. Any ideas why that would be?

Most certainly network has nothing to do with it. It's in graphics/CPU part where the issue lies.