macOS GP client says its connected - but it really isnt

[C.Chamberlain]

steps to repro issue:

1. run any Mac w Ventura or Sonoma installed

2. run any GP versions for past year (yes this issue remains unresolved that long)

3. click GP icon in your menubar to connect to corp network

4. after auth process - verify you see connected status from GP 

5. from a home office, try to load VPN only website (known to work in office) or ping corp domain 10.x.y.z

6. check in with HIP submit button - works sometimes other times a fails for awhile (up to an hour messing around)

7. expected action = site loads / can ping domain

8. actual action = site doesnt load / cant ping domain

8. 

[JayGolf]

Hi @C.Chamberlain ,

Can you verify if the GP client is actually assigning you an IP address from the expected VPN pool? Double check with the gateway connection logins as well. Take a look at the GP client logs to ensure the auth process completes successfully. Incomplete auth might prevent the tunnel from fully establishing. 

[C.Chamberlain]

yes the machines are getting an IP. But this is secondary to why GP client says its connected when it really isnt. 

We are having to tell our users to hit a VPN only website to confirm connectivity. If this issue is to last, is there a known method to notify the user that they will need to do a secondary verification? This is really causing pain for our WFH users who do password changes which always require VPN, and they think they are legitimately connected, only to find out they werent, and have to make an unplanned trip to the office to remedy the problem. We are really in a bind here!