9 responses to “Testing TCP Port Response from PowerShell”

• 

  jkavanagh58 December 20th, 2011 at 12:50

  Excellent!

• 

  Jeffery Hicks December 20th, 2011 at 13:27

  I’m curious why you don’t use New-Object to create $MyObject and why you add it to $myCol. In this version you end up writing a string object to the pipeline with a number of note properties. I would think all you need is code like this:

  New-Object -TypeName PSObject -Property @{
  Computername=$computername
  Port=$Port
  Response=$Response
  }

  Simple write each response object to the pipeline.

• 

  Jonathan Medd December 20th, 2011 at 14:27

  Thanks Jeff for the feedback, that was mostly lazy in my part in moving a lot of pre-packaged stuff I have used in other scripts and making it more appropriate for pipeline use, rather than foreach statements – updated accordingly. Always appreciate someone of your knowledge casting a critical eye

  I’ve never liked New-Object and the fact you can’t control the order of the output (slightly OCD), so I prefer to use the Select-Object way until I can use v3 and [ordered].

• 

  Jeffery Hicks December 20th, 2011 at 14:31

  I have the same reservations about New-Object. The way around it is to add type name to the custom object and include your own format extension (.psxml) file.

  The other challenge here is that if a computer is offline or unreachable the port will show as closed. And maybe that’s ok. But it could also lead to a misunderstanding.

• 

  Shay Levy December 20th, 2011 at 14:54

  I also don’t like the fact that New-Object doesn’t retain the order of properties, but as Jeff suggested, I also prefer to use New-Object. When I need to retain the order of properties I pipe the result to the Select-Object cmdlet and specify the properties again in the order I need. Not so friendly

  Now, you can still use the same method you chose and cast the properties to the desired type:

  $MYObject = “” | Select-Object ComputerName,Port,Response
  $MYObject.ComputerName = $ComputerName
  $MYObject.Port = [int]$Port
  $MYObject.Response = $Response
  $MYObject

  Lastly, you need to mark the ComputerName parameter as Mandatory. I would also make the the ComputerName parameter more robust and pipeline-able by adding the ValueFromPipelineByPropertyName and the Alias attributes:

  [Parameter(Mandatory=$true,Position=0,ValueFromPipeline=$True,ValueFromPipelineByPropertyName=$true)]
  [Alias('CN','__SERVER','IPAddress','Server')]
  [System.String]
  $ComputerName,

• 

  Sitaram Pamarthi December 21st, 2011 at 07:05

  >I also don’t like the fact that New-Object doesn’t retain the order of properties

  Hi Shay Levy,

  I recently authored a post that talks about port connectivity using powershell.

  http://techibee.com/powershell/powershell-test-port-connectivity/1214

  I created custom object for output by using new-object cmdlet and able to print the colums in desired order by using select statement. Is this approach is good?

• 

  Jonathan Medd December 21st, 2011 at 08:59

  That is great, thanks for the feedback. The alias attribute is super cool, I had somehow missed seeing that before.

  Thanks!

• 

  Jonathan Medd December 21st, 2011 at 09:01

  Cool, excellent suggestion. Take the point about the computer being offline. For my requirements that is exactly the scenario I am trying to match, I guess I could also add an optional ping test.

• 

  John February 21st, 2012 at 11:26

  Hey,

  I was testing this power shell script and works great on W2k8 R2 systems, but when I tried on wsk8 it doesn’t work. It gives me this error:
  ==
  Missing closing ‘)’ in expression.
  At C:\Users\syseng\Desktop\Test-PortResponse.ps1:26 char:1
  + [ <<<< Alias('CN','__SERVER','IPAddress','Server')]
  ==

  Anyone knows what's the deal with this error?

  Many thanks.

1 Trackbacks / Pingbacks

• Testing TCP Port Response from PowerShell « Igorovo January 15th, 2012 at 16:45

  [...] Testing TCP Port Response from PowerShell @ Jonathan Medd’s Blog Rate this: Sdílejte s:MoreLike this:LikeBe the first to like this post. [...]