I'm configuring our new Windows Server 2008 machine. In Windows Server 2003 we would enable TCP/IP Filtering on our network cards to only allow traffic on specific ports to get through. This was done by right clicking on the network connection, and selecting properties. Then, selecting "Internet Protocol (TCP/IP)" and clicking properties. Next, click Advanced and select the options tab. In optional settings there was TCP/IP filtering. Select, TCP/IP filtering and click Properties.
In the TCP/IP Filtering window you could permit traffic only on certain ports. The Options tab no longer exists in Windows Server 2008. I have searched Google and TechNet, but can't seem to find where they hid it or what the replacement for these settings would be. Does anyone know where these settings are in Windows Server 2008? Is the Windows Firewall as close as I'm going to get? Is the Windows Firewall just as reliable as the old settings I used to use?
Best Answer
Based on my Googling, here is what I've found:
Both TCP\IP Filtering and the Windows Firewall up to Windows XP were bound to a specific NIC. Regardless of what type of network the computer was connected to, the filtering and firewall were either on or off. This is effective, but not intelligent.
In Vista, 7, and W2K8 the firewall is bound to a specific network profile, not to a NIC. So now it's possible to have different firewall rules and conditions applied to every network adapter or to specific network adapters based on the type of network the computer is connected to. For instance, You can allow incoming HTTP connections to your wireless NIC when you're connected to a private network, but not when you're connected to a public network. You can allow incoming FTP connections to your ethernet NIC when you're connected to a public network but not when you're connected to a private network. Etc., etc. Much more intelligent and much more granular control.