Pulse Secure V.9.0.3 B1599 and macOS Mojave - Status: Waiting to connect - up to 1-2 minute(s)

[chrrac]

Both features are not used by checking Users, Pulse Secure Client Connections.
Always-on Pulse client - Value is untagged. VPN only access - Value is untagged.

I am facing 1-2 minute(s) waiting to connect with Pulse Secure Desktop Client-9.0R3.2 Software (Build 1667) and Client-9.0R3.3 Software (Build 1667). I have installed Pulse Secure Desktop Client-9.0R4 Software (Build 1731) today, maybe it behaves differently.

[zanyterp]

can you also check traffic enforcement at users>user roles>rolename>vpn tunneling?

[chrrac]

users>user roles>rolename>vpn tunneling ... yes, this is tagged and being used.

[[email protected]]

Under the VPN tunneling settings, please check if "Traffic Enforcement" option enabled for IPv4/IPv6.

[chrrac]

users>user roles>rolename>vpn tunneling>options>traffic enforcement ... yes, IPv4 is tagged and being used. IPv6 is untagged.

[zanyterp]

thank you for confirming that this feature is enabled, @chrrac. can you disable this, uninstall Pulse, reboot, and test again, please?

[chrrac]

I disabled traffic enforcement for IPv4 for a specific group of "users" and will let you know outcome.

users>user roles>rolename>vpn tunneling>options>traffic enforcement ... Disabled, IPv4 and IPv6 are untagged

[zanyterp]

thank you

[chrrac]

Since i disabled (untagged) traffic enforcement for a specific group of "users" the reconnection works fine for them using Pulse Secure V.9.0.3 1667 (we got rid of V.9.0.3 B1599 a couple of weeks ago).

It looks promising. I disabled traffic enforcement for IPv4 for ALL "users" today and will let you know outcome.

users>user roles>rolename>vpn tunneling>options>traffic enforcement ... Disabled, IPv4 and IPv6 are untagged

[zanyterp]

thank you for the update, @chrrac