We had this issue with several users and the workaround suggested on the article sorted the issue out. Adding a dummy domain on the split tunnel tab worked. Note: without "no direct access to local netwok" othersie this will nullify the fix of using the domain in split tunnel. From the admin-guide: "Disable the No direct access to local network option (Split TunnelAccess Route). If enabled, this setting disables split tunneling on Windows, Linux, and macOS networks." The 2nd workaround is to disable weakhost mode from the powershell with commands: Get-WmiObject win32_networkadapter | where-object NetConnectionStatus -eq 2 | where-object ServiceName -ne PanGpd | ForEach {netsh interface ipv4 set interface $_.InterfaceIndex weakhostsend=disabled} Get-WmiObject win32_networkadapter | where-object NetConnectionStatus -eq 2 | where-object ServiceName -ne PanGpd | ForEach {netsh interface ipv6 set interface $_.InterfaceIndex weakhostsend=disabled} Both workarounds worked fine for all the users. Does anyone know if this design is intended to be changed in future GP releases? I guess this is a something for a feature request. Did someone requested one for this matter? Thank you!
... View more
