About NeilR

We had this issue as well recently. We are using the 5.1-13 client. Two different WIN 10 users on both Pro and Enterprise. I suspect some recent change on Win 10 is interacting with GP, and not allowing the stack to connect. Even when the user has admin rights uninstall/reinstall did not fix unless done by the Administrator account. Where this is an issue is because we don’t give local administrator account access to users. So the admininstrator login doesn’t work for remote support.    After some testing I use this workaround which seems to solve the problem for the impacted remote user: Uninstall the 5.1 client Reactivate or otherwise deploy the 4.1 client and install - this does not have the dependency on local admin to set portal and credentials. Re-activate the 5.1 client and allow it to auto-update when the user logs on to the firewall The client is now open for the user to login and set the credentials.   As the remote users are isolated mostly this is less a short term issue. As this just started affecting us it seems to be related to recent Win 10 updates. I had this happen on a new install and existing install, both pro and enterprise editions ... View more

More on this. Where this is an issue is because we don’t give local administrator account access to users. So the admininstrator login doesn’t work for remote support.    This workaround seems to solve the problem for the impacted remote user: Uninstall the 5.1 client Reactivate or otherwise deploy the 4.1 client and install - this does not have the dependency on local admin to set portal and credentials. Re-activate the 5.1 client and allow it to auto-update when the user logs on to the firewall The client is now open for the user to login and set the credentials.   Some questions still being researched: Only Domain users? Can another domain user log into the “fixed” machine and use their credentials to connect? As the remote users are isolated mostly this is less a short term issue. As this just started affecting us it seems to be related to recent Win 10 updates. I had this happen on a new install and existing install, both pro and enterprise editions ... View more

I had this problem - network is there but GP won't connect. Only way I could fix it was to install using local Administrator account on windows. Even though my user was an admin, I could not get it to work even with uninstall reinstall. After admin install log back in as user and supply credentials.    Seems like a local security issue, but have not found the fix. This workaround is ok but not good in user support situations ... View more

Not resolved. This was specifically triggered by my account password change on our internal Active Directory system that's provide user auth via LDAP. Same issue - both wifi & cell data network access blocked until GP app deleted and then it was possible to download, install and re-connect to the gateway.   IOS 13.3 and GP 5.1.1-5. Same issue on iphone Xr and ipad pro.   Related to the time delta after changing pw in Windows and finally changing pw on ios? 12 hours during which the app is banging away with a password alert - maybe a stack overflow of some kind. ... View more