GlobalProtect Enforce Connection for Network Access Windows session logon Latency

[plevesque]

Hi,

I have noticed that enabling the Enforce GlobalProtect connection for network Access is adding latency at the user Windows logon session, wondering if other people experience the same and what could be the root cause and for any workaround.

Thank you,

Kind regards

Pierrick L

[Remo]

Are you using pre-logon?

When you talk about latency, do you mean that the response time to internal ressources is getting higher (for example 60ms instead of 40ms) or does it just take longer to login until you see the desktop?

If it is the second ... did you check your logs for dropped connections to internal ressources (active directory, homedrives, printservers, ...)?

[Raido_Rattameister]

If you use pre-logon then check if your clients can access DNS servers.

Windows logon can be really long if it can't resolve DNS at this time.

[plevesque]

Hi,

Thank you for your response, i am using user logon and while enabling the enforce globalprotect connection for network access it takes longer to login to windows and reach the windows logon session.

it could be explain by the fact that windows is not having any network access at this stage becaase of this global protect option.

But is there any alternative, or workaround?

Thank you

kind regards,

Pierrick L 

[Remo]

The solution is pre-logon.

Because the client does not have access to any ressources (including dns) it waits and waits and waits for responses ... and then once windows gives up and realizes that it does not have network access at that time and continues with cached ressources

[Raido_Rattameister]

Are your users inside company perimeter or at home/airport?