{"id":754,"date":"2010-07-29T15:24:37","date_gmt":"2010-07-29T19:24:37","guid":{"rendered":"http:\/\/jdhitsolutions.com\/blog\/?p=754"},"modified":"2010-07-29T15:24:37","modified_gmt":"2010-07-29T19:24:37","slug":"get-your-tcp-ports-here","status":"publish","type":"post","link":"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/","title":{"rendered":"Get Your TCP Ports Here!"},"content":{"rendered":"

Once again, the PowerShell forum at ScriptingAnswers.com<\/a> has undone me. I was answering a question about running Netstat in a PowerShell session on a remote computer which got me thinking about a PowerShell function to turn NETSTAT.EXE output into objects. Once you have an object then you can do all sorts of things.\u00a0 Needless to say I got hooked on working something up instead of working on what I had planned for the day. The good news is that you get a tool and there's still a few hours of the day left for me to get something else accomplished. I'm sure there are plenty of variations on this topic already out there, but here's my contribution: Get-TCP.
\n[cc lang=\"Powershell\"]
\nFunction Get-TCP {
\n<#\n.Synopsis\nGet TCP Netstat information\n.Description\nThis function calls the command line NETSTAT.EXE tool and returns an object representation\nof the TCP data.\n\nProtocol\u00a0\u00a0 : TCP\nLocalhost\u00a0 : 172.16.10.127\nLocalPort\u00a0 : 49259\nRemoteHost : 74.201.86.29\nRemotePort : https\nStatus\u00a0\u00a0\u00a0\u00a0 : ESTABLISHED\n\nThe default is the local computer without name resolution. However you can specify a remote\ncomputername, assuming the remote computer is running PowerShell 2.0 and has remoting enabled.\nUse -ResolveHost to resolve IP addresses to host names. This is a little slower.\n\nThis function will only return IPv4 hosts and addresses\n.Parameter Computername\nThe name of the computer to query. The default is the localhost.\n.Parameter ResolveHost\nResolve IP addresses to host names. This is a little slower. The is the equivalent of running\nNetstat.exe without any parameters.\n.Parameter ResolvePort\nResolve the service name associated with the port. This requires access to the legacy\nServices file found at $env:windir\\system32\\drivers\\etc\\services.\n.Parameter IncludeRaw\nInclude the raw netstat data.\n.Example\nPS C:\\> get-tcp Return TCP Netstat information for the local computer. .Example PS C:\\> get-tcp \"Server1\",\"Server2\" -resolve<\/p>\n

Return TCP Netstat information for computers Server1 and Server2 with resolved IP addresses.
\n.Example
\nPS C:\\> get-content computers.txt } get-tcp -resolveHost | where {$_.RemotePort -eq 80} | format-table -autosize<\/p>\n

Get HTTP connections for every computer in computers.txt and present as a formatted table.
\n.Example
\nPS C:\\> get-tcp | sort RemotePort | Select RemotePort -unique<\/p>\n

Get a sorted list of all remote connections by port.
\n.Inputs
\nStrings
\n.Outputs
\nCustom object
\n.Link
\nhttp:\/\/jdhitsolutions.com\/blog<\/p>\n

.Link
\nInvoke-Command<\/p>\n

.Notes
\nNAME:\u00a0\u00a0\u00a0\u00a0\u00a0 Get-TCP
\nVERSION:\u00a0\u00a0 1.5
\nAUTHOR:\u00a0\u00a0\u00a0 Jeffery Hicks
\nLASTEDIT:\u00a0 July 29, 2010<\/p>\n

Learn more with a copy of Windows PowerShell 2.0: TFM (SAPIEN Press 2010)<\/p>\n

#><\/p>\n

[cmdletbinding()]<\/p>\n

Param(
\n[Parameter(Position=0,ValueFromPipeline=$True)]
\n[string[]]$Computername=$env:computername,
\n[switch]$ResolveHost,
\n[switch]$ResolvePort,
\n[switch]$IncludeRaw
\n)<\/p>\n

Begin {
\nWrite-Verbose \"Starting $($myinvocation.mycommand)\"
\nif ($ResolveHost) { Write-Verbose \"Resolving host names\"}
\nif ($ResolvePort) {Write-Verbose \"Resolving port names\"}
\n#put everything into a script block so that if the computer
\n#is remote it can be executed using Invoke-Command
\n$scriptblock={netstat.exe -n | where {$_.Contains(\"TCP\") -AND $_ -notmatch \"\\[\"}}<\/p>\n

Write-Verbose \"Caching Services information\"
\n$file=\"$env:windir\\system32\\drivers\\etc\\services\"
\n#get just tcp services
\n$services=Get-Content -Path $file | Select-String -Pattern \"\/tcp\"<\/p>\n

Write-Verbose $($scriptblock.ToString())<\/p>\n

#define the name resolution function
\nFunction Resolve-DNS\u00a0 {<\/p>\n

[cmdletbinding()]<\/p>\n

Param(
\n[Parameter(Position=0,Mandatory=$True,ValueFromPipeline=$True,
\nHelpMessage=\"Enter an IP Address to resolve\")]
\n[string[]]$Address
\n)
\nBegin {
\nWrite-Verbose \"Starting Resolve-DNS\"
\n#turn off error pipeline
\n$errorActionPreference=\"SilentlyContinue\"
\n}
\nProcess {
\nforeach ($IP in $Address) {
\nWrite-Verbose \"Resolving $IP\"
\n$dns=[System.net.DNS]::GetHostByAddress(\"$IP\")
\nif (-not $dns) {
\nWrite-Verbose \"no record found for $IP\"
\n$h=$IP
\n$a=$null
\n}
\nelse {
\n$h=$dns.hostname
\n$a=$dns.AddressList
\n}
\nNew-Object -TypeName PSobject -Property @{
\nHostname=$h
\nAddresses=$a
\n}
\n} #foreach
\n} #process<\/p>\n

End {
\n#turn On error pipeline
\n$errorActionPreference=\"Continue\"
\n}
\n} #end function<\/p>\n

} #begin<\/p>\n

Process {
\nforeach ($computer in $computername) {
\nWrite-Verbose \"Getting raw NETSTAT data from $($computer.toUpper())\"
\nif ($computer -eq $env:computername) {
\n#just run the script block if local computer
\n$data=&$scriptblock
\n}
\nelse {
\nTry {
\n$data=Invoke-Command -ScriptBlock $scriptblock -computername $computer -errorAction \"Stop\"
\n}
\nCatch {
\nWrite-Warning \"Failed to run command on $computer\"
\nWrite-Warning $error[0].exception.message
\n}
\n} #else
\n#process data
\nWrite-Verbose \"Returned $($data.count) items\"
\nWrite-Verbose \"Parsing data\"
\n#initialize a hash table for IP names
\n$hash=@{}
\nforeach ($tcp in $data) {
\nWrite-Verbose $tcp.trim()
\n#split the line removing empty spaces
\n$arr=$tcp.trim().split() | where {$_}
\n$localData=$arr[1].Split(\":\")
\n$remoteData=$arr[2].Split(\":\")
\n$protocol=$arr[0]
\n$raw=$tcp.trim()
\n$local=$localData[0]
\n[int]$localPort=$localData[1]
\n$remote=$remoteData[0]
\n[int]$remotePort=$remoteData[1]
\n$status=$arr[3]<\/p>\n

#if resolve host requested build a dictionary or
\n#ip addresses so we don't need to resolve one already resolved
\n#and change the property value accordingly
\nif ($resolveHost) {
\nif ($hash.contains(\"$local\")) {
\n$local=$hash.Item(\"$local\")
\n}
\nelse {
\n#look up name
\nWrite-Verbose \"Resolving $local\"
\n$localLookup=Resolve-DNS \"$local\"
\n#add to hash
\n$hash.Add(\"$local\",$localLookup.Hostname)
\n#update property
\n$local=$localLookup.Hostname
\n}
\n#do the same for remote
\nif ($hash.contains(\"$remote\")) {
\n$remote=$hash.Item(\"$remote\")
\n}
\nelse {
\n#look up name
\nWrite-Verbose \"Resolving $remote\"
\n$remoteLookup=Resolve-DNS \"$remote\"
\n#add to hash
\n$hash.Add(\"$remote\",$localLookup.Hostname)
\n#update property
\n$remote=$RemoteLookup.Hostname
\n}
\n} #if $resolveHost<\/p>\n

#resolve ports if specified
\nif ($resolvePort) {
\n#this is a mini scriptblock to return the service name
\n#in lieu of a full-blown function
\n$getsvc={Param ([string]$port)
\nWrite-Verbose \"searching for $port\"
\n$service=$services | Select-String -pattern\u00a0 \"\\s$port\/tcp\"<\/p>\n

if ($service) {
\n$data=$service.ToString().Trim().split() | where {$_}
\nWrite-Output $data[0]
\n}
\nelse {
\nWrite-Output $port
\n}<\/p>\n

} #end $getSvc<\/p>\n

[string]$localPort=&$getsvc $localPort
\n[string]$remotePort=&$getsvc $remotePort<\/p>\n

} #end resolveport<\/p>\n

#create a new object and pipe it to Select-Object so that
\n#the properties are in a nice order
\n$obj=New-Object -TypeName \"PSObject\" -Property @{
\nProtocol=$protocol
\nLocalhost=$local
\nLocalPort=$localPort
\nRemoteHost=$remote
\nRemotePort=$remotePort
\nStatus=$status
\n}
\nif ($IncludeRaw) {
\n$obj | Add-Member -MemberType \"Noteproperty\" -Name \"Raw\" -Value $raw -PassThru |
\nSelect-Object -Property Protocol,LocalHost,LocalPort,RemoteHost,RemotePort,Status,Raw
\n}
\nelse {
\n$obj | Select-Object -Property Protocol,LocalHost,LocalPort,RemoteHost,RemotePort,Status
\n}
\n} #foreach $tcp
\n} #foreach computer
\n} #Process<\/p>\n

End {
\nWrite-Verbose \"Ending $($myinvocation.mycommand)\"
\n}<\/p>\n

} #end function[\/cc]
\nThis is an advanced Windows PowerShell 2.0 function. By default it converts output from Netstat -n to object. I've parsed the output so you get an object like this for each line.<\/p>\n

[cc lang=DOS]
\nProtocol\u00a0\u00a0 : TCP
\nLocalhost\u00a0 : 172.16.10.122
\nLocalPort\u00a0 : 60553
\nRemoteHost : 74.201.86.29
\nRemotePort : 443
\nStatus\u00a0\u00a0\u00a0\u00a0 : ESTABLISHED[\/cc]<\/p>\n

When you run Netstat without any parameters it resolves both host and port names. I've separated the two so you can use either -ResolveHost and\/or -ResolvePort. The former uses an embedded function to get the host entry name by IP address. If not found, then the IP address is used. This function by the way only returns IPv4 information. Service ports are resolved by finding the associated TCP port in the legacy Services file. What you end up with is something like this:<\/p>\n

\"\"<\/a>The function can also accept a remote computername as it uses Invoke-Command to run the Netstat command remotely.\u00a0 All the results are then processed locally. You can pipe computernames to the function or it accepts arrays.<\/p>\n

If you have any questions on the nitty-gritty details, please post a comment.<\/p>\n

Download Get-TCP.ps1<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Once again, the PowerShell forum at ScriptingAnswers.com has undone me. I was answering a question about running Netstat in a PowerShell session on a remote computer which got me thinking about a PowerShell function to turn NETSTAT.EXE output into objects. Once you have an object then you can do all sorts of things.\u00a0 Needless to…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[72,75,99,135],"tags":[32,122,213,534,214],"class_list":["post-754","post","type-post","status-publish","format-standard","hentry","category-commandline","category-powershell-v2-0","category-windows-7","category-windows-server","tag-functions","tag-invoke-command","tag-netstat","tag-powershell","tag-remote"],"yoast_head":"\nGet Your TCP Ports Here! • The Lonely Administrator<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Get Your TCP Ports Here! • The Lonely Administrator\" \/>\n<meta property=\"og:description\" content=\"Once again, the PowerShell forum at ScriptingAnswers.com has undone me. I was answering a question about running Netstat in a PowerShell session on a remote computer which got me thinking about a PowerShell function to turn NETSTAT.EXE output into objects. Once you have an object then you can do all sorts of things.\u00a0 Needless to...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/\" \/>\n<meta property=\"og:site_name\" content=\"The Lonely Administrator\" \/>\n<meta property=\"article:published_time\" content=\"2010-07-29T19:24:37+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2010\/07\/get-tcp-300x171.png\" \/>\n<meta name=\"author\" content=\"Jeffery Hicks\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@JeffHicks\" \/>\n<meta name=\"twitter:site\" content=\"@JeffHicks\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jeffery Hicks\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/commandline\\\/754\\\/get-your-tcp-ports-here\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/commandline\\\/754\\\/get-your-tcp-ports-here\\\/\"},\"author\":{\"name\":\"Jeffery Hicks\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"headline\":\"Get Your TCP Ports Here!\",\"datePublished\":\"2010-07-29T19:24:37+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/commandline\\\/754\\\/get-your-tcp-ports-here\\\/\"},\"wordCount\":947,\"commentCount\":2,\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"image\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/commandline\\\/754\\\/get-your-tcp-ports-here\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2010\\\/07\\\/get-tcp-300x171.png\",\"keywords\":[\"functions\",\"Invoke-Command\",\"Netstat\",\"PowerShell\",\"Remote\"],\"articleSection\":[\"CommandLine\",\"PowerShell v2.0\",\"Windows 7\",\"Windows Server\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/commandline\\\/754\\\/get-your-tcp-ports-here\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/commandline\\\/754\\\/get-your-tcp-ports-here\\\/\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/commandline\\\/754\\\/get-your-tcp-ports-here\\\/\",\"name\":\"Get Your TCP Ports Here! • The Lonely Administrator\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/commandline\\\/754\\\/get-your-tcp-ports-here\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/commandline\\\/754\\\/get-your-tcp-ports-here\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2010\\\/07\\\/get-tcp-300x171.png\",\"datePublished\":\"2010-07-29T19:24:37+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/commandline\\\/754\\\/get-your-tcp-ports-here\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/commandline\\\/754\\\/get-your-tcp-ports-here\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/commandline\\\/754\\\/get-your-tcp-ports-here\\\/#primaryimage\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2010\\\/07\\\/get-tcp.png\",\"contentUrl\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2010\\\/07\\\/get-tcp.png\",\"width\":\"1005\",\"height\":\"574\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/commandline\\\/754\\\/get-your-tcp-ports-here\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"CommandLine\",\"item\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/category\\\/commandline\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Get Your TCP Ports Here!\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/\",\"name\":\"The Lonely Administrator\",\"description\":\"Practical Advice for the Automating IT Pro\",\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\",\"name\":\"Jeffery Hicks\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"caption\":\"Jeffery Hicks\"},\"logo\":{\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Get Your TCP Ports Here! • The Lonely Administrator","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/","og_locale":"en_US","og_type":"article","og_title":"Get Your TCP Ports Here! • The Lonely Administrator","og_description":"Once again, the PowerShell forum at ScriptingAnswers.com has undone me. I was answering a question about running Netstat in a PowerShell session on a remote computer which got me thinking about a PowerShell function to turn NETSTAT.EXE output into objects. Once you have an object then you can do all sorts of things.\u00a0 Needless to...","og_url":"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/","og_site_name":"The Lonely Administrator","article_published_time":"2010-07-29T19:24:37+00:00","og_image":[{"url":"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2010\/07\/get-tcp-300x171.png","type":"","width":"","height":""}],"author":"Jeffery Hicks","twitter_card":"summary_large_image","twitter_creator":"@JeffHicks","twitter_site":"@JeffHicks","twitter_misc":{"Written by":"Jeffery Hicks","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/#article","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/"},"author":{"name":"Jeffery Hicks","@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"headline":"Get Your TCP Ports Here!","datePublished":"2010-07-29T19:24:37+00:00","mainEntityOfPage":{"@id":"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/"},"wordCount":947,"commentCount":2,"publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"image":{"@id":"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/#primaryimage"},"thumbnailUrl":"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2010\/07\/get-tcp-300x171.png","keywords":["functions","Invoke-Command","Netstat","PowerShell","Remote"],"articleSection":["CommandLine","PowerShell v2.0","Windows 7","Windows Server"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/","url":"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/","name":"Get Your TCP Ports Here! • The Lonely Administrator","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/#primaryimage"},"image":{"@id":"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/#primaryimage"},"thumbnailUrl":"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2010\/07\/get-tcp-300x171.png","datePublished":"2010-07-29T19:24:37+00:00","breadcrumb":{"@id":"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/#primaryimage","url":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2010\/07\/get-tcp.png","contentUrl":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2010\/07\/get-tcp.png","width":"1005","height":"574"},{"@type":"BreadcrumbList","@id":"https:\/\/jdhitsolutions.com\/blog\/commandline\/754\/get-your-tcp-ports-here\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"CommandLine","item":"https:\/\/jdhitsolutions.com\/blog\/category\/commandline\/"},{"@type":"ListItem","position":2,"name":"Get Your TCP Ports Here!"}]},{"@type":"WebSite","@id":"https:\/\/jdhitsolutions.com\/blog\/#website","url":"https:\/\/jdhitsolutions.com\/blog\/","name":"The Lonely Administrator","description":"Practical Advice for the Automating IT Pro","publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/jdhitsolutions.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9","name":"Jeffery Hicks","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","url":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","caption":"Jeffery Hicks"},"logo":{"@id":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg"}}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"jetpack-related-posts":[{"id":1483,"url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/1483\/test-port-2-0\/","url_meta":{"origin":754,"position":0},"title":"Test Port 2.0","author":"Jeffery Hicks","date":"May 31, 2011","format":false,"excerpt":"A few years ago I updated a PowerShell script I came across to scan a computer for open ports. My initial revision was aimed at making it more pipeline friendly in PowerShell v1.0. I recently needed to use the function for a project and realized it could benefit from a\u2026","rel":"","context":"In "PowerShell v2.0"","block_context":{"text":"PowerShell v2.0","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell-v2-0\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2011\/05\/test-port-300x126.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":3673,"url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/3673\/convert-text-to-object-with-powershell-and-regular-expressions\/","url_meta":{"origin":754,"position":1},"title":"Convert Text to Object with PowerShell and Regular Expressions","author":"Jeffery Hicks","date":"February 10, 2014","format":false,"excerpt":"A few weeks ago I was getting more familiar with named captures in regular expressions. With a named capture, you can give your matches meaningful names which makes it easier to access specific captures. The capture is done by prefixing your regular expression pattern with a name. PS C:\\> \"UNC\u2026","rel":"","context":"In "CommandLine"","block_context":{"text":"CommandLine","link":"https:\/\/jdhitsolutions.com\/blog\/category\/commandline\/"},"img":{"alt_text":"squarepattern","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/04\/squarepattern-150x150.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":7978,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7978\/deploy-openssh-to-windows-server\/","url_meta":{"origin":754,"position":2},"title":"Deploy OpenSSH to Windows Server","author":"Jeffery Hicks","date":"December 17, 2020","format":false,"excerpt":"Yesterday I shared some PowerShell ideas for remotely setting up the server component of ssh on a remote Windows 10 system. This would allow you to establish an ssh session to the desktop or even use PowerShell remoting over ssh. Next, we need to look at doing the same thing\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/12\/win2019-psssh.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/12\/win2019-psssh.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/12\/win2019-psssh.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/12\/win2019-psssh.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/12\/win2019-psssh.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/12\/win2019-psssh.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":7447,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7447\/get-installed-powershell-versions\/","url_meta":{"origin":754,"position":3},"title":"Get Installed PowerShell Versions","author":"Jeffery Hicks","date":"May 7, 2020","format":false,"excerpt":"As is the norm for a typical day, I was working on one thing when I was distracted by a shiny rabbit hole (to mix some metaphors). Half a day later I have a new PowerShell function that not only might you find useful, but I think it has some\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/get-psinstalled-result2.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/get-psinstalled-result2.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/get-psinstalled-result2.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/get-psinstalled-result2.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/get-psinstalled-result2.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/get-psinstalled-result2.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":7458,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7458\/a-powershell-remote-function-framework\/","url_meta":{"origin":754,"position":4},"title":"A PowerShell Remote Function Framework","author":"Jeffery Hicks","date":"May 8, 2020","format":false,"excerpt":"The other day I shared a PowerShell function to query the registry on remote computers to find installed versions of PowerShell. The function leveraged PowerShell remoting with the flexibility of using a computer name with an optional credential or existing PSSessions. The more I thought about it, the more I\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/stop-remoteprocess.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/stop-remoteprocess.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/stop-remoteprocess.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/stop-remoteprocess.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/stop-remoteprocess.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/stop-remoteprocess.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":8499,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/8499\/using-the-powershell-ise-as-a-remote-management-console\/","url_meta":{"origin":754,"position":5},"title":"Using the PowerShell ISE as a Remote Management Console","author":"Jeffery Hicks","date":"July 20, 2021","format":false,"excerpt":"Way back before the days of PowerShell Core, or even VS Code for that matter, the PowerShell ISE was the center of my PowerShell world. I spent a lot of time finding ways to make it easier for me to use and to push it to its limits. Naturally, the\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2021\/07\/ise-remotetab-form2.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/754","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/comments?post=754"}],"version-history":[{"count":0,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/754\/revisions"}],"wp:attachment":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=754"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=754"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=754"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}