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 running VMware Server 2.0.2 with 2 VM's. One of the VM's I want to have bridged with the domain/primary NIC of the host which I have done successfully. I want the other VM to have access to only the other NIC on the host which is wired directly to the hardware firewall/gateway with a DMZ dedicated to that port. The purpose of this is to have the VM segregated from the domain network because it is going to be a web server. I am having troubles configuring the VM so that it only has access to the DMZ'd NIC. I have a dedicated IP address from our provider that I can use to staticly assign either the VM or the NIC on the host which I want DMZ'd to the VM.

What other information would be useful to help me?

Is there a more practical/secure way to do this?

Here's a diagram:network diagram

share|improve this question
Serverfault is for professional sysadmins, perhaps superuser would be a better place for this as VMWare Server isn't really used in professional environments. – Chopper3 Jun 8 '12 at 17:35
This was an unexpected project. If it was up to me I would have purchased ESXi but it's too late for that now :P. Should I let this sit here for a little bit then try to migrate the question? -- I am biting my tongue now.. apparently ESXi is free? Someone told me it only had a 60 day trial.. going to look into this now. – qroberts Jun 8 '12 at 17:38
ESXi "base" is free, and should be all you need. You can easily achieve this separation in ESXi by using two different vSwitches each using different physical NICs. – Jeremy Jun 8 '12 at 18:20
Don't use VMware Server. It's old and end of life. – Shane Madden Jun 8 '12 at 23:43
up vote 2 down vote accepted

it's better to use two firewalled routers for a real DMZ .. this is more an "exposed router" setup ;)

There isn't a big difference in the overall technical setup between VMWare Server and ESXi - which is called VMware vSphere Hypervisor now. If you comply with the hypervisor hardware requirements you should use it instead of VMWare Server.

Check the compatibility guide first:

You may add IPs/ranges to your scheme e.g DMZ and LAN Will use these two networks from now on.

As for the VMWare Server 2.0.2 setup, you may like to rename the existing two physical NICs according to your scheme via windows network center; then start the "VMWare Virtual Network Editor" Application and

  • Remove all interfaces from automatic bridging
  • Assign the two NICs in the "Host Virtual Network Mapping" tab, e.g VMnet1 for DMZ & VMnet2 for LAN access
  • Deactivate/Stop DHCP & NAT services

As you wrote, you already connected the first NIC to your LAN + configured the physical server for LAN access. Check that if your 2nd NIC for virtual DMZ access has DHCP config activated change it to a static configuration (e.g. here; an unused ip range).

Assign the configured virtual LAN interfaces to the two virtual machines via the "VMware Server Home Page" according to your network mappings, eg. vm01 gets vmnet1, vm02 gets vmnet2.

Startup your VM01 host and setup the static IP configuration, e.g with gateway, if your Firewall has

Your public IP is assigned to the WAN interface of your firewall. The DMZ port of your firewall is connected to the server NIC1/vmnet1 an gets the (internal) ip, the LAN port the ip to the network switch.

You may activate a DHCP server for the LAN port. All LAN/domain devices now use as Gateway and receive an ip from range if DHCP is active.

If you like to add an additional LAN server, just connect it to your lan connection vmnet2.

Is it working? ;)

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.