SAM Template - PowerShell Script - Test Network Port

I'm going to give the disclaimer that I just wrote this in here, so there maybe some issues.

#Arguments to Variables
Try {
[IPAddress]$IPAddress = $Args[0]
[Int]$Port = $Args[1]
} Catch {
Write-Host "Message: $($Error[0].Exception)"
Exit 1
}

#Clear Script Variables
Clear-Variable TestCon -ErrorAction Ignore

#Test Connection
Try {
$TestCon = Test-NetConnection -ComputerName $IPAddress.IPAddressToString -Port $Port -InformationLevelDetailed -ErrorAction Stop
} Catch {
Write-Host "Message: $Error[0].Exception"
Exit 1
}

#Results
If ($TestCon.TcpTestSucceeded -eq $True) {
Write-Host "Message:  Test Succeeded"
Write-Host "Statistic: 0"
} Else {
Write-Host "Message: Test Failed"
Write-Host "Statistic: 1"
}

Exit 0

On stuff like this, I prefer to use the threshold value and have it, if Statistic equals 1 then Critical.  The down on the monitor would trip in the eve

If you are wanting the other details, you could utilize the multi statistic values.  This would be something like:

Write-Host "Message.InterfaceAlias:  $($TestCon.InterfaceAlias)"
Write-Host "Message.ComputerName: $($TestCon.ComputerName)"
Write-Host "Message.PingSucceeded: $($TestCon.PingSucceeded)"

Steve's answer is correct

There's a much much easier to maintain port check component you should consider instead, given that you're just hoping to return the port status.

If you want to stick with powershell chuck a tracert on there or something

Thank,

This is a building block to use the .count with the port check to find when the number of connection has jumped above a set level.

I'd be interested to know about about what the much easier method is?

THank you SteveK for sharing the script.

You could always try the Application Template Module Monitor TCP Port.

This can monitor a port from a monitored node.

TCP Port Monitor