GlobalProtect Agent error Cannot connect to service, error: 10022

GlobalProtect Agent error Cannot connect to service, error: 10022

126032
Created On 08/31/19 12:51 PM - Last Modified 07/24/26 02:16 AM


Symptom


Global Protect not able to reach the portal and keeps connecting.

Logs from PanGPA.log shows:

(P4888-T22484)Dump ( 586): 04/29/26 10:49:43:425 CPanCommand::Send - not connected, and reintialized connection to service.
(P4888-T22484)Dump (1614): 04/29/26 10:49:43:425 Send command failed
(P4888-T19404)Dump ( 308): 04/29/26 10:49:43:425 InitWinConnection ...
(P4888-T19404)Dump ( 312): 04/29/26 10:49:43:425 Cannot connect to service, error: 10022
(P4888-T19404)Dump (3633): 04/29/26 10:49:43:425 Try to connect to GPS...
(P4888-T19404)Dump ( 308): 04/29/26 10:49:43:842 InitWinConnection ...
(P4888-T19404)Dump ( 312): 04/29/26 10:49:43:842 Cannot connect to service, error: 10022
(P4888-T19404)Dump (1376): 04/29/26 10:49:43:842 Unable to connect to Pan Service
(P4888-T22484)Debug(1604): 04/29/26 10:49:43:932 Special command, expects no return msg: <request><type>setdebug</type><debuglevel>6</debuglevel></request>
(P4888-T19404)Dump ( 308): 04/29/26 10:49:43:933 InitWinConnection ...
(P4888-T22484)Dump ( 586): 04/29/26 10:49:43:932 CPanCommand::Send - not connected, and reintialized connection to service.
(P4888-T22484)Dump (1614): 04/29/26 10:49:43:933 Send command failed
(P4888-T19404)Dump ( 312): 04/29/26 10:49:43:933 Cannot connect to service, error: 10022
(P4888-T19404)Dump (3633): 04/29/26 10:49:43:933 Try to connect to GPS...


Environment


  • GlobalProtect Client
  • Windows OS


Cause


This error means that the GP client cannot communicate with PanGPS process or the agent is not able to start PanGPS service in the client machine itself.



Resolution


Make sure that PanGPS is started and running in Task Manager --> Services
if needed you can reinstall the Agent which will confirm that the process is started automatically.

PanGPS service should be listening on localhost port 4767.  To check run the command on windows PC:

Netstat -an | find "4767"


the output should be as below for example:

TCP    127.0.0.1:4767          0.0.0.0:0                   LISTENING
  TCP    127.0.0.1:4767         127.0.0.1:49779        ESTABLISHED
  TCP    127.0.0.1:49779        127.0.0.1:4767         ESTABLISHED


Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/kCSArticleDetail?id=kA10g000000PMiD&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FkCSArticleDetail

Choose Language