GlobalProtect App 4.1 Known Issues
See a list of the Known Issues in GlobalProtect™ app 4.1.
The following table includes known issues in GlobalProtect™ app 4.1.
When you configure a split tunnel to include or exclude a destination domain, the GlobalProtect app for Windows endpoints disconnects every time users establish the GlobalProtect connection and attempt to access the specified domain.
Windows users receive a script error when authenticating to the GlobalProtect portal or gateway using SAML authentication.
On endpoints running Android 8.0 and later releases, GlobalProtect does not reconnect automatically when switching from internal mode (corporate Wi-Fi) to external mode (LTE).
On Windows endpoints, the GlobalProtect app icon intermittently disappears from the notification area (system tray) and reappears only when you halt the GlobalProtect process.
Workaround: Launch the GlobalProtect app from the Start menu.
This issue is now resolved. See GlobalProtect App 4.1.6 Addressed Issues.
GlobalProtect cannot identify and display
Last Full Scan TimeHIP data for Bitdefender Antivirus on macOS endpoints.
This issue is now resolved. See GlobalProtect App 4.1.5 Addressed Issues.
The GlobalProtect app for Linux endpoints prompts end users to enter their credentials in succession despite entering correct credentials. This issue occurs after the end user attempts to connect to an alternate manual gateway configured with the User-logon (Always On) connect method.
GlobalProtect cannot identify and display the
Last Full Scan TimeHIP data for the 360 Total Security antivirus app.
Endpoints can't connect to GlobalProtect after you set the Windows System Display to Chinese and specify Chinese characters for the
Username Labelin the GlobalProtect app login page (
Workaround:Specify English characters for the
Allow User to Disable GlobalProtectand then specify a
Disable Timeoutvalue to restrict the amount of time for which users can disable the app (
), the GlobalProtect app for macOS endpoints does not automatically enable after reaching the
Workaround: Users must manually enable the GlobalProtect app.
Endpoints running iOS 10.12 and later iOS releases on the T-Mobile LTE network cannot connect to GlobalProtect gateways that are configured with only IPv4 addresses because T-Mobile now assigns only IPv6 addresses to endpoints running iOS 10.12 and later releases.
Workaround: Configure your GlobalProtect gateway with FQDNs instead of IPv4 addresses.
On Windows 10 endpoints, the GlobalProtect app removes DNS suffixes due to an error in the read/rewrite function that directly modifies the DNS suffix search list in the Windows registry key.
On macOS endpoints, the GlobalProtect app can’t detect the following
Anti-Malwareinformation for the HIP Match log details of the Gatekeeper security feature (
Proxies are disabled after you establish the GlobalProtect connection on macOS endpoints because proxy settings are not copied from the physical network adapter of the endpoint to the virtual network adapter of the endpoint, and the virtual network adapter becomes the primary adapter from which the macOS endpoint receives proxy settings.
When a user first logs in to a GlobalProtect VPN that uses SAML authentication with pre-logon enabled, the tunnel rename (from pre-logon to user logon) fails, the pre-logon tunnel is disconnected, and the user is prompted to re-authenticate.
Recommended For You
Recommended videos not found.