Pulse secure and zscaler client connector interoperability issue
I create a pulse secure role with split tunneling. When a start my windows 10 station zapp is automaticaly launch and i can acces internet. Then if i launch pukse secure client then i stop it, i can t acces internet anymore. All ie, chrome or firefox browsers can t access pac file on local proxy settings.
Re: Pulse secure and zscaler client connector interoperability issue
what about the Intranet traffic? are those working by connecting through the VPN tunnel?
what type of split tunnel configuration? IP based or FQDN? allow or deny?
Zapp should be sending traffic to the proxy server hosted on the cloud, correct? i am expecting the Zapp not to interfere with the pulse client traffic i.e. VPN server URL should be excluded from the application proxy config... if thats the case, why do we need to stop zapp after connecting to VPN?