Endpoint with Netskope Private APP Client and VPN Client installed endpoint
Hello, good afternoon, as always, thanks for the support and for your constant collaboration.
I have a question regarding the following environment/particular case.
-Workstation/Laptop, outside the network/DC (Internet modem 4g/5g - Home Internet connection - Connection from Cafe) with Netskope Client installed and with VPN Client installed and Connected to the datacenter, bound for 10.10. 10.100 (App1) 10.10.10.200 (App2) 10.10.10.250 (App3).
-Tenant Netskope with NPA Private Access (policies, access, configurations already fully done)
-Publisher in Datacenter and fully connected
-Publisher NPA Private Access/Private Apps destinations: with IP of internal access systems: that is, App1:10.10.10.100 - App2:10.10.10.200 - App3: 10.10.10.250
My question is the following, with the environment already described, what happens in the case of the workstation with the VPN client connected, with the Netskope client installed, where both the VPN client has access to the 3 App1-3 as well as the Netskope NPA Private Access client. In this particular case, what prevails, which traffic is prioritized, which traffic has preference, which type of connection will be established when the workstation/endpoint connects or tries to establish a connection to any of the aforementioned APPs? Would you prefer the access you have through the Netskope Private Access Client or would you prefer the access through the VPN client?
Thank you, I am attentive to your comments, details, observations, suggestions, etc.
This ultimately depends on the exact remote access VPN that is installed and how it intercepts traffic. In broader cases where the app is defined by hostname, NPA usually intercepts first by replying with a stub IP address that the client automatically intercepts. In your specific case, since it's defined by IP address, it's going to depend on how the VPN client operates and the operating system (driver level, proxy, system extension, etc). One other note, while it is supported to run the Netskope client with Private Access enabled at the same time as a VPN client, most enterprises end up replacing their traditional VPN client with Netskope Private Access. I hope this helps but if there's a specific client for VPN you are interested in understanding the interoperability, I'd be happy to do some additional digging.
Hello, good afternoon, thank you very much for your prompt response and support.
If precisely the applications are only accessible via IP, not with FQDN or Hostname, they are somewhat legacy applications.
Yes, I understand that once NPA Private Access is used, I understand that normally the traditional VPN client should no longer be used, however, under a "transition" period, both solutions may operate, and both may be useful for operational continuity.
Now with respect to the mode, client and vendor, it would be the following scheme.
Palo Alto Networks Global Protect Client Version 5.2.
and Fortinet FortiClient version 6.4.X.
Both in split tunnel mode, where only passes through the VPN tunnel the traffic destined for internal resources, networks and in this case the app discussed in the beginning of the post, the traffic to the Internet, goes directly from the client/endpoint and its connection to local internet, cafe, home, public, home, etc, etc .... Not through the VPN concentrator and then to the Internet, but direct to the Internet, the VPN only for access to local networks and internal resources.
Thank you very much for your support
I remain very attentive to your comments.
Good morning @MetgatzNK,
My apologies for the delay. After some additional research, Netskope doesn't support running a remote access VPN client at the same time as Netskope Private Access. This is because the respective drivers/services will likely fight over traffic depending on the specific VPN client. If there's a specific use case you're looking to solve for, please let me know. Keep in mind, there is a feature in Netskope Private Access to allow users to enable and disable the tunnel from the client:
This would allow you to alternate between the remote access VPN and Netskope Private Access as needed.
Hello @sshiflett Good afternoon
A ok, thank you for your answer and for confirming it.
Now thinking in an environment, in an implementation that requires "transition" stages from VPN client access to private access then to Netskope Private access, how do you handle it or how have you handled it in that case ?
Since if you do not support VPN client, in parallel, it means is a complete cutover from VPN access and then via Netskope Private Access Apps.
There is no middle ground then that Netskope can offer thinking that I am connected with my VPN client to access certain services, while in parallel I have Netskope Client to test and validate access to certain private applications via Private Access ZTNA.
I remain attentive
In order to view this content, you will need to sign in to your account. Simply click the "Sign In" button belowSign In