MacSO Big Sur with Globalprotect are incompatible ?

cancel
Showing results for 
Search instead for 
Did you mean: 

MacSO Big Sur with Globalprotect are incompatible ?

L4 Transporter

hi,

We have users with MacSO Big Sur having problems with the GlobalProtect client. The software does not run correctly and therefore they cannot establish the VPN. Upgrading to the latest version of the GP client (5.2.6) does not solve the problem.

 

is it known if it is a bug or if palo alto is going to fix the problem?

 

Kind regards.

4 REPLIES 4

Cyber Elite
Cyber Elite

@BigPalo,

What sort of issue are they actually running into? The 5.2.6 agent works perfectly fine across our Big Sur fleet running Intel and M1 based Macs. 

@BPry 

We have users with MacSO Big Sur having problems with the GlobalProtect client. The software does not run correctly and therefore they cannot establish the VPN. Upgrading to the latest version of the GP client (5.2.6) does not solve the problem.

We have seen similar cases at: https://www.reddit.com/r/paloaltonetworks/comments/mietq7/issues_with_globalprotect_on_macos_big_sur...

We have checked that it is not a permissions problem but it is not.

These logs appear in the client logs:


P1842-T38163 04/06/2021 12:37:21:755 Info ( 228): InitConnection ...
P1842-T38163 04/06/2021 12:37:21:755 Debug( 57): fd still open before connect
P1842-T38163 04/06/2021 12:37:21:755 Error( 80): CPanSocket::Connect - Failed to connect to server at port:4767
P1842-T38163 04/06/2021 12:37:21:755 Error( 232): Cannot connect to service, error: 61
P1842-T38163 04/06/2021 12:37:21:756 Debug(1272): CPanCommand::Send - InitConnection failed again. return without sent.

@BigPalo,

This is a service issue on the local device, IE: the agent can't actually connect to the service. On the effected endpoint verify that the service is running by running netstat -an | grep 4767 via terminal. You should see a listening connection show up if things are functioning properly, but according to your logs you won't. 

 

You said that you've verified it's not a permissions issue, but have you actually had the user restart and go into 'System Preferenced' -> 'Security & Privacy' and actually verified that it's not being blocked by macOS? This is usually the source of the issue on macOS endpoints running into service issues like this. 

Hi,

 

we this the tested it and it is not the problem.

 

Have you a idea that can be the problem?

 

Kind regards

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!