Connection Error- The target is not responding.

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

Connection Error- The target is not responding.

L2 Linker

Connection Error- The target is not responding. While connecting to windows target server using SIA with local account credentials.068Vy00000xQ2IlIAK.jpg

1 accepted solution

Accepted Solutions

L1 Bithead

Good afternoon,

 

In Session diagnostics, please check what is listed there. Please go to the connector page, then click on a connector in the pool the target exists in. From there, you can click test, and give it the FQDN. You'll be able to test ports. You can also attempt for testing purposes to turn off TLS certificate validation in SIA>Settings. From there, test again. It also appears that you didn't specify the FQDN in the connection string. Please ensure that you do that if this an on-prem resource. The fact that it can't create the tunnel is because you're not triggering an identifier.

 

Thanks,

 

Austin Suddarth

Sr. Solutions Engineer, PAM SME

SIA Experts Council - CyberArk

View solution in original post

12 REPLIES 12

Hey @Ganesh Uppari​ 

Did you add the target sets? also is it ZSP or Vaulted connection, it helps if you give more details from the session diagnostics.

L7 Applicator

I think there's a firewall or similar blocking the traffic .

 

If you go into the sia tab of identity you should be able to see the diagnostics from this session which will give more information .

Please find the error details from diagnostics.

Field_Content_versions_oct20__068Vy00000xPReBIAW.png068Vy00000xQKvbIAG.jpg

Yes that looks like server down or firewall/network routing is the cause .

Hello @Vamshi Nivas Dubbasi Sudarshan​ 

 

Target sets mean the identifiers, right? I am using Vaulted connection

Hello @Malcolm Murray​ ,

 

I tried to connect target server using RDP. It is working fine. But If I try to connect the target server using SIA. I am getting this error.

 

Note: The server is up. I have tested connection from Connector to target using test from connectors using RDP test that was success. But when I try to connect using SIA, I am getting the above error.

 

What firewall or network do I need to add?

 

Please help me with this.

Is there a firewall in the way that has been opened for rdp traffic ?

 

I saw a similar problem where there was content based firewall in the way and it had been set to allow rdp traffic . However sia isn't normal rdp traffic as its doing it slightly different as it is from unix .

 

But it will be something like that I expect .

 

Hello @Malcolm Murray​ 

 

Our Windows team is saying that VM’s are in same VNET’s and there is no communication issue.

But they were using the custom port for RDP. Upon request they opened the default port that is RDP 3389.

 

Please let me know if you need any details.

L4 Transporter

Hello @Ganesh Uppari​ 

 

This error seems to be related to TLS certification. Can you please try connecting to target without TLS certification validation?

L4 Transporter

Hello @Ganesh Uppari​ 

 

This error seems to be related to TLS certification. Can you please try connecting to target without TLS certification validation?

L4 Transporter

Hi @Ganesh Uppari​ 

 

Since several community members answered your question, could you kindly share if any of these solutions resolved your issue?

If so, could you please mark the appropriate answer as "Select as Best" to assist other community members.

 

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

 

Thank you,

Shaked

L1 Bithead

Good afternoon,

 

In Session diagnostics, please check what is listed there. Please go to the connector page, then click on a connector in the pool the target exists in. From there, you can click test, and give it the FQDN. You'll be able to test ports. You can also attempt for testing purposes to turn off TLS certificate validation in SIA>Settings. From there, test again. It also appears that you didn't specify the FQDN in the connection string. Please ensure that you do that if this an on-prem resource. The fact that it can't create the tunnel is because you're not triggering an identifier.

 

Thanks,

 

Austin Suddarth

Sr. Solutions Engineer, PAM SME

SIA Experts Council - CyberArk

  • 1 accepted solution
  • 298 Views
  • 12 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!