Additional global protect portal and gateway

[DF2020]

Hi

We have a working user-logon always on GP setup using certificates to authenticate, but we would like to make some changes and go to prelogon, but with most of the company working remotely we thought we would play it safe and setup a second GP instance on our 820 to use as a testing environment, this is where things got interesting. As a test we have managed to setup a second GP portal instance working with Microsoft authenticator (RADIUS) on-demand, via the loopback method. This allows us to log in (after being prompted by authenticator) and download the client, but once the GP client is installed and we try to connect it just comes up with the error saying  "Error: No network Connectivity. Please verify your network connection and try again", but nothing shows up in the PA's logs for that attempt. I have tried various tweaks thinking it would help but so we havent got much further

[BPry]

@DF2020,

So you've gotten to the portal, but you haven't been able to actually verify the gateway access. You need to start focusing on the gateway configuration and making sure that the gateway is accessible. You'll also want to double check that you have a policy that would match any denied traffic to the portal/gateway IP address or enable logging on the interzone-default policy so that you can verify that your security rulebase is actually correct.

Are you using the same address for your portal/gateway, or are you seperating those out? 

[Namalw]

Addition to recommendations from DF2020, please check if you haven't mis-typed the portal address on the GP client, I encounter the same issue where portal name was incorrect and GP client reported it as "Error: No network Connectivity. Please verify your network connection and try again"