It appears when switching from Z-Tunnel 2.0 to 1.0 or to disable ZIA completely, it fails and only likes when it remains on Z-Tunnel 1.0 throughout the connection.

tried Tunnel with Local Proxy for VPN Trusted Network - fails.

added the DNS domain of the 3rd party to the DNS search suffix so it’s detected as VPN Trusted Network and set to None (disabled) - fails.

added the DNS domain of the 3rd party to the DNS search suffix so it drops down to Tunnel 1.0 - fails.

The VPN destination is in the App PAC, Fwd PAC, VPN Gateway Bypass and still fails. Off Trusted Network: Same as On Trusted Network blades Junos Pulse Secure Access Service (SA) Junos Pulse Access.VPN Trusted Network: Same as On Trusted Network.Tunnel Driver Type: Packet Filter Based.Our app is now available on Google Play About Us F.A.Q. Please, tick the box below to get your link: Print manual. The connection is not established fully and both Pulse Secure and ZCC go into Connecting and Connected state. Juniper MAG6611 Junos Pulse Gateway w/2x Secure Access Blade 160 MAG-SM160Here is a used Juniper MAG-6611Junos Pulse Gateway chassis populated with 2. This manual is also suitable for: Junos pulse mag4610, Junos pulse mag4611, Junos pulse mag6610, Junos pulse mag6611. Everything works in Tunnel 1.0 configuration but we are making a move to Tunnel 2.0 where it fails to function. We have a number of users that use Pulse Secure VPN client to connect to a 3rd party, which is configured in Full Tunnel mode.

Junos pulse gateway