Submit a ticketCall us
Home > Success Center > Server & Application Monitor (SAM) > Connection Quality polling fails on Windows Server 2012 nodes in SAM

Connection Quality polling fails on Windows Server 2012 nodes in SAM

Updated March 5, 2018

Overview

After you enable Connection Quality polling on the Application Connection Settings page, SAM deploys TCP agent plug-ins with Npcap drivers to Windows nodes to support NPing, an open source tool that generates network packets so SAM can collect TCP connection metrics via synthetic polling. Errors may occur after each Connection Quality poll (every five minutes) for Windows Server 2012 nodes. 

(©2018 InsecureOrg, available at https://nmap.org/nping, link obtained on March 5, 2018.)

Environment

  • SAM 6.6
  • Nodes running Windows Server 2012 

Cause 

When Connection Quality polling is enabled, SAM deploys agent plug-ins with Npcap drivers to Windows nodes with application dependencies. Windows Server 2012 nodes may not recognize Npcap drivers due to a network interface service that is also installed with that OS may not bind properly during initialization. 

Resolution

Restart nodes running Windows Server 2012 and wait for the next Connection Quality poll to occur in five minutes. If the issue continues, create a list of impacted nodes and follow these steps:

  1. Disable Connection Quality polling on the Application Connection Settings page. SAM will remove all Npcap plug-ins.
  2. In Npcap is not installed yet, use C:\Program Files\Npcap\NPFInstall.exe -r to install Npcap 0.93 or later on Windows Server 2012 nodes manually.
  3. For each node, run the following command to ping a valid IP address such as the Orion poller: 

.\nping.exe --tcp xxx.xxx.xxx.xxx 

  1. Restart each Windows Server 2012 machine, which will also reset network interfaces on nodes.
  2. Enable Connection Quality polling on the Application Connection Settings page and check polling results.

Two other workarounds include:

  • Reset the related network interface. If multiple network interfaces are involved, reset all.
  • Reboot the machine running Windows Server 2012.
 

 

Last modified

Tags

Classifications

Public