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 have an (virtual) internal Win 2008 R2 Server as a DC and also running Exchange 2010.

I have one NIC configured. However I have seen set-ups where one NIC is configured for external and another NIC is configured for internal.

Can someone point out to me the benefits of this (if any) and also point me in the way of further information on this?

share|improve this question
I think you're far enough from Best Practices already, no need to put your DC on the web. – Chris S Jan 17 '12 at 23:20
I know this... it's a play box that I'm learning on. Thanks for your excellent comment though, I very much appreciate your time :) and helpful guidance. – Paul Brown Jan 17 '12 at 23:34

I've had multiple NICs for host servers, where there will be several virtual servers running inside. I can assign separate nics to individual servers and improve network performance this way.

I've also seen multiple NICs in a fail-over situation, where the switch port for one nic is disabled, but can come online automatically if a failure is sensed in the other connection.

I have a server with one NIC facing the external network, another facing the internal network, and another facing a dmz, but this server is my gateway and firewall. It does things like virus protection at the edge for the rest of our internal network. It is not my domain controller.

I have not seen a DC placed on the public internet, but maybe I've just lived a sheltered life.

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.