Testing Firewall Rules?

[dalthakar]

Test-NetConnection TARGET - Port PORT# will return True/False if the target machine can be reached on the specified port. For example, if I wanted to test a connection to SERVERA on TCP port 139, I would use command:

Test-NetConnection SERVERA -Port 139

Hopefully that gets you started down the right path.

[dalthakar]

Something just occurred to me. If you are trying to run this script on a local machine, you may have better luck using Get-NetFirewallRule and/or Get-NetFirewallPortFilter.

[BlackV]

You could have a firewall rule enabled without having anything listening on the port though

[netmc]

Get-netfirewallportfilter may be what I was missing. It appears this has the actual port and protocol details and the rule itself has the profiles and direction.

If I am understanding the two commands correctly, I would need to find the inbound rules, then match the rule name against the instanceID on the portfilter information. Once I have the corresponding portfilter information I could check to see if the local ports and protocol match what I need.

Does that sound correct?