Has anyone who's implemented the Enforce Global Protect connection option had issues permitting remote support applications?
I've tried adding the required wildcarded FQDN's to the Global Protect Portal under App Configurations but no joy yet.
Just wondering if anyone else has had a similar issue?
Solved! Go to Solution.
Correct, my thinking is that if an end user cannot connect to the Gateway for whatever reason but the Global Protect Client is still preventing internet access we'd be unable to provide them with remote support unless we used the static disable passcode.
So I've only done this in my lab, but it appears to work as I would expect without any issues and I can access allowed resources without issue. I think the difference here though is that you're trying to access the machine remotely through this method right? So you're trying to allow access to some service such as logmein or something like that so you can then remote into the machine?
@BPry Correct, so the remote support client app needs to pull down a code on the impacted endpoint for use by the admin on their host software, who then establishes the remote connection.
Under my current testing using a pilot Portal Agent config, the connection doesn't work and a code isn't even pulled down.
We have the required FQDNs added into App Configurations but there is also an additional TCP port that may be required (I think we'll need to permit this on the Windows Firewall).
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!