The GP client doesn't leave the connecting state and load the locally cached portal configuration because the locally stored portal cache is not utilized until credentials are entered into the GP client and a connection to the portal is attempted. If ' on-demand mode' is selected in the portal configuration and the GP client connects to the portal, it will recognize that on-demand mode is enabled, stop spinning (leave the 'connecting' state) and wait for the user to hit the connect button to connect to the Gateway / VPN. The GP client will remain in this state if credentials aren't entered or saved on the client machine because it's unable to attempt a connection to the portal without those credentials. This is not an attempt to connect to the Gateway/VPN, only to the portal. The GP client icon stays in the 'connecting' state after a reboot because, by design, it will always try to connect to the portal for the latest configuration after a reboot or restart of the GP client software. Why doesn't the GP client ever leave the connecting state and load the locally cached portal configuration residing on the client machine?

The Global Protect client icon just spins in the taskbar after a reboot and remains in a 'connecting' state.

Sony vegas pro spinning text