stAgentSvc NSCOM2 bind error

  • 20 April 2023
  • 4 replies
  • 153 views

Badge +3
  • Netskope Partner
  • 0 replies

Can anyone help me in understanding the below error logs and what could be the issue here.

Thank you in advance!

 

User's Netskope client is in disabled state.

 

2023/04/20 10:50:32.663 stAgentSvc p1484 t48d0 error NSCom2.cpp:863 NSCOM2 bind failed on sever socket 10013
2023/04/20 10:50:32.663 stAgentSvc p1484 t48d0 error stAgentSvcEx.cpp:2147 nsAgentSvc Token not found in the client name
2023/04/20 10:50:32.663 stAgentSvc p1484 t48d0 error stAgentSvcEx.cpp:1225 nsAgentSvc Failed to get session details on NSCom error


4 replies

Badge +4

Hi @tam 

This symptom can occur if the Antivirus exceptions are not being applied. 

Please check the https://docs.netskope.com/en/exceptions-for-anti-virus-applications.html

 

Thanks!

TP

You need to restart your netskope client 

Badge +9

Hey,

Managed to solve?
I have the same problem, I can't access an application via CLI, I see this error in the client's logs.

When the client is up and the NPA receives an error return above E0705 Proxserver error during proxy request: net/http: TLS handshake timeout.

Userlevel 4
Badge +12

Bumping this - it seems Netskopes response to logs with these errors (i.e. Failed to get session details on NSCom error) is that Antivirus exceptions are not inplace. We get this a lot and have fully enabled all exclusions in Crowdstrike. Any more information on how to track this down?

Reply