- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
09-10-2024 09:26 PM
I had setup the DPA connector on-prem together with other connector like PSM,CPM, assign in correct pool, and added the endpoints identified for both dpa host and client machine, but still received this error
Details error:
Failed to create a secure tunnel
Error code: ErrorCode.DPA_CREATE_TUNNEL_NO_ACTIVE_CONNECTOR_AVAILABLE
Error description: No active connector found for network: ON-PREMISE
Error message: There are no active connectors available. Contact your system administrator.
09-10-2024 11:03 PM
This error generally points to no connector targets being matched against your pool. Could you confirm once again that the connector pool has the required entries? Are you using IPs, hostnames, or FQDNs for those entries?
09-10-2024 11:21 PM
yes, I had insert both the hostnames of the client and host in the pools.
How can I defined the IPs? The documentation pointed there are IP can be input but IPs is not in my endpoint identifiers selection.
09-12-2024 11:46 PM
Hi
I did confirm the DPA connector is up. However, it still mentioned the same error when I click on the "connect" in the privilege cloud portal.
I had also try added the host into the host file to make sure the connector server able to resolve the server I try to connect.
One more things to confirm, my DPA connector is not domain joined, but my target server is domain joined, would this impact ?
FYI, PSM is working fine when connect through RDP.
09-18-2024 01:03 AM
Hi,
Check endpoint identifiers in the DPA Connector pool, if you added FQDN and its value as *.domain.com.
Then you need to use the target server address as FQDN in the connection guidance. If you use netbios or hostname, you may face this error.
09-25-2024 12:47 AM
Hello @Wei Jing Ng
Since several community members answered your question, could you kindly share if any of these solutions resolved your issue?
If so, please mark the appropriate answer as "Select as Best" to assist other community members.
Thank you,
Liad
12-09-2024 12:39 AM
I had the same issue and the solution was not clear, but using the tip from @Rajasekar Natarajan , I finally worked out what I needed to do. Here's a summary of my scenario and the fix for it.
In Connector Management, go to "Connector Pools" and edit the pool.
Under the Endpoint identifiers, I only had the FQDN of the domain in there ( i.e. *.domain.com)
When you click the option to "Select endpoint type", there are only 2 options for All connections - "FQDN" and "Hostname". To fix the issue, I had to add the local IP addresses of each of the connector servers (I have 2), but as a FQDN. Even though it says to type a Full FQDN Domain, I just typed the IP adress of the connector, then clicked Add, then "Done" once both were added.
03-06-2025 08:32 AM
Connector Management, go to "Connector Pools" and edit the pool.
Under the Endpoint identifiers,
When you click the option to "Select endpoint type", there are only 2 options for All connections - "FQDN" and "Hostname".
THEN IF YOU IN DOMAIN.
07-30-2025 03:32 AM
That's worked for me as well, thanks!
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!

