how to create multiple VLAN in Windows 2003

[Mahesh]

Hi,

We are istalling 4 Virtual Server of Windows 2003 on base machine of Windows
2003 and wanted configure all 4 virtual machine in different VLAN, hence
wanted to configure 4 VLAN in Windows 2003 OS where Server is having INtelPro
Network adaptor. Request you pls help to configure multiple VLAN in Windows
2003 for IntelPro Network card.Below is the link of Intel NIC given by
hardware vendor.

http://support.intel.com/support/net.../cs-009715.htm

Thanks in advance and hoping for possitive result.

Thanks and Regards
Mahesh

[Bill Grant]

The NICs in the virtual machines will not be Intel NICs. The NICs will be
emulated. What type of emulated NIC is in the vm depends on what you are
using for virtualization (Virtual Server, VMWare, Hyper-V or whatever).

Hyper-V is VLAN aware. What this means is that, if you are running VLANs
on your physical network, the virtual machines will recognize the VLAN tags,
so you can link different vms to different VLANs. It does not mean that you
can create VLANs on the virtual switch. But if you are running on Server
2003 you are not using Hyper-V.

Did you really mean VLAN, or do you simply want to put each virtual
server in a different network? If that is what you need, simply create four
different virtual networks and put on vm in each.

[Mahesh]

We wanted configure 4 different VLAN in base machine, we have network
adapter in Teaming.The Teamed Network adaptor should be able to work as a
trunk port....

is it possible?

[Phillip Windell]

I'm just thinking "out loud" here (or I guess "in writing"? :-) )

If you are talking about Virtualization,...the Parent machine doesn't even
need to have the nic fully configured or even functional beyond just the
hardware and the driver.

With the MS virtualization (VPC, VirtualServer, hyper-V) you can even remove
TCP/IP completely and unbind all other things from the Nic and the VMS will
still work. With hyper-V I believe you can even disable the "connection" in
Network Places as long as you do it after the VM is configured.

So if your LAN's infastructure allows all of the required VLANs to use the
same switch port that the physical Parent machine is connected into,...then
the VMs should all work by simply giving then the TCP/IP specs they are
supposed to have and then just associate all of them with the same physical
nic on the Parent.

The Parent machine itself would be effectively "dead" on the network without
TCP/IP even being on the Nic (which is the proper way things should be)
while the VMs that run on the Parent run just fine. This is the
"stituation" that MS recommends in the Hyper-V videos I saw, particularly if
a proxy or firewall product was being used on one of the VMs (like maybe ISA
Server or TMG).

[Bill Grant]

To expand a bit on what Phillip said. The networking in Hyper-V is VLAN
"aware" but it is not VLAN "capable". What this effectively means is much
along the lines Phillip outlined. If your physical network is configured to
use VLANs, you can use just one NIC of the host machine for your virtual
machines and have them linked to different VLANs. The virtual switch will
recognize the VLAN tags and handle things correctly.

What you cannot do is use the virtual switch to configure VLANs. You
must have a device on the physical LAN which is VLAN capable to set up the
VLANs.