PSM - RDP slow connection

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PSM - RDP slow connection

L1 Bithead

Good day,

We implemented Privilege Cloud solution for a costumer and we decided to deploy 2 Connector Server. All the communication works fine but I have performance issue with one of the Connector Server.

When I tried to use the first Connector Server as PSM server for a platform and test an RDP Connection (Connect button), the solution takes almost 1 minutes in order to start the Proxy Session.

This behavior not happen with the second Connector Server where, if I click in the RDP file downloaded from the web page, the connection to the target system and the start of the proxy session is immediate.

 

The normal RDP connection to both Connector Server not have any problem (I tried to do a simple RDP in both the machines and the connection start immediately).

I also enable the trace and I notice a step that required a lot of time in the first connector.

 

First Connector (slow RDP connection issue):

 

[08/11/2021 | 15:11:22.315273] | {pid= 6708} | {tid=   2648} | class CPSMConnectionRequestHandler * | PSM\(407)                          | :: | PSMSR964I The [DisableMapLocalDrives] RDS setting value received from session token is [true].

[08/11/2021 | 15:12:06.531475] | {pid= 6708} | {tid=   2648} | class CPSMSessionIdSynchronizer *  | PSM\(599)                          | :: | PSMSR978I The session id was successfully registered and will be allowed to logon. (Session UUID: 498e5cb0-de7a-4b3b-8f5b-0febec8a96ab, Session Id: 10).

 

Second Connector (normal RDP connection):

 

[08/11/2021 | 15:16:18.110204] | {pid= 6100} | {tid=  11352} | class CPSMConnectionRequestHandler * | PSM\(407)                          | :: | PSMSR964I The [DisableMapLocalDrives] RDS setting value received from session token is [true].

[08/11/2021 | 15:16:18.171269] | {pid= 6100} | {tid=  11352} | class CPSMSessionIdSynchronizer *  | PSM\(599)                          | :: | PSMSR978I The session id was successfully registered and will be allowed to logon. (Session UUID: 3019126f-954d-4c88-85e0-bf470a966b2d, Session Id: 122).

 

It's seems that the problem is between the CPSMConnectionRequestHandler step and the CPSMSessionIdSynchronizer that required almost one minute.

 

Do you have some experience about this issue? How do you resolve that?

 

Regards,

Andrea Gimmelli

3 REPLIES 3

L4 Transporter

sounds like something with the Trusted Root Cert lookup or similar issues...

 

You can try this KB article: https://community.cyberark.com/s/article/00003575

or that:

On the PSM "Turn off Automatic Root Certificate Update"

GPO: Computer / Administrative Templates / System / Internet Communication Management / Internet Communication Settings / Turn off Automatic Root Certificate Update

> Set to "Enabled"

L3 Networker

I am facing the same issues as well but the slowness started very recently and we didn't make any changes on the PSM Servers. I can try the solution suggested in Article but can that be applied in Prod environment ?

L1 Bithead

good day,

In my case the problem was an incorrect configuration of the network adapter DNS in the connector server 1. We didn't notice immediately because the connector server is in domain and the connection with AD account works without problem but doing an "nslookup" we notice that other machine could resolve the FQDN of the connector server 2 but not the connector server 1.

 

Regards,

Andrea Gimmelli

  • 1318 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!