Since last year, we are using GlobalProtect 5.0.4 along with DHCP options 43 to detect the Internal GP GW FQDN. The GP client then connects to the branch office GP GW and pushes the User-ID - as it should.
Since I updated our main PA 5520 cluster to PAN OS 9.1, I also upgraded a newer version of GlobalProtect (v.5.1.1 and then v5.1.2).
I noticed now that if the client OS (Windows) runs those latest GP version, authentication to the local GW fails though DHCP option 43 code. To be more exact, the FQDN is detected correctly, but fails with an error ((T1952)Debug( 111): 04/17/20 11:53:24:007 connect failed with error 10047(An address incompatible with the requested protocol was used.))
Thank you for reading and any input.
Cheers to all.
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!