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 got in to Server 2008 R2 via Dreamspark and would like to start learning on it.

I don't have much option but to put it on a system sitting between the Internet and my home LAN due to electricity bills and the fact that 3 computers in an 11x11 space in 102 degree weather is pretty stygian.

Currently I use a ClearOS gateway to manage everything, what I'd like to do is take my server 2008 R2 box, which has two NICs, and drop it at the head of my network. I'd want Server 2008 R2 to ignore all traffic on the external facing NIC and pass it to a virtual ClearOS gateway, and to put all its Internet traffic through its other NIC - which will face the rest of my network and be the default gateway for it.

The theory is to keep the potentially vulnerable Server 2008 R2 install as tucked behind a Linux box as possible, without sacrificing too much performance. This is a home network that occasionally hosts dedicated game servers and voice chat servers, so most malicious activity is in the form of drive by non-targeted attacks, however, I don't trust Windows Server because I don't know the OS well enough, yet.

So, three questions: How do I do this, am I going to be reasonably more secure doing this than if I just let the Server 2008 R2 rig handle all the network traffic and DHCP (not an option), and should I virtualize the Server 2008 R2 rig instead and if so in what? (Core 2 Duo e6600 w/ 5 gigs usable RAM)

share|improve this question

closed as off topic by EEAA, mgorven, Tim Brigham, sysadmin1138 Sep 29 '12 at 18:55

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

Are you sure you're required to put it on the internet and not a internet accessible LAN? Why can't you put it on a switch right behind the ClearOS gateway? The only reason to set it up as you suggest is for dual homing. The answer to your question is to install VMWare ESXi on the server. Configure the management to be on the second internal NIC. Configure both interfaces to be separate virtual switches. Install W2k8 server in a VM and route it however you feel comfortable for your project. – jfalcon Jun 8 '12 at 4:26
whats with the -ive votes? – Aceth Jun 8 '12 at 19:42
This cannot be put on a switch behind the clearOS gateway because I cannot have that many physical systems on in a home environment. My total power draw is enough that with three systems on if, for some reason, all end up on a heavy load while I have my speakers and monitors on, I'll throw the breakers. – Wolvenmoon Jun 8 '12 at 22:27
@Aceth: It attracted negative votes because questions about home computer and home network setups are off-topic here (see the FAQ). The question should have been asked on SuperUser. – Starfish Sep 29 '12 at 18:48
@Starfish - It's still a server related issue, which is what I thought this site was about? – Aceth Nov 29 '12 at 14:08
up vote 0 down vote accepted

I've already set this sort of thing in similar places! I'm glad someone else thinks like me! :D

Nope you can keep the server 2008 R2 as is! then ... on the NIC thats internet facing .. in the properties disable all the protocols apart from the VM bridging (hyperv / vmware / virtualbox) then in the virtual machine bridge the NIC to that internet facing NIC.. job done the server 2008 R2 will now ignore everything coming in / out on that interface :)

share|improve this answer
Awesome, this answers my question and then some. I didn't realize the various VM tools used their own protocols to interact with hardware NICs. – Wolvenmoon Jun 8 '12 at 22:38

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