Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

I am setting up a Windows Server 2008 R2 lab environment in VMWare workstation and attempting where possible to use Windows Server 2008 R2 to implement machines that serve specific roles within that environment. Using the "Network Policy and Access Services" role I have been able to setup a machine that can server as a NAT router. The issue is that any and all connections are allowed outbound. Is there a way to restrict what outbound connections are allowed?

share|improve this question
up vote 0 down vote accepted

You can control outbound connections from the server itself using Windows Firewall with AS.

You can't control the outbound connections from NAT'ed clients with a third party system:

Bottom line is, if you need a firewall product capable of filtering traffic as it is being routed between different NICs on the server, you need to install Microsoft Forefront Threat Management Gateway 2010.

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.