Failure Connectivity for Port 1858 - VaultConenctivity FAILED

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

Failure Connectivity for Port 1858 - VaultConenctivity FAILED

L2 Linker

Please see the configuration in my Windows Server for the Privilege Connector.

The firewall is turned OFF.

Inbound Traffic - Local Port 1858 ALLOWED

Outbound Traffic - Remote Port 1858 ALLOWED

With internet access

 

but I still encountered a Network Connectivity Error, which failed for Vault Connectivity.

I don't have any errors encountered for port 443, only in port 1858.

Already did Test-NetConnection in PowerShell, Ping succeeded: FALSE

 

Kindly help me where should I check next? Why is there always an error connecting to 1858?

 

14 REPLIES 14

L2 Linker

probably routing issue

L7 Applicator

Hi @RR Anthony Alca​ 

 

Please use ‘Tracert’ command to confirm if packets are being routed correctly.

 

tracert <Vault IP>

 

Look for timeout error.

 

Also please ensure the Vault is actively listening on port 1858.

 

netstat -ano | findstr :1858

 

Please involve your network team to investigate network restrictions.

 

Hope it helps !

L7 Applicator

It is likely a firewall causing this. Speak to your networks team to help diagnose and resolve

 

I'll check on this. Thank you!

I'll check on this. Thank you!

 

L2 Linker

One key thing to note is that as many have already advised this is likely a gateway firewall change that is needed as port 1858 is not a standard port. Please also note that all traffic from P-Cloud connectors is outbound so exposing your system for inbound also is a risk please follow the pre-requisites and also consider using the connector management pre-req script for a unified single tool that will test your readiness for deployment of the cloud connector

I was informed that my test lab has no blockings (in ports). I tried only allowing port 1858 to the outbound and both inbound and outbound but I still got the same result.

 

RTO when pinging the vault.

Field_Content_versions_oct20__068Vy00000GMWZWIA5.png

L2 Linker

I would say in this instance it may be worth having a call with your network team and also checking have you whitelisted the public ip from your test lab. this does certainly seem to be something local.

 

If you have persistent errors please consider raising a support ticket

L2 Linker

Is that Privilege Cloud Standard or ISPSS?

Does it happen on all of your connectors or just one of them?

L1 Bithead

Hi, I am also facing this issue. Same as you only 1858 bas reachability issue.

 

Did you get a resolution for this?

L4 Transporter

Let me help you troubleshoot this. in order to work with vault

1- Enable the windows firewall- it should be up all the time

 

oprn the powershell as administrator on vault server

 

and run the following

get-netconnectionprofile

 

note down the name of the connection --- it could be network 1 or 2

 

next run below command

 

set-netconnectionprofile -name "<name you noted down>" -Networkcategory Private

L4 Transporter

Let me help you troubleshoot this. in order to work with vault

1- Enable the windows firewall- it should be up all the time

 

oprn the powershell as administrator on vault server

 

and run the following

get-netconnectionprofile

 

note down the name of the connection --- it could be network 1 or 2

 

next run below command

 

set-netconnectionprofile -name "<name you noted down>" -Networkcategory Private

do this

 

Let me help you troubleshoot this. in order to work with vault

1- Enable the windows firewall- it should be up all the time

 

oprn the powershell as administrator on vault server

 

and run the following

get-netconnectionprofile

 

note down the name of the connection --- it could be network 1 or 2

 

next run below command

 

set-netconnectionprofile -name "<name you noted down>" -Networkcategory Private

do this

 

Let me help you troubleshoot this. in order to work with vault

1- Enable the windows firewall- it should be up all the time

 

oprn the powershell as administrator on vault server

 

and run the following

get-netconnectionprofile

 

note down the name of the connection --- it could be network 1 or 2

 

next run below command

 

set-netconnectionprofile -name "<name you noted down>" -Networkcategory Private

  • 836 Views
  • 14 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!