Global Protect Split Tunnelling on Domains - client version issue?

Reply
Highlighted
L4 Transporter

Global Protect Split Tunnelling on Domains - client version issue?

Hey folks.

 

We're planning in implementing MFA for Office 365, and as part of that I want to add the Microsoft office domains into our Global protect split tunnels - since almost everyone is working from home, I want to whitelist our "corporate" IP addresses and have people who are connected from company PC's on the VPN not be bothered by MFA requests.

 

This is relatively easy in the configuration, but I've come across an issue which is perplexing me.

 

I run my personal machine on a fairly recent VPN client to check for issues before pushing it out to the main portal for users to upgrade - and when I implemented this split tunnel on the portal, it didn't work.

 

A colleague who is running the "production" release I have on the portal. So I downgraded tot hat version - and the split tunnelled domains work.

 

Does anyone know if there's something extra in the later clients which needs to be done to make this work?

 

Working client version - 5.0.8

Failed client version - 5.2.2

 

Thanks

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 Live Community as a whole!

The Live Community thanks you for your participation!