We are having this connection failure since December 13, 2021. The connection process is starting but the login window to input the user credentials is not displayed anymore. Connection to 41.65.183.2:443 is established, but all other opened connection to port 80 are TIME_WAIT. Is this failure related to the published security issue with JAva log4j?
A
Answer by
Ashish Bajaj
The failure with GlobalProtect is not directly related to the published security issue with Java log4j. It seems to be a connection issue where the login window does not appear.
Installed GlobalProtect version: 5.2.4-21
OS: Windows 10 Enterprise
We are having this connection failure since December 13, 2021.
The connection process is starting but the login window to input the user credentials is not displayed anymore.
Connection to 41.65.183.2:443 is established, but all other opened connection to port 80 are TIME_WAIT.
Is this failure related to the published security issue with JAva log4j?
The failure with GlobalProtect is not directly related to the published security issue with Java log4j. It seems to be a connection issue where the login window does not appear.