Hyper-V, 2008R2 client & unidentified network :(

[pooley]

Ok I have a Server 2008 host machine.

 

1 x Server 2008 Virtual Client with Exchange 2007 installed - running fine, has been for 18 months or so.

 

Today I installed 2008R2 as a virtual client, installed fine etc, but it will cot connect to the rest of the network, wont pick up dhcp address, wont ping DC, default gateway etc, but it can (and does) ping the Host server and the other virtual server.

 

I only have 1 Nic installed in the server, have ordered a dual port nic but in my mind sureley both VM's should be able to use the 1 virtual nic (linked to the physical) to gain access to the outside world?

 

Have re-installed the Server os twice today but to no avail.

 

Any tips or am I best just waiting until my new nic arrives?

 

Cheers

[Arthur]

I had a similar issue on Windows 7 and used the PowerShell script below to fix it. Might be worth a try?

 

http://blogs.msdn.com/b/dimeby8/archive/2009/06/10/change-unidentified-network-from-public-to-work-in-windows-7.aspx