• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 10105
  • Last Modified:

Hyper-V Server only one NIC - all connection lost after creating virtual network

Trying to set-up a test Hyper-V Server on machine with only one NIC.
I know it is not ideal, but should work.
After using Hyper-V manager from a Vista Machine to Create a Virtual Network - External, it says network connection may be temporarily lost. But it never returns!

I have seen http://www.experts-exchange.com/Software/Virtualization/Q_23864532.html 
but can not get anywhere with that.
On Hyper-V server I now have just one available network adaptor, "External Network" - which is the one I created, but the original physical one is gone.. I have tried changing the IP address of the virtual network, but can not get any communications.
PING of the default gateway (which should respond) from the Hyper-V server cnsole gets a "destination host unreachable"

Any idea how to recover comms (Can't use Hyper-V Manager as I can't connect!)
0
dcp002
Asked:
dcp002
  • 6
  • 4
  • 3
  • +1
3 Solutions
 
Amit BhatnagarCommented:
From the CLI within Hyper-V...Can you see the IP Configuration of the Server? It is quite possible that it lost all the IP information when the reset happened.

When you say physical one is gone..What do you mean by that?
0
 
dcp002Author Commented:
Bamit99,

ipconfig shows
Ethernet Local Area Connection 2     with IP address 192.168.1.44 (which is what I originally gave the physical NIC)

Also
Tunnel adaptor local area connection
Tunnel adaptor local area connection 2
both have "media disconnected"

From the Hyper-V Configuration batch file menu,
Option 3 - Networks only shows one network Adaptor - it is number 3 - "External Network" with IP address 192.168.1.44

If I change this to 192.168.1.43, IPCONFIG then reflects the change on the
Ethernet Local Area Connection 2 adapter.

However, try to ping out from Hyper-V console to 192.168.1.254 (my router and gateway) or anything else in the subnet that I know exists, and I just get "reply from 192.168.1.43 - destination host unreachable".
Before I created the virtual adapter, From the Hyper-V Configuration batch file menu,
Option 3 - Networks - it used to show just the physical NIC - which is no longer there.

I believe that when I configured the virtual Network, I did select the VLAN option - unsure that my physical NIC supports that.

I could quickly re-install Hyper-V Server to get back where I was, but that is no help if the same happens again!

Ideas welcome.

regards

dcp002
0
 
Darius GhassemCommented:
Remove any existing Network Adapters for Hyper-V install a Legacy Network Adapter on the Hyper-V machine. See if you get network access.
0
Microsoft Certification Exam 74-409

VeeamĀ® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
dcp002Author Commented:
Dariusg,

I do not understand.
Remove any existing Network Adapters for Hyper-V.   How?

Install a Legacy Network Adapter on the Hyper-V machine.  What do you mean by a legacy network adaptor"?

The machine is a laptop with the only NIC on the motherboard, so physical changing of NICs is impossible - although I have tried adding PC-Card adaptors, but cannot find right drivers for them.

regards,
dcp002
0
 
Amit BhatnagarCommented:
I am creating a small lab to emulate ur environment. Give me some time. Hope to get back with an answer,
0
 
dcp002Author Commented:
Bamit99,
That is very good of you, thanks.  - I will watch for updates.

dcp002
0
 
Darius GhassemCommented:
Go to the settings of the Hyper-V VM by right-clicking the VM in Hyper-V go to settings make sure the VM is shutdown. Once in the settings delete any existing Network Adapters listed. Then select the Add Hardware page and add a Legacy Adapter.
0
 
dcp002Author Commented:
dariusg,

Maybe I did not make it clear. I was not referring to the Virtual Machine - I was referring to the Hyper-V Server itself losing all network connectivity.
If the Hyper-V server has no network connectivity, then
a) Impossible to access any Virtual machine
b) Impossible to access Hyper-V from the Hyper-V manager running on a Vista PC.

Meanwhile I have re-built the Hyper-V server, and created just an INTERNAL network (not bound to any NIC). This has allowed me to run up a virtual machine,and connect to it from Hyper-V Manager, but of course the virtual machine itself has no external network connectivity.

What I want is to be able to configure an EXTERNAL virtual network, bound to a NIC that is still able to function for the Hyper-V management purposes. But if I create an EXTERNAL virtual network, bound to the only possible NIC, I immediately lose all connectivity with the Hyper-V Server.

dcp002
0
 
Darius GhassemCommented:
You are right I was thinking you were talking about the VM not the Hyper-V server I wasn't paying attention.

On the Hyper-V VM what Network Card do you have installed?
0
 
dcp002Author Commented:
dariusg,

It is an Intel 82567LM Gigibit NIC built-in a the Dell Lattitude E6500 laptop. However, I suspect that is not the issue - I had an identical issue previously with a Dell T100 server - but in that case the solution was to add another physical card - not so easy on a laptop.

regards,
dcp002
0
 
Amit BhatnagarCommented:
I tried recreating the issue but it did not help. I am not even sure if we can try and redetect the hardware that is attached with the System since your NIC is not even showing up now.
0
 
dcp002Author Commented:
Solved it.

I asked a question on John Howard's blog at
http://blogs.technet.com/jhoward/archive/2008/06/16/how-does-basic-networking-work-in-hyper-v.aspx?
and he pointed me to
http://blogs.msdn.com/virtual_pc_guy/archive/2009/02/19/script-creating-an-external-virtual-network-with-hyper-v.aspx

The script in that article by Ben Armstrong successfully (despite reporting that it had failed) created an external virtual network switch without losing the connectivity of the Hyper-V Server operating System.

My virtual machines can now access the outside world, and I can still access Hyper-V Server from Hyper-V Manager on an external machine.
0
 
Amit BhatnagarCommented:
Perfect, thanks for sharing the solution !
0
 
medmarc_groupCommented:
I ran into a similar problem when setting up a lab for some testing.  I was running a Physical Server Windows 2008 SP2 x64 and added the HyperV role, which changed me from a single connection to using the Microsoft Virtual Network Switch.  I could no longer change settings on the physical NIC.

The quickest way to resolve and set a static IP for your physical host when using this role is thru the Network and Sharing Center in Windows 2008.  I have attached a screen shot for clarification.  This should resolve any problems you are having.

HyperV-Static-IP-Setting.jpg
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 6
  • 4
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now