App Control: How to Test Agent Network Connectivity (Windows)
search cancel

App Control: How to Test Agent Network Connectivity (Windows)


Article ID: 286509


Updated On:


Carbon Black App Control (formerly Cb Protection)


To test network connectivity between an endpoint and the App Control Server.


  • App Control Agent: All Supported Versions
  • Microsoft Windows: All Supported Versions


  1. Log in to the endpoint being tested and use a command prompt to issue the following commands:
    cd "C:\Program Files (x86)\Bit9\Parity Agent"
    dascli status
  2. In the returned output, locate: Server Information > Server and note the address.
    Example: means the Server Address is and port is 41002.
  3. Issue the following commands:
    netstat -ano | findstr "41002"
    nslookup <ServerAddress>
    ping <ServerAddress>
    tracert <ServerAddress>
    netsh winhttp show proxy
    (for XP/Server 2003 use: proxycfg)
  4. Use PowerShell to issue the following commands:
    Test-NetConnection -ComputerName <ServerAddress> -Port 41002 -InformationLevel "Detailed"
    Test-NetConnection -ComputerName <ServerAddress> -Port 443 -InformationLevel "Detailed"
  5. Confirm results are successful (See Additional Notes for further reference)

Additional Information

  • The output of the PowerShell command should indicate that the name resolves to an IP and the TcpTest is "True"
    RemoteAddress            :
    TcpTestSucceeded         : True
  • If Remote address did not return the correct IP address then the DNS must be fixed
  • If the TcpTest is "False" then port 41002 is not accessible on the server
  • The output of netstat -ano | findstr "41002", should be 'ESTABLISHED' - This is necessary in order for comms to succeed between agent and server. If there is anything other than 'ESTABLISHED' (including No output), then this generally indicates some issue or other with Firewall or proxy settings, and will likely need the Infra/IT Team to help determine why Port 41002 connection was not 'ESTABLISHED', as this is not something the agent has control of, as it relies on the connection settings in order to make the 2 way communication.
  • If ICMP response is disabled in the environment, ping may not be successful
  • For more information on communication requirements see the documentation for the relevant version
  • Optionally if Telnet is available, you can check connectivity with:
    telnet AppCServerName 41002
  • For more information on telnet see: