Applications Systems

SAM TCP port monitor is not functioning correctly

TCP port monitor is not working. Connection refused. The target actively refused connection. Port monitor failing, port monitor is down. No connection being made because target machine actively refused

First published date

5/16/2019 7:55 PM

Last published date

11/30/2019 9:27 PM

Overview

This article describes potential resolutions for failing TCP port monitors. This is one of the types of components within SAM that tests an  open port. These can fail for many reasons, almost all causes are environmental network issues. 

Product section

Server Application Monitor

Cause

The TCP port is blocked by the firewall.

Resolution

Test connection outside of the software.
  1. RDP to the Orion polling engine assigned to the node with the TCP Port Monitor.
  2. Open PowerShell as administrator.
  3. Execute the following command. Replace <server> and <port> with the actual server hostname of the target node and the port number configured in the TCP port monitor. 
    -- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

Test-NetConnection -ComputerName <server> -Port <port>

If the test fails, consult your network team for further assistance. 

If the test passes, contact SolarWinds support.



Alternate solution: Try rebooting the poller on which this application monitor is not polling properly. It's possible that there's a JobEngine process holding bad run of application monitor.