Source of Hyper-v VM configuration
I exported my Lab's Domain controller installed on windows 2008 R2 Hyper-v VM (2008 R2) running all the DNS and FSMO role, to a folder on a new Hyper-V Server (win 2008 R2).
Turned off the old machine , imoprted the VM into new server, added a new virtual adapter with external access and started the server.
No issues with Domain controller doing its functions (all dns resolution and AD functions are working OK)
However when I tried to change the network IP address to the same IP as before, I get a message
"The IP adress 192.168.1.127 you have entered for this network adapter is already assigned to another adapter (Microsoft Virtual Machine Bus Network
Adapter) which is no longer present in the computer, only one of them will use the address. ......." I ignored the message and changed the IP and all seem to be working.I fished for networking data in config.xml <source type= ....> </source> which is still showing the location from the old machine. &
the B867DCF8-1507-4CD8-A367-46BDE75C914D.exp and in the VM's windows registry but could not come up with any thing.Where is the source for the message and do I need to worry about it (I am running my CA-root on the machine)?
EMAIL REMOVED- Edited byjaytaba Thursday, October 08, 2009 11:53 PMadditional info
Answers
- The message comes from the OS, not from Hyper-V. You get the same message on a physical machine if you install a new NIC without removing the old one. The OS warns you that the previous NIC already has this IP. It would cause problems if two NICs had the same IP. If you don't ever plan to re-activate the old NIC it won't cause you any problems. If it worries you, you can remove the old NIC from device manager.
Bill- Marked As Answer byBrianEhMVP, ModeratorFriday, October 09, 2009 2:25 PM
- Marked As Answer byjaytaba Friday, October 09, 2009 9:31 PM
- Unmarked As Answer byjaytaba Friday, October 09, 2009 7:36 PM
- Unproposed As Answer byjaytaba Friday, October 09, 2009 6:03 AM
- Proposed As Answer byVincent HuMSFT, ModeratorFriday, October 09, 2009 2:49 AM
Hello,
Here is how you remove the old NIC.
http://support.microsoft.com/kb/269155
I hope this helps you out.
Nathan Lasnoski- Proposed As Answer byNathan Lasnoski Friday, October 09, 2009 3:14 AM
- Marked As Answer byjaytaba Friday, October 09, 2009 7:35 PM
All Replies
- The message comes from the OS, not from Hyper-V. You get the same message on a physical machine if you install a new NIC without removing the old one. The OS warns you that the previous NIC already has this IP. It would cause problems if two NICs had the same IP. If you don't ever plan to re-activate the old NIC it won't cause you any problems. If it worries you, you can remove the old NIC from device manager.
Bill- Marked As Answer byBrianEhMVP, ModeratorFriday, October 09, 2009 2:25 PM
- Marked As Answer byjaytaba Friday, October 09, 2009 9:31 PM
- Unmarked As Answer byjaytaba Friday, October 09, 2009 7:36 PM
- Unproposed As Answer byjaytaba Friday, October 09, 2009 6:03 AM
- Proposed As Answer byVincent HuMSFT, ModeratorFriday, October 09, 2009 2:49 AM
Hello,
Here is how you remove the old NIC.
http://support.microsoft.com/kb/269155
I hope this helps you out.
Nathan Lasnoski- Proposed As Answer byNathan Lasnoski Friday, October 09, 2009 3:14 AM
- Marked As Answer byjaytaba Friday, October 09, 2009 7:35 PM
Thanks for the great clue, I downloaded the devcon and ran the "Devcon findall =net" on the problem VM machine and got the following result:
ROOT\MS_L2TPMINIPORT\0000 : WAN Miniport (L2TP)
VMBUS\{F707443A-07E2-43D0-AB22-6492FEE97663}\5&296C0F0E&0&{F707443A-07E2-43D0-AB22-6492FEE97663}: Microsoft Virtual Machine Bus Network Adapter
ROOT\MS_NDISWANBH\0000 : WAN Miniport (Network Monitor)
ROOT\MS_NDISWANIP\0000 : WAN Miniport (IP)
ROOT\MS_NDISWANIPV6\0000 : WAN Miniport (IPv6)
ROOT\MS_PPPOEMINIPORT\0000 : WAN Miniport (PPPOE)
ROOT\MS_PPTPMINIPORT\0000 : WAN Miniport (PPTP)
ROOT\MS_SSTPMINIPORT\0000 : WAN Miniport (SSTP)
ROOT\*ISATAP\0000 : Microsoft ISATAP Adapter
VMBUS\{6939B49E-B64E-4BE3-AF7E-019211ADE8C0}\5&296C0F0E&0&{6939B49E-B64E-4BE3-AF7E-019211ADE8C0}: Microsoft Virtual Machine Bus Network Adapter #2
ROOT\*TEREDO\0000 : Teredo Tunneling Pseudo-Interface
SW\{EEAB7790-C514-11D1-B42B-00805FC1270E}\ASYNCMAC : RAS Async Adapter
ROOT\MS_AGILEVPNMINIPORT\0000 : WAN Miniport (IKEv2)
Since my network connection is using the Network Adapter #2 , then to remove hidden adapter the I issued the following command:devcon -r remove "@VMBUS\{F707443A-07E2-43D0-AB22-6492FEE97663}\5&296C0F0E&0&{F707443A-07E2-43D0-AB22-6492FEE97663}"
However I get an error message: Remove failed, no devices removed. Is my devcon remove syntax correct?
Jay
EMAIL REMOVEDHi,
In method 1, can you find the dimmed network adapter? How about to use the GUI to remove it.
Method 1
6. Right-click the dimmed network adapter, and then click Uninstall.
Vincent Hu
- By the Way - the message is simply a warning - not a failure.
You can simply assign the IP address and move on - it is NOT necessary to remove old NIC with the duplicate IP.
Brian Ehlert (hopefully you have found this useful) - I started with method one, however the device manager , Network Adapters only shows one of the adapters "Microsoft Virtual Machine Bus Network Adapter2" and there are no sign of the dimmed second adapter.
The only way for me to see the list of both adapters, was when I used "Devcon findall =Net"
Per Brian's comment since the message is only a warning, and if I can not make the "Devcon remove" work, then I am going to live with what I have.
Just figured out the issue,
To see the list of hidden adapter in the device manager, it is important to issue both of the following commands from the command prompt
set devmgr_show_nonpresent_devices=1
Start DEVMGMT.MSC
The reason for the hidden network adapter not showing up was because I was issuing theset devmgr_show_nonpresent_devices=1 from the command prompt and then starting the device manager from Start --> Run and not from the command prompt.
Thanks everyone for the input and education.
EMAIL REMOVED - Thanks! I spent ages trying to work out why the network adapter wasn't showing up. All because I didn't precisely follow the instructions and opened device manager from the start menu. That will teach me!
- Hi Brian,
In my case it was necessary to delete the old adapter as it had a static IP address and a statically assigned gateway. This meant that whenever I rebooted the server it removed the gateway address from the new adapter and I suddenly had no internet connection!
Ben
