Pauline's community posts

Hello William,

Thank you for your message.

Please note that we’ve responded to another thread you’ve created in order to avoid duplication.

Hope that helps.

Hello William,

Thank you for your message.

Please note that RDP is a Microsoft-native solution and Remote Utilities have no control over how exactly it functions. The RDP connection mode that you can see in Remote Utilities Viewer simply runs the Microsoft's RDP client, nothing more.

Here's how you can change the RDP resolution and preserve it every time you connect to a remote Host using RDP:

1. First please make sure to delete all .rdp files from the %appdata%\Remote Utilities Files\rdp_connections folder. In addition, please note, that we do not recommend manually modifying any of the .rdp files.
2. Right-click on the connection in the address book and select Properties.
3. Navigate to the RDP tab and click Configure. This will open the native Microsoft RDC client.
4. Click Show Options, navigate to the Display tab and select the preferred resolution.
5. Get back to the General tab of the RDP window and press Save.
6. Important: Make sure to close the RDC window (do not press "Connect") and click OK in the connection properties window - this will save your connection properties for RDP within Remote Utilities, so that the resolution stays the same every time you use the RDP mode.

Hope that helps.

Hi David,

Thank you for your message.

This is to inform you that we’ve received your ticket and replied to it to avoid duplication. I’m submitting the issue to our development team for a review and will keep you updated.

Thank you.

Hello John,

Thank you for your message.

Yes, this issue definitely can be caused by the graphics card changes. What we can recommend here is to enable the Use Legacy Capture Mode feature if you haven't done so yet or use a HDMI dummy plug in adapter - this is what tends to help with similar issues related to headless Host machines.

Let us know if you have more questions.

Hi Robert,

Thank you for your message.

I’m glad to hear you were able to figure out the issue and it works for you!  Please feel free to let us know if you have any questions or need our assistance.

Thank you.

Hello Tony,

Thank you for your message.

Have you already tried enabling the Use legacy capture mode as described in this guide? If you haven’t done so yet, please try enabling it and see if this helps to resolve the issue.

Hope that helps.

Hello,

Thank you for your message.

It seems that the issue might be caused by a mismatch in the Kerberos authentication process due to the following factors:
1.  Different Domains: since the Viewer PC and the hosts are in separate domains, Kerberos requires proper cross-domain trust to authenticate. If there's no trust relationship between the two domains, authentication will fail.  Please try verifying if the domains have a two-way trust configured. If not, set up the required trust relationship or ensure both systems are in the same domain for Kerberos to work.

2. Time Synchronization: Kerberos authentication is sensitive to time discrepancies. If the clocks between the Viewer PC, Host PC, the self-hosted RU Server, and the domain controllers are not in sync, it will fail.  Please double-check to ensure all machines are synchronized to the same NTP server.

3. Password Incorrect Error: The error suggests authentication attempts with invalid credentials. Ensure:  
 - The correct username/password is used.  
 - The account has not been locked out due to failed attempts.  
 - The account being used has permission to authenticate against the target system.

4. Last but not least, fallback to NTLM: since NTLM is disabled, any fallback attempts by Remote Utilities will fail if Kerberos isn’t configured correctly. Ensure Kerberos is the only supported and functional authentication protocol.

Finally, double-check the Connection Properties -> Security to ensure Kerberos authentication is properly enabled and configured.

Hope this helps!

Hello Alan,

Thank you for your message.

Thank you for sharing your thoughts! You can disable clipboard capture directly in the Host Settings under Other settings. Here’s the link to the relevant instructions for more details.

Regarding your suggestion for easier access to this setting, we really appreciate your feedback. I will forward this to our development team to see if improvements can be made in future updates.  

Hope that helps.

Hi Keith,

I’m glad to hear you were able to find a workaround and it works for you now!
You can also save the configuration settings for your RDP connection - you just need to close the RDP window after applying changes (instead of clicking Connect and click Save in the connection properties window - this should save the setting for the next time you initiate the connection.

Hope that helps.

Hello Keith,

Thank you for your message.

Have you already tried enabling the Use legacy capture mode feature to see if it helps to resolve the issue? If you haven’t done so yet, please try enabling it following this guide and see if this helps with the issue.

Let us know if this works for you or if the issue persists.