05-03-2022 02:13 PM
I have been having an issue over 2022 in that some users when logging on remotely via Prisma cant connect. I have tracked it down and it seems to be a fairly new windows widget in windows10 where a weather and location widget loads.
To get around it i had to create a prelogon rule to allow access to external internet services, the logon works as expected. We think we have narrowed it down to the following urls -
It looks like the windows 10 build tries to connect to these resources before the full tunnel is built.
Just curious but has anyone else seen this issue and know why this widget would cause the pre-tunnel to fail
06-02-2022 03:02 AM
I have spoken to Microsoft and taken logs off an affected laptop.
It turns out this is the problematic URL - autologon.microsoftazuread-sso.com
If i whitelist this URL then pre-tunnel is unaffected but if i dont a lot of users are getting an issue where their taskbar hangs and they cant login to global protect until they disconnect their wifi and turn it back on. It must be because the laptops are trying to login to Azure even though our laptops are not Azure joined - they are only Azure registered.
has anyone else seen this before and does anyone know why this would affect the pre-tunnel if not whitelisted
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!