Go Back   PackageDeploy Application Packaging Forums > Virtualization > Microsoft Virtual Server (Hyper-V)

Reply
 
LinkBack Thread Tools Display Modes
Old 10-06-2011, 04:20 PM   #1 (permalink)
Enzo Bastianello
Guest
 
Posts: n/a
Default Re: Can't configure virtual network connect to external

Great... now it work fine

> On Tuesday, April 22, 2008 5:45 AM Hii Sing Chung wrote:


> 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?



>> On Tuesday, April 22, 2008 9:56 AM Ryan Sokolowski [MVP] wrote:


>> Break the NIC team and try this again.
>>
>> --
>> Ryan Sokolowski
>> MVP - Clustering
>> MCSE, CCNA, CCDA, BCFP



>>> On Tuesday, April 22, 2008 10:24 AM Charlie Russel - MVP wrote:


>>> 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" <singchung@sgintracod.com> wrote in message
>>> news:AA40862C-5584-4F59-947D-D0508EF103BB@microsoft.com...



>>>> On Wednesday, April 23, 2008 12:09 AM Hii Sing Chung wrote:


>>>> 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]" <ryan@clustering101.com> wrote in message
>>>> news:E4994088-5DE5-4D29-A492-AD67EE3E2B42@microsoft.com...



>>>>> On Wednesday, April 23, 2008 1:03 AM Charlie Russel - MVP wrote:


>>>>> 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" <singchung@sgintracod.com> wrote in message
>>>>> news:97BE4A3B-589A-4697-9D60-E99F37501207@microsoft.com...



>>>>>> On Wednesday, April 23, 2008 3:48 AM Hii Sing Chung wrote:


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



>>>>>>> On Wednesday, April 23, 2008 10:45 AM Charlie Russel - MVP wrote:


>>>>>>> Good, glad it got you working.
>>>>>>>
>>>>>>> --
>>>>>>> Charlie.
>>>>>>> http://msmvps.com/blogs/xperts64
>>>>>>> http://mvp.support.microsoft.com/profile/charlie.russel




  Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 09:17 PM.


vBulletin, Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
2007 - 2012 PackageDeploy.com