ASP Developer Network - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com

ASPDeveloper

ASPDeveloper.Net / VirtualServerFAQ.COM

Make sure you go to our home page for:

* Virtual Server 2005 FAQ
* ASP.Net 2.0 Information
* ASP.Net 2.0 Streaming Tutorials
* ASP.Net 2.0 HTML based Tutorials

Made possible by Business Internet Technology Shop (BitShop)

Virtual Server 2005

Recent Virtual Server 2005 posts

* No connectivity between guest servers on the same host - part II (solution)
* Remote management in a Workgroup environment
* Setup New Virtual server
* Virtual Server Service Login - Run VM under User Account
* I cannot open VS administrator web site.
* "A network cable is unplugged"
* Virtual Server Service Login - Run VM under User Account (v.VS2005
* VM Guest Performance Ridiculously Slow...
* Hyper-V Networking Issue
* Event ID 12 and 57"s when dong P2V Script for live guest backup
* Huge Licensing Dilemma
* multiple nic
* Hyper V Network speed at 10Gbps - Can"t Access anything
* VM disappears
* Delayed Write Failures and disk errors
* Hyper-V and Vista x64 guest networking problem
* Licensing Question
* Virual PC 2007 CD burner
* Virtual network connection unplugged?
* When rebooting VM guest.. VM hangs in the bios screen / blank scre

Add Solution

Can"t configure virtual network connect to external

Source: microsoft.public.virtualserver
Sent: 04/22/2008
From: "Hii Sing Chung" <(email address - cut out)>
Message:

I am running Windows 2008 Enterprise x64 and had updated the Hyper-V to RC0.
The server is an HP Proliant DL360 G5 5110 (Xeon 2 Cores), 4GB RAM. I
configured teaming on the 2 Gigabit NIC (HP NC373i Multifunction Gigabit
Server Adapter). The Server (the host) has fixed IP address configured. In
Hyper-V the Virtual Network was default set up as "Private virtual machine
network". Whenever I changed it to External, and clicked OK or Apply, it
said "Apply Changes...." and would remains at this state forever. I left it
running for 2 weeks, it was still like that. I rebuilt the server from
scratch (re-created the RAID, re-install OS), when I reached the Virtual
Network Manager and configure the virtual network to External, click OK or
Apply, it went to the "Apply changes....." endless loop. I am stuck here.

Is this caused by the NIC teaming?

Any idea why?

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: Can"t configure virtual network connect to external

Sent: 04/22/2008
From: "Charlie Russel - MVP" <(email address - cut out)>
Message:

I'd agree with Ryan, this is probably from the NIC teaming. The issue is
that when you create an external network in Hyper-V, it removes the TCP/IP
stack from the NIC and replaces it with the "Microsoft Virtual Network
Switch Protocol", and creates a new network that has all the TCP/IP stuff on
it. Apparently that causes issues with the teamed adapter. (Note also that
you should always leave one network adapter free to connect to the parent
partition for management.)

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Hii Sing Chung" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

>I am running Windows 2008 Enterprise x64 and had updated the Hyper-V to
>RC0. The server is an HP Proliant DL360 G5 5110 (Xeon 2 Cores), 4GB RAM. I
>configured teaming on the 2 Gigabit NIC (HP NC373i Multifunction Gigabit
>Server Adapter). The Server (the host) has fixed IP address configured. In
>Hyper-V the Virtual Network was default set up as "Private virtual machine
>network". Whenever I changed it to External, and clicked OK or Apply, it
>said "Apply Changes...." and would remains at this state forever. I left it
>running for 2 weeks, it was still like that. I rebuilt the server from
>scratch (re-created the RAID, re-install OS), when I reached the Virtual
>Network Manager and configure the virtual network to External, click OK or
>Apply, it went to the "Apply changes....." endless loop. I am stuck here.
>
> Is this caused by the NIC teaming?
>
> Any idea why?

Re: Can"t configure virtual network connect to external

Sent: 04/22/2008
From: "Ryan Sokolowski [MVP]" <(email address - cut out)>
Message:

Break the NIC team and try this again.

--
Ryan Sokolowski
MVP - Clustering
MCSE, CCNA, CCDA, BCFP

"Hii Sing Chung" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

Re: Can"t configure virtual network connect to external

Sent: 04/22/2008
From: "Charlie Russel - MVP" <(email address - cut out)>
Message:

The problem is that the Microsoft Virtual Switch protocol has been enabled
on those switches. And once that happens, it's a bit of a nuisance getting
them sorted. I just had to do this on a machine (for a different reason, but
same process.) To resolve it, I did the following:

1.) deleted all external networks using the Hyper-V Network Manager
2.) Went in to Device Manager and uninstalled the adapters
3.) Rebooted, letting Windows re-create the adapters.
4.) Re-created the external network using the Hyper-V Network Manager
5.) Fixed the "configuration error" for all VMs that were attached to those
networks by detaching the network, and then re-attaching to the new switch.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Hii Sing Chung" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

>I broke the team, restarted. When I tried to configure virtual network as
>external, press Apply, it says "Error Applying New Virtual Network Changes.
>Setup switch failed. The switch could not bind to HP NC373i Multifunction
>Gigabit Server Adapter because it is already bound to another switch." I
>tried the second network card, it was the same result. What is the 'switch'
>refer to? What is the 'bind' about?
>
> "Ryan Sokolowski [MVP]" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Break the NIC team and try this again.
>>
>> --
>> Ryan Sokolowski
>> MVP - Clustering
>> MCSE, CCNA, CCDA, BCFP
>>
>> "Hii Sing Chung" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>>I am running Windows 2008 Enterprise x64 and had updated the Hyper-V to
>>>RC0. The server is an HP Proliant DL360 G5 5110 (Xeon 2 Cores), 4GB RAM.
>>>I configured teaming on the 2 Gigabit NIC (HP NC373i Multifunction
>>>Gigabit Server Adapter). The Server (the host) has fixed IP address
>>>configured. In Hyper-V the Virtual Network was default set up as "Private
>>>virtual machine network". Whenever I changed it to External, and clicked
>>>OK or Apply, it said "Apply Changes...." and would remains at this state
>>>forever. I left it running for 2 weeks, it was still like that. I rebuilt
>>>the server from scratch (re-created the RAID, re-install OS), when I
>>>reached the Virtual Network Manager and configure the virtual network to
>>>External, click OK or Apply, it went to the "Apply changes....." endless
>>>loop. I am stuck here.
>>>
>>> Is this caused by the NIC teaming?
>>>
>>> Any idea why?
>>
>
>

Re: Can"t configure virtual network connect to external

Sent: 04/23/2008
From: "Charlie Russel - MVP" <(email address - cut out)>
Message:

Good, glad it got you working.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Hii Sing Chung" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Right, uninstall all the network adapters, re-start. That did the trick.
>
> "Charlie Russel - MVP" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> The problem is that the Microsoft Virtual Switch protocol has been
>> enabled on those switches. And once that happens, it's a bit of a
>> nuisance getting them sorted. I just had to do this on a machine (for a
>> different reason, but same process.) To resolve it, I did the following:
>>
>> 1.) deleted all external networks using the Hyper-V Network Manager
>> 2.) Went in to Device Manager and uninstalled the adapters
>> 3.) Rebooted, letting Windows re-create the adapters.
>> 4.) Re-created the external network using the Hyper-V Network Manager
>> 5.) Fixed the "configuration error" for all VMs that were attached to
>> those networks by detaching the network, and then re-attaching to the new
>> switch.
>>
>> --
>> Charlie.
>> http://msmvps.com/blogs/xperts64
>> http://mvp.support.microsoft.com/profile/charlie.russel
>>
>>
>> "Hii Sing Chung" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>>I broke the team, restarted. When I tried to configure virtual network as
>>>external, press Apply, it says "Error Applying New Virtual Network
>>>Changes. Setup switch failed. The switch could not bind to HP NC373i
>>>Multifunction Gigabit Server Adapter because it is already bound to
>>>another switch." I tried the second network card, it was the same result.
>>>What is the 'switch' refer to? What is the 'bind' about?
>>>
>>> "Ryan Sokolowski [MVP]" <(email address - cut out)> wrote in message
>>> news:(email address - cut out)...
>>>> Break the NIC team and try this again.
>>>>
>>>> --
>>>> Ryan Sokolowski
>>>> MVP - Clustering
>>>> MCSE, CCNA, CCDA, BCFP
>>>>
>>>> "Hii Sing Chung" <(email address - cut out)> wrote in message
>>>> news:(email address - cut out)...
>>>>>I am running Windows 2008 Enterprise x64 and had updated the Hyper-V to
>>>>>RC0. The server is an HP Proliant DL360 G5 5110 (Xeon 2 Cores), 4GB
>>>>>RAM. I configured teaming on the 2 Gigabit NIC (HP NC373i Multifunction
>>>>>Gigabit Server Adapter). The Server (the host) has fixed IP address
>>>>>configured. In Hyper-V the Virtual Network was default set up as
>>>>>"Private virtual machine network". Whenever I changed it to External,
>>>>>and clicked OK or Apply, it said "Apply Changes...." and would remains
>>>>>at this state forever. I left it running for 2 weeks, it was still like
>>>>>that. I rebuilt the server from scratch (re-created the RAID,
>>>>>re-install OS), when I reached the Virtual Network Manager and
>>>>>configure the virtual network to External, click OK or Apply, it went
>>>>>to the "Apply changes....." endless loop. I am stuck here.
>>>>>
>>>>> Is this caused by the NIC teaming?
>>>>>
>>>>> Any idea why?
>>>>
>>>
>>>
>>
>

Re: Can"t configure virtual network connect to external

Sent: 04/23/2008
From: "Hii Sing Chung" <(email address - cut out)>
Message:

I broke the team, restarted. When I tried to configure virtual network as
external, press Apply, it says "Error Applying New Virtual Network Changes.
Setup switch failed. The switch could not bind to HP NC373i Multifunction
Gigabit Server Adapter because it is already bound to another switch." I
tried the second network card, it was the same result. What is the 'switch'
refer to? What is the 'bind' about?

"Ryan Sokolowski [MVP]" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Break the NIC team and try this again.
>
> --
> Ryan Sokolowski
> MVP - Clustering
> MCSE, CCNA, CCDA, BCFP
>
> "Hii Sing Chung" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>>I am running Windows 2008 Enterprise x64 and had updated the Hyper-V to
>>RC0. The server is an HP Proliant DL360 G5 5110 (Xeon 2 Cores), 4GB RAM. I
>>configured teaming on the 2 Gigabit NIC (HP NC373i Multifunction Gigabit
>>Server Adapter). The Server (the host) has fixed IP address configured. In
>>Hyper-V the Virtual Network was default set up as "Private virtual machine
>>network". Whenever I changed it to External, and clicked OK or Apply, it
>>said "Apply Changes...." and would remains at this state forever. I left
>>it running for 2 weeks, it was still like that. I rebuilt the server from
>>scratch (re-created the RAID, re-install OS), when I reached the Virtual
>>Network Manager and configure the virtual network to External, click OK or
>>Apply, it went to the "Apply changes....." endless loop. I am stuck here.
>>
>> Is this caused by the NIC teaming?
>>
>> Any idea why?
>

Re: Can"t configure virtual network connect to external

Sent: 04/23/2008
From: "Hii Sing Chung" <(email address - cut out)>
Message:

Right, uninstall all the network adapters, re-start. That did the trick.

"Charlie Russel - MVP" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> The problem is that the Microsoft Virtual Switch protocol has been enabled
> on those switches. And once that happens, it's a bit of a nuisance getting
> them sorted. I just had to do this on a machine (for a different reason,
> but same process.) To resolve it, I did the following:
>
> 1.) deleted all external networks using the Hyper-V Network Manager
> 2.) Went in to Device Manager and uninstalled the adapters
> 3.) Rebooted, letting Windows re-create the adapters.
> 4.) Re-created the external network using the Hyper-V Network Manager
> 5.) Fixed the "configuration error" for all VMs that were attached to
> those networks by detaching the network, and then re-attaching to the new
> switch.
>
> --
> Charlie.
> http://msmvps.com/blogs/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
>
> "Hii Sing Chung" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>>I broke the team, restarted. When I tried to configure virtual network as
>>external, press Apply, it says "Error Applying New Virtual Network
>>Changes. Setup switch failed. The switch could not bind to HP NC373i
>>Multifunction Gigabit Server Adapter because it is already bound to
>>another switch." I tried the second network card, it was the same result.
>>What is the 'switch' refer to? What is the 'bind' about?
>>
>> "Ryan Sokolowski [MVP]" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> Break the NIC team and try this again.
>>>
>>> --
>>> Ryan Sokolowski
>>> MVP - Clustering
>>> MCSE, CCNA, CCDA, BCFP
>>>
>>> "Hii Sing Chung" <(email address - cut out)> wrote in message
>>> news:(email address - cut out)...
>>>>I am running Windows 2008 Enterprise x64 and had updated the Hyper-V to
>>>>RC0. The server is an HP Proliant DL360 G5 5110 (Xeon 2 Cores), 4GB RAM.
>>>>I configured teaming on the 2 Gigabit NIC (HP NC373i Multifunction
>>>>Gigabit Server Adapter). The Server (the host) has fixed IP address
>>>>configured. In Hyper-V the Virtual Network was default set up as
>>>>"Private virtual machine network". Whenever I changed it to External,
>>>>and clicked OK or Apply, it said "Apply Changes...." and would remains
>>>>at this state forever. I left it running for 2 weeks, it was still like
>>>>that. I rebuilt the server from scratch (re-created the RAID, re-install
>>>>OS), when I reached the Virtual Network Manager and configure the
>>>>virtual network to External, click OK or Apply, it went to the "Apply
>>>>changes....." endless loop. I am stuck here.
>>>>
>>>> Is this caused by the NIC teaming?
>>>>
>>>> Any idea why?
>>>
>>
>>
>

Post Reply | This is Spam! | Mark as Spam

Other groups

Virtual PC (Mac)(3592)	Virtual PC(12844)	Virtual PC (French)(496)
Virtual Server 2005(6245)

Our Sponsors

Virtual Server 2005 Info Here!
http://www.aspdeveloper.net

Wiki

Blogs

Articles

Image galleries

File galleries

Forums

Maps

Directories

ASP Developer Network (since 1996) - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com
Copyright © 1997-2005 by BitShop, Inc. All Rights Reserved.
No content may be reproduced in any form without written permission from BitShop, Inc.
We will be honored to assist with reproduction rights on our material if you contact us.
We also can provide print articles for your magazine, private training seminars at your site, and conference presentations.
Thank you for visiting. Please bookmark our site if you found it useful!
If you wish to make a donation it will help further the development of these free resources: