The company I worked for observed an unusual error today with just Windows 7 users of GlobalProtect
Windows 10 & Macos users were unaffected.
We use okta verification to allow authentication btw
In a nutshell, did some testing in virtual machines running latest patched version of Windows 7 and Windows 10
All windows clients were able to connect, all windows 7 clients got...
An error occured in the secure channel.
Both machines were running 64bit client
Have tried older clients on both os's and always the same... win10 connect, win7 does not
UPDATE: We installed GlobalProtect64-4.1.4 on the Windows 7 machines, and the OKTA issue was no more!
It does raise more questions than it answers though...
* Could a firewall or server change have caused this?
* Why weren't macos or Win10 clients effected?
This same issue also started affecting my users as well. It showed up just in the last few weeks. Also appears to be isolated to Windows 7. We also use Okta SAML authentication for GlobalProtect. We are on GP client ver 4.0.5-8.
I'm going to test your sugestion of updating the GlobalProtect client.
Might it have been a Microsoft update altering how Windows handles SSL or TLS?
Upgrading GlobalProtect VPN client appears to be resolving the issue for us. Swapping to ver 4.1.5 seems to be working better. And I think they made some good improvements with the UI in ver 4.1.x over 4.0.x.
GlobalProtect release notes indicate a bug sounding similar to this issue was fixed:
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!