RDP error in connection guidance

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

RDP error in connection guidance

L3 Networker

Field_Content_versions_oct20__068Vy00000N6hJgIAJ.pngWe have SIA set up recently to be used as html5 gateway from Privileged cloud portal.

This is working correctly,

Now, as another feature of SIA is connecting to the target either using vaulted creds or zero standing privileges. When I am putting the target details it is failing with standard RDP error:

Am i missing anything?

If i put in the RDP computer name as company_subdomain.rdp.cyberark.cloud, it does not connect at all. DPA is installed on one of our PSM servers already.

 

6 REPLIES 6

L3 Networker

Are we required to add another PSM gateway server in configuration options apart from ispssh5gw?

And put in there subdomain..rdp.cyberark.cloud?

L6 Presenter

There's no extra configuration needed in the Configured PSM Servers section of the Privilege Cloud portal for vaulted credential access through the SIA. As long as the SIA connector is up and running and the pool is defined properly with the relevant scope of targets, all you need is to have permissions to connect to the account through safe permissions.

 

Are you entering the right details in the required fields? The username, target address, and domain name should match the account in the Privilege Cloud portal.

 

As another check, are you able to connect to this account through PSM / HTML5 GW sessions from the Privilege Cloud portal?

Yes we are able to connect the account through HTML5 gateway from Privilege cloud portal.

Platform type is LDAP (and not windows domain platform), is Windows ldap platform supported by SIA?

 

Also, just for checking connectivity, i entered subdomain.rdp.cyberark.cloud in mstsc computer name and it doesn't move forward. At least gateway connection should be established .

While I haven't tested this myself, you can see in this section of the docs the types of accounts supported: https://docs.cyberark.com/ispss-access/latest/en/content/vm/acc-vm.htm#Virtualmachineaccessworkflow

 

Have you tried to connect to an account that's associated with either the Windows domain or Windows local account platforms? This will at least validate that your SIA connections are working as expected. We could make some inferences in that scenario.

L4 Transporter

Hi @Ankit Kumar​ 

 

As it seems @Tanishq Pandey​ provided an answer for your question, could you kindly share if this solution resolved your issue?

If so, could you please mark the answer as "Select as Best" to help other community members?

 

If the issue is still relevant, I would advise raising a ticket with our support team for further assistance.

 

Thank you, Liad

L1 Bithead

Hello,

 

I am facing the exact same issue. I am trying with Domain Account. Is there any solution for that?

  • 443 Views
  • 6 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!