Community

« Back to Windows version

Problems switching RDP-Session

Page:

Go to last message

Links used in this discussion

Conrad Sallian, Support (Posts: 2953)

Jun 09, 2021 4:21:26 pm EDT

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.

Gaute Greipsland, User (Posts: 12)

Jun 09, 2021 6:23:53 pm EDT

Support level: Free or trial

My goal was to have a Wyse/Dell thin client connected to a Windows machine (XP/7/10/2008/2012/2016/2019) using RDP (Not "some kind of remote control software" - RDP!! TCP/UDP port 3389) , and when that user needs support I want to connect to the windows machine and connect to the same RDP session that the user is using, so we both see the same screen, move the mouse together and they can show what they did, and I can show what they should have done. This works with a lot of other Remote Control Software, but obviously not RU - according to themselves.

Gaute Greipsland, User (Posts: 12)

Jun 09, 2021 6:27:35 pm EDT

Support level: Free or trial

Michael Albright wrote:
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.

According to the answer I got - It is actually working as designed 1 out of 10 times, and some kind of bug allows you to connect 9 out of 10 times... ;)

Spooner Tech, User (Posts: 3)

Jun 10, 2021 8:00:35 am EDT

Support level: Pro

I really love this software, it meets many of the needs I have as a singular IT department for our company.

I had no idea the logs were in html, very easy to read through.

The first portion is the bit where it hangs at the map screen and i close and restart and it goes in. I know there is a setting about using "Legacy Capture Mode" which when I have time I'll test.

The additional lines would be my attempt at switching to the existing RDP session.

All of on-network internal clients are set as direct connect-type.

For this instance, I ended up connecting to the end-user laptop VIA Internet ID, that was being used to connect to our RD-Gateway and from there was able to assist them.
Logs Image attached

Conrad Sallian wrote:

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.

Attached Files

Spooner Tech, User (Posts: 3)

Jun 10, 2021 8:04:09 am EDT

Support level: Pro

Thank you for clearing that one up, I've been working with IT for 20+ years, and I would always specify the protocol rather than use RDP as a verb. I wasn't able to find much on the base for RU..I suspected a VNC scenario rather that it being the RDP protocol.

Conrad Sallian wrote:

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.

Thanks.

Submit a reply

Page:

Go to last message

^* Website time zone: America/New_York (UTC -4)