On Windows XP and Windows Server 2003, I can know currently open ports on the Windows Firewall using the following command:
netsh firewall show state
However, on Windows 7 and Hyper-V Server 2008 R2, when I give that command, it says:
No ports are currently open on all network interfaces.
IMPORTANT: Command executed successfully.
However, "netsh firewall" is deprecated;
use "netsh advfirewall firewall" instead.
Apparently there are ports open because services such as NetBIOS NS, Remote Desktop, and Hyper-V remote administration are functioning.
I tried a few 'netsh advfirewall' show commands, but didn't get a way to find out which ports are permit by Windows Firewall.
Knowing the currently open ports, I can be sure that I'm permitting necessary and sufficient traffic to pass in, no more, no less.
Going through the whole set of advanced firewall rules is so tedious and error-prone.
Is there a command on Windows 7 and Windows Server 2008 to do this efficiently?
The reason you can't get the same results using the same commands is that the Win7 firewall rules can be specific to an individual application, and configured per network type (Private, Domain, Public), protocol, port, etc. Powershell should give you a much better way to query this information and sort it. Here's a quick script I have to dump my configuration, when I need it.
A lot of this was based off of this post on MSDN