Yes, I know it's Windows 7, but with COVID the new hardware delivery has been delayed yet again. This is a short term issue, but it's mission critical.
The machines were connecting just fine using the previous version of GlobalProtect. Now our vendor is forcing us to connect using 5.2.
On later Windows 7 machines it loads and runs flawlessly. On the existing workstations which are probably a little older, I could not get 5.2 to load. Then I realized it was a SHA256 issue. MS released an update for that last year. After applying that, I can get 5.2 to load, but not connect. It looks like at connect we do not get the:
(T6400)Debug(5090): 11/03/20 19:29:31:963 Gateway xxx.xxxxxxxx.com, response to the hip report check:
Instead, it fails.
If we cannot resolve this before Monday, we will have move hundreds of files back to an old legacy system to try and be able to open on Monday. Our vendor has been unable to resolve the issue. Any help would be much appreciated.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!