I know Palo's best practice is to use a different FQDN from your web-interface if configuring GlobalProtect Clientless VPN. But, I'd like to know - If using separate FQDNs for globalprotect clientless VPN (e.g web.globalprotect.com) and client-based VPN (e.g vpn.globalprotect.com), is it possible to use the same public IP address to host the GlobalProtect clientless VPN and the client-based VPN?
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!