Vista - I cannot add a physical switch between Win Server 2008 and corp Ne

Hyper-V is great tool that I has been using for a while. Originally, my
Windows Server 2008 with Hyper-V is connected directly to the corp net.
Recently, I added a switch between the corp net and my Windows Server 2008
server. (That is Windows Server 2008 connects to the switch, the switch
connects to the corp net).

Now a problem comes up. When I started Windows Server 2003 VMs, the VMs got
192.168... IP address, although the network I designate to the VMs is
connected to the physical NIC.

Additionally, when I try to create a new network that is connected to the
physical NIC, I receive an error message: "The switch could not bind to
Broadcom NetXtreme 57xx Gigabit Controller because it is already bound to
another switch".

According to the error message, my physical NIC is bound to the physical
switch that I added, which is now allowed. However, I also found that this
problem does not occur for Windows Server 2008 VMs. Windows Server 2008 VMs
can obtain the appropriate IP address.

Any ideas how I can make Windows Server 2003 VMs get workable IP addresses?
Thanks!

Why not just set each VM to a static IP and not try to obtain an IP (if I am
understanding what your are saying). Also, if you are using DHCP, what's
handing out these IPs?
--
MCP, MCSA, MCSE+Security, CEH, CCA


"Felix_Jiang" wrote:

Why are you trying to create an additional network? If there is already a
virtual switch linked to the physical NIC, simply connect your vms to it.
They will behave as if they are connected to the physical network.

As Jeremy suggested, try using a manual config if DHCP is failing.