Getting error E-9999 while trying to connect to a Windows host using vaulted credentials

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

Getting error E-9999 while trying to connect to a Windows host using vaulted credentials

L3 Networker

Hi,

 

We are using the SIA infrastructure to connect to Windows workload with Vaulted Credentials. We are not able to connect to any of our host and we are getting a very generic error E-9999. Looking at the SIA session diagnostics it is reported in error while the details do not show any error ! Very strange session diagnotics.

 

CyberArk support is engaged but they do not answer and do not provide any solution.

 

I checked SIA servers and the traffic from them to the target hosts on port 3389 is allowed.

 

How can identify what is the issue?

 

Guidance appreciated.

1 accepted solution

Accepted Solutions

L3 Networker

Finally I was able to make a first connection via SIA on our first Window Domain join server.

 

This is what I have done:

 

To solve E-9999: needed to add the network name even optional in the connection string

To solve E-1003: certificate matching SIA on the target server was missing. Switch to another server using one. All servers that you want to connect to should have a certificate from the same CA authority that is installed in the SIA. Some of our servers were running a self-signed only.

To solve E-1006: this is due because the account I was using is member of the "protected group". Please note that CyberArk SIA does not support it. You should exclude the account from this AD protected group.

 

 

 

 

 

View solution in original post

9 REPLIES 9

L7 Applicator

Edit: Updated from E-9999 to E-1005

Are you using a vpn or similar?

 

If the ip address changes from when the rdp is signed by PVWA and it is run, then an e-1005 (originally incorrectly said E-9999) error will occur.

 

There's a fix Cyberark can give you which will patch a config file via rest.

But I prefer not to give it as they should.

 

Log a case and see what happens

 

L2 Linker

Take a look at the session diagnostics.

I have found that putting in the network name helps (even if it is just default_network).

Can you advise what the error in session diagnostics is?

Problem is the same from the office network or from home office using the VPN always ending E-9999.

HTML 5 gateway work well

Seems your recommendation to put the "network name" even optional field is moving the things forward.

I have now a bit more of tangible session diagnostics details. It is now ending with error E-1003 that sounds the target server does not have a proper certificate to validate the request incoming from SIA servers.

To test the theory, you can remove the TLS certificate verification in the settings of SIA.

This is not recommended to leave in production, but rather just to test if it is indeed the certificate.

I have again progress but now another error.

 

To solve E-9999: needed to add the network name event optionnal in the connection string

To solve E-1003: certificate matching SIA on the target server was missing. Switch to another server using one

 

Now I have the error E-1006

There may be an error in the way the connection or account is configured.

Client error message

Unable to connect using vaulted credentials

 

Connecting via HTML 5 gateway with the same account is ok on the target host

L7 Applicator

Checked my notes.

E-9999

Ip address used and no network specified.

Invalid host name

 

Which platform are you using? Only a few are supported.

 

"Configure the Privilege Cloud Portal to support SIA access This section describes the configuration steps for supporting SIA access to remote targets from the Privilege Cloud Portal. This option is supported for the following platforms:   

Windows Desktop Local Accounts  

 Windows Domain Account   

Windows Server Local Accounts"

 

You'll get an e-1006 for example if trying to connect using the windows ldap domain platform.

Hi, did you find a solution for this? I have the same problem since monday

L3 Networker

Finally I was able to make a first connection via SIA on our first Window Domain join server.

 

This is what I have done:

 

To solve E-9999: needed to add the network name even optional in the connection string

To solve E-1003: certificate matching SIA on the target server was missing. Switch to another server using one. All servers that you want to connect to should have a certificate from the same CA authority that is installed in the SIA. Some of our servers were running a self-signed only.

To solve E-1006: this is due because the account I was using is member of the "protected group". Please note that CyberArk SIA does not support it. You should exclude the account from this AD protected group.

 

 

 

 

 

  • 1 accepted solution
  • 366 Views
  • 9 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!