Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On Windows 2003 Server, we have 2 network cards and it's easy to open different ports to the different network cards.

I'm trying to do the same on a Windows 2008 Server, I've discovered Windows Firewall with Advanced Security, but can't see where (or if) we can restrict the ports on the second network card. Is this possible?

share|improve this question
Could you use the NIC's IP or does it have to be the card itself? – squarebear May 11 '14 at 21:58

The Windows Firewall with Advanced Security in W2K8 doesn't bind to the individual network cards, per se. It binds to the network profile. If you want to set different rules per NIC then make sure to set each NIC to a different network type, such as private and public. Windows should automatically do this based on the ip address in use but for RFC 1918 addresses on a non-domain joined server I believe you can modify this.

share|improve this answer
Ugly. This makes sense for SBS or basic web-facing servers, but it is really frustrating to struggle with Mikeysoft wizards that are trying to be psychic network engineers :-/ – DutchUncle Feb 2 '11 at 1:26
Then do not use the wizards but learn the command line? – TomTom May 13 '14 at 18:29

The safest way I've found to go about this is to scope the firewall. Just add rules allowing only the local subnet to ports that need to be closed.

The network profile assignment is quite finicky and I have oftentimes seen the profiles change after a reboot causing issues. By scoping you avoid this as the rule will always properly apply.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.