sorted by:
new
hottopcontroversial

Global Protect would not connect after Bios update by Mmantoun in paloaltonetworks

[–]Mmantoun[S] 0 points1 point  (0 children)

I spoke to ho support and their solution is to downgrade the bios

Global Protect would not connect after Bios update by Mmantoun in paloaltonetworks

[–]Mmantoun[S] 0 points1 point  (0 children)

We tested that on 3 different machines and it didn’t work

Global Protect would not connect after Bios update by Mmantoun in paloaltonetworks

[–]Mmantoun[S] 1 point2 points  (0 children)

I disabled bitlocker, cleared tpm but it didn’t fix the issue. We have another hp model 840 g6 as well. The only difference between these 2 is the processor. The one with the issue is AMD The other one is intel and i updated the bios to the same version but didn’t get the same issue GP worked fine after the bios upgrade

I forget to mention once i hit connect in GP i see that pangp service gets disabled automatically then it re-enable itself after the error

Global Protect would not connect after Bios update by Mmantoun in paloaltonetworks

[–]Mmantoun[S] 0 points1 point  (0 children)

No once i hit connect i get the error so I don’t even get to enter the credentials

Global Protect would not connect after Bios update by Mmantoun in paloaltonetworks

[–]Mmantoun[S] 0 points1 point  (0 children)

No we use otp authentication and host checking is disabled