Does anyone know if the GP client uses the settings it previously received from a gateway when it initially connects? In my past life using Cisco AnyConnect, a change to the AnyConnect profile would only become "active" if the user connected twice to the ASA after the change. The first time would push the change to AnyConnect, and the second time the client would use the change when connecting.
I seem to have observed some similar behavior with GlobalProtect 5.2.12 on a Mac. We implemented IPv6 sinkhole to address dual stack clients. In the meantime, another dual stack client reported a symptom of MS Outlook client seeming to be connected (to Outlook as no error messages appear and to GlobalProtect), but wouldn't send/receive mail (symptoms of Azure CAP, as not a trusted device on the open internet). However, the when the issue couldn't be replicated, the user indicated the Outlook issue hasn't recurred in X days, and it was attributed to our IPv6 sinkhole fix which was implemented in that window.
However, when we attempted to break Outlook by having the client connect to a gateway that did not have IPv6 sinkhole configured, the issue could not be duplicated. The user then connected back to our IPv6 sinkhole enabled gateway, and within a few hours was no longer sending/receiving messages. The client logs indicated an IPv6 address was assigned to the virtual adapter so it appeared to have the correct settings, but the display of symptoms would indicate otherwise. No other Mac Outlook client issues have been reported, but to our knowledge our dual stack population is also low.
... View more
