which I can't post to because I get a post-flooding error.
Mod [email protected] advised this requires a NAT connection with the VM.
I've setup my VM (ubuntu) in hyperv with NAT networking following instructions here:
and here: https://serverfault.com/a/911587
But when Pulse Secure connects, I can no longer connect to the NAT router (my host laptop). Ping no longer responds in either direction. VPN is working fine on the Windows host laptop, the new NIC appeas on it: Pulse Secure - Juniper Networks Virtual Adapter, and connectivity to remote hosts works fine on it. The VM's NAT nic remains up, has an IP assigned, and can ping itself, but can no longer ping the host.
A similar setup works fine in virtualbox by following guidance here: https://www.virtualbox.org/manual/ch06.html#network_nat_service
No mention of Enforcement in any pulseclient.logs. Are you thinking this ability has been disallowed by admin policy? Is there any other way of checking? Eg a registry value? If this is true, it's strange how it works in virtualbox, but not hyperv