GlobalProtect - Connecting before pre-logon

Showing results for 
Show  only  | Search instead for 
Did you mean: 

GlobalProtect - Connecting before pre-logon

L1 Bithead

Hi Everyone,


We are experiencing an issue with some of our Windows 10 laptops where if the user connects before the pre-logon tunnel establishes at the Windows logon screen, then they are presented with a Global Protect error saying 'VPN Connection could not be established' once the desktop loads.


I have checked the system logs during this process, and the strange thing is that the tunnel does get established and is up, even though GP says otherwise. However either the user needs to refresh the connection, or if you wait long enough GlobalProtect will auto refresh before it displays as connected.


The system logs look like the following;

<user logs into Windows, before pre-logon tunnel>

1 globalprotectportal-auth-succ               Portal          user authentication succeeded. User name: xxxx
2 globalprotectportal-config-succ            Portal          client configuration generated.
3 globalprotectgateway-auth-succ          Gateway     user authentication succeeded. User name: xxxx
4 globalprotectgateway-regist-succ        Gateway      user login succeeded. User name: xxxx
5 globalprotectgateway-config-succ       Gateway     client configuration generated.
6 globalprotectgateway-switch-succ       Gateway     client switch to SSL tunnel mode succeeded.

<user see's popup saying VPN failure>
7 globalprotectgateway-auth-succ          Gateway      user authentication succeeded. User name: xxxx
8 globalprotectgateway-regist-fail           Gateway      user login failed. User name: xxxx, error: Existing user session found.
9 globalprotectgateway-config-release   Gateway    client configuration released. User name: xxxx
10 globalprotectgateway-logout-succ     Gateway     user logout succeeded. User name: xxxx, Reason: remove previous login.
11 globalprotectgateway-regist-succ      Gateway     user login succeeded. User name: xxxx
12 globalprotectgateway-config-succ     Gateway     client configuration generated.

<user sees VPN connected message>


If the user waits for the pre-logon tunnel to establish (which sometimes its not easy to ask them to do this, you have to explain where to find the icon which shows this on the Windows logon screen) then the tunnel will establish with pre-logon user, and then rename when Windows loads - as per design.


Has anyone come across anything similar with people logging in before the pre-logon tunnel establishes?


Thanks in advance





Accepted Solutions

L1 Bithead

We had a ticket open with support for some time, although the main issue that we were trying to fix was pre-logon tunnels not renaming, the problem in this post was also resolved along with the tunnel-rename issue being fixed. 


What it came down to was routing from the internal network to the gateways.


As we have multiple internet circuits and a gateway on each one, we had to make sure that traffic was getting routed correctly. When we looked into this we found one gateway was going into a routing loop and we needed to put a PBF in place to make the traffic bypass the default PBF rules.


It's not a very detailed solution, but I hope this may point others in the right direction.

View solution in original post


Cyber Elite
Cyber Elite



We are Running GP 5.2.2 with Prelog on always on no issues.

Our machine tunnel connects before user log on and GP shows connected.

We are using windows 10 laptops.


Make sure under Portal agent single sign is configured as Yes.




Thanks @MP18 , it works fine for us too - but only if you wait for the pre-logon tunnel to establish.


If you get your credentials in before that, then there are issues once Windows loads.


As per my understanding in our case we see user login prompt and we see sign in options.

Then if i click on sign in options i see GP icon shows connected in sec or 2

For prelogon always on we need to wait for few secs to get the GP machine tunnel built with user name prelogon.


I will say check the client side GP logs in your case if it takes more time to built machine tunnel?

Once PC is rebooted and login prompt is there then GP prelogon should connect with few secs








What build of the GlobalProtect Agent do you have deployed? I can't say that I've seen this issue in recent releases, but we did see it on occasion with old releases of the agent. However, post 5.0 and higher we've completely eliminated the issue getting reported within our environment. 

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!