> When you enable the second NIC, you would connect the vm to the
> virtual network linked to that NIC.
> On the host, you would disable VMNS on the first network card (so that
> it was not accessible from a VM). On the second NIC you would disable
> everything except VMNS (so that only the vm could access the network).

> When you enable the second NIC, you would connect the vm to the
> virtual network linked to that NIC.
> On the host, you would disable VMNS on the first network card (so that
> it was not accessible from a VM). On the second NIC you would disable
> everything except VMNS (so that only the vm could access the network).

> I have two network feeds and operate DNS on both. Each is a totally
> separate and unique feed -- different routers, IP space, etc. I'd like to
> virtual the DNS server on the secondary as a VM running on a host machine
> that sits on the primary network.
>
> The server has 2 NICs (it's a PowerEdge 2650) and I'm not using the second
> NIC, so I could just as easily plug that into the secondary network.
>
> Is this a doable thing? I don't want to create any routing issues for the
> physical box and I know W2K3E doesn't particularly play well with mixed
> network segments like that.

> I suggest that you re-read what I wrote and think about it. How would it
> possibly work if the NIC was disabled? What you are doing is isolating
> the NIC from the IP stack on the host but allowing it to see the IP
> stack in the guest(s).

>
>> I suggest that you re-read what I wrote and think about it. How would it
>> possibly work if the NIC was disabled? What you are doing is isolating
>> the NIC from the IP stack on the host but allowing it to see the IP
>> stack in the guest(s).
>
>This is what I'm not getting. I have 2 physical NICs in the box, each
>connected to a different network segment. NIC 1 has VMs as well as the
>host itself; NIC 2 would need to be isolated from the host but available
>to the VMs.
>
>I guess the real question here is how do I isolate NIC 2 from the host
>while still having it available to the VMs? I understand the concept of
>creating the virtual network but isolating it is where I'm not seeing
>the light on this one. I think I just don't understand what's attached
>to the NICs and what to disable.

>> It seems a strange thing to do, but it is possible.
>
> Strange why...?
>
>> When you enable the second NIC, you would connect the vm to the virtual
>> network linked to that NIC.
>
> Does the NIC have to be configured on the host? Can it be disabled in the
> host's OS or just given a dummy address? I want to ensure the host does
> NOT attempt to route over it.
>
>> On the host, you would disable VMNS on the first network card (so that
>> it was not accessible from a VM). On the second NIC you would disable
>> everything except VMNS (so that only the vm could access the network).
>
> I wouldn't want to do that, would I? I have other VMs on this host that
> route over the first NIC.
>
> James

> Just unchecking TCP in the NIC properties for the second NIC would
> make it so the host couldn't access it. (assuming it's TCP only)
>
> --
> Bob Comer
>
>

>
>
> "Robert Comer" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Just unchecking TCP in the NIC properties for the second NIC would
>> make it so the host couldn't access it. (assuming it's TCP only)
>>
>> --
>> Bob Comer
>>
>>
> To expand on what Bob said, look closely at the options you see in the
> NIC properties from the host OS. This is where you control what happens.
>
> To allow a vm to access the network through this NIC, all you need is
> VMNS (Virtual Machine Network Services). This is the code which works with
> the NIC driver to allow the virtual machines to access the physical LAN.
>
> As long as VMNS is checked, you can clear the check marks in all the
> other boxes. These refer to how the host machine uses the NIC. If you
> clear them, the host cannot use the NIC at all. No traffic on the network
> is transferred to the IP stack of the host.
>
> Traffic on the LAN which is addressed to the vm will still be accepted by
> the NIC and processed by the IP stack in the OS running in the vm. It will
> no be seen by the OS running on the host.
>