Data Flows - Dual NIC setup

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Data Flows - Dual NIC setup

L1 Bithead

Hey All

 

I know that its not supported but before we rebuild our 4 connectors I'd like to try to get some clarity..

 

We have PrivCloud and its working fine with dual nics - typical "old-skool" implementation of 4 machines (2 per DC) setup with an inside and outside NIC.

 

Routing rules for windows is set that any non-private network traffic has outside as default interface and any private networks goes via the internal interface.

 

This seems to work well for all our PSM and SIA connections to RDP hosts, we have seen a couple of issues with when we close a HTML5 session via the VPN but that's an internal routing issue - works fine via hard line into the right VLAN.

 

We are now setting up SSH to our Linux estate and here's where the fun comes in..

 

It looks like the session is established on RDP to the connector (via the outside interface) and then rather than try to proxy/route via the internal interface its trying to go via the outside where there is no route..

 

I realise that everyone's going to come back with a "that's a big no-no, you've set it up wrong" but let me keep banging my head 😉 Can someone provide a nice simple flow diagram for how in detail the ssh connection is established from PrivCloud through both PIA and SIA

 

1 accepted solution

Accepted Solutions

L5 Sessionator

CyberArk PSM doesn't specify which NIC to use for the target connection. The only relevant configuration is reaching the PSM Server ID node configured in Privilege Cloud Web Portal > Administration > Configuration Options > Privileged Session Management > Configured PSM Servers > {Server ID} > Connection Details.

 

Which NIC the target connection will go through, once it reaches the Privilege Cloud Connector (PSM) is entirely handled by the Windows OS routing and may require Network/Microsoft assistance in determining why traffic is going through a particular NIC unexpectedly, based on the configuration.

 

The PSM-SSH Connection Component (CC) is the Out-of-Box (OOB) CC, which leverages a CyberArk modified PSMSSHClient.exe, based on PuTTy 0.81 (the executable will run under a PSM-12340000000000 Shadow User). If you want to replicate a connection directly from the PSM, download PuTTy 0.81 and runas an existing Shadow User (you will need to reset the local password for the Shadow User, then try connecting directly to the target using the vaulted username/address).

 

https://docs.cyberark.com/ispss-deployment/latest/en/content/privilege%20cloud/privcloud-sys-req-connector.htm#Networkrequirements

 

For SIA, End User connection is established to the SIA Gateway (CyberArk) > SIA Connector (Customer) > Target (Customer). You can replicate a connection by doing SSH directly from the SIA Connector server to the target, but once again this routing is done entirely by the OS.

 

https://docs.cyberark.com/ispss-deployment/latest/en/content/introduction/dpa_network-requirements.htm

View solution in original post

1 REPLY 1

L5 Sessionator

CyberArk PSM doesn't specify which NIC to use for the target connection. The only relevant configuration is reaching the PSM Server ID node configured in Privilege Cloud Web Portal > Administration > Configuration Options > Privileged Session Management > Configured PSM Servers > {Server ID} > Connection Details.

 

Which NIC the target connection will go through, once it reaches the Privilege Cloud Connector (PSM) is entirely handled by the Windows OS routing and may require Network/Microsoft assistance in determining why traffic is going through a particular NIC unexpectedly, based on the configuration.

 

The PSM-SSH Connection Component (CC) is the Out-of-Box (OOB) CC, which leverages a CyberArk modified PSMSSHClient.exe, based on PuTTy 0.81 (the executable will run under a PSM-12340000000000 Shadow User). If you want to replicate a connection directly from the PSM, download PuTTy 0.81 and runas an existing Shadow User (you will need to reset the local password for the Shadow User, then try connecting directly to the target using the vaulted username/address).

 

https://docs.cyberark.com/ispss-deployment/latest/en/content/privilege%20cloud/privcloud-sys-req-connector.htm#Networkrequirements

 

For SIA, End User connection is established to the SIA Gateway (CyberArk) > SIA Connector (Customer) > Target (Customer). You can replicate a connection by doing SSH directly from the SIA Connector server to the target, but once again this routing is done entirely by the OS.

 

https://docs.cyberark.com/ispss-deployment/latest/en/content/introduction/dpa_network-requirements.htm

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