but if you don’t want to install 3rd party tools, this script is very usefull.
For error-trapping you could use try {…} catch {…} as follows:

Code:
filter Test-TcpPort {

Param([int]$port = 80,
[string]$horst)
$socket = new-object Net.Sockets.TcpClient
try {
$socket.Connect($horst, $port)
if ($socket.Connected) {
$status = “Open”
$socket.Close()
}
else {
$status = “Closed / Filtered”
}
} catch { $status = “Closed / Filtered” }
$socket = $null
write-output “$horst`t$port`t$status”
}

You are right, testing $_ is a non sense.

Arnaud

For error testing, you can use the automatic variable $_. But if you do so, you must disable error display by using $ErrorActionPreference = “SilentlyContinue”.

Here’s your modified script :

filter Test-TcpPort {
### filter: Test-TcpPort
### description: Tests to see if a port is open or closed.
### version: 0.1
### input:
### paramaters (1) (optional, default = 80): [int] port
### object pipeline: [string] IP addresses and hostnames
### output:
### [string] “$_ ## status” where # is port number
### TODO: create custom object for output instead of strings
### also need to trap the connect errors
Param([int]$port = 80)
$ErrorActionPreference = “SilentlyContinue”

$socket = new-object Net.Sockets.TcpClient
$socket.Connect($_, $port)

if ($_ -and $socket.Connected) {
$status = “Open”
$socket.Close()
}
else {
$status = “Closed / Filtered”
}
$socket = $null
write-output “$_`t$port`t$status”
}

Can I put you script in my French Powershell script repository ?

Best regards from France,

Arnaud

Shay
http://scriptolog.blogspot.com