Should my server have one or two NICs?

Should my server have one or two NICs?

My coworkers and I have had the debate on one of the most common topics about network/server security: "Should a server have one or two NICs? And, what are the pros and cons of having one or two (OS independent, Windows, Unix, Linux)?

    Requires Free Membership to View

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Well, that depends upon what you are trying to do with that server. If it's simply a stand-alone application server that's part of a LAN, then there is no reason for a second NIC. If you're trying to make a server part of two different LANs, I prefer dual-homing using two separate NICs (with two separate sets of address space for each LAN, and no routing within the server) rather than trying to separate them only by using VLANs. However, the sensitivity of the data being processed by the system should be used to guide your decision.

This was first published in September 2004