End-of-Life (EoL)

GlobalProtect App 4.0.7 Addressed Issues

The following table lists the issues that are addressed in the GlobalProtect™ app 4.0.7 release.
Issue ID
Description
GPC-5654
Fixed an issue where macOS clients ignored the DNS settings for GlobalProtect VPN tunnels when the physical interface on the clients was manually configured with static IP and DNS settings and you enabled split tunneling on the GlobalProtect gateway (
Network
GlobalProtect
Gateways
<gateway>
Agent
Client Settings
<client_configuration>
Split Tunnel
).
GPC-5638
Fixed an issue where end users experienced connection timeouts or slow connections to applications because GlobalProtect made several RequestCredentials calls before establishing the connections.
GPC-5637
Fixed an issue where a GlobalProtect OSX client attempted an initial connection to GlobalProtect without end user interaction when you configured the client property list file (plist) with the GlobalProtect portal IP address and set the connect method to on-demand.
GPC-5566
Fixed an issue where endpoints could not connect to a GlobalProtect internal gateway that you configured with DHCP sub-option codes and with an FQDN to specify the firewall interface for the gateway (
Network
GlobalProtect
Portals
<gateway>
Agent
<agent>
Internal
).
GPC-5556
Fixed an issue on Windows 10 endpoints where the GlobalProtect app reverted the Windows Local Group Policy settings to the default values after end users logged out and logged back in to the endpoints.
GPC-5536
Fixed an issue where the GlobalProtect app on a Windows endpoint with more than two DNS servers configured on the physical adapter could not connect to the GlobalProtect gateway.
GPC-5526
Fixed an issue where the GlobalProtect app did not detect F-Secure Computer Protection v17 on endpoints when performing a Host Information Profile (HIP) check.
GPC-5448
Fixed an issue where endpoints did not correctly display non-UTF8 characters in the names of GlobalProtect gateways when you listed the available gateways (right-click the GlobalProtect icon and select
Connect to
).
GPC-4470
Fixed an issue where, after you configured the GlobalProtect gateway to use authentication cookies (
Network
GlobalProtect
Gateways
<gateway>
Agent
Client Settings
<client_settings_configuration>
Authentication Override
), GlobalProtect displayed an Authentication failure message at the login prompt even before the end user had a chance to provide login credentials.

Recommended For You