up vote 3 down vote favorite
share [g+] share [fb]

I have installed W2k3 R2 VM, since it had at start no network detected i added a legacy network adapter and installed intergration services. Now by recommendations on the comments of ths question I change the legacy network adapter to a tradicional virtual network adapter.

The server is used as DNS and a Domain Controller. Users are working as intended with no problems.

Still i get the "Heartbeat: No contact" message but the icon shows the activity of the server.

What did i do wrong ?

P.S.

As i noticed, i cannot install intergration services as it retruns an OS icompatibility error and update via Windows Update is not possible returning a '0x80072EFE windows update error' enter image description here enter image description here enter image description here enter image description here

link|improve this question
To start you should not use the legacy network adapter if you don't really need. ¿Do you really need it? If not change to a normal network adapter for continue. You can accomplish this task using this procedure technet.microsoft.com/en-us/library/ee956895(WS.10).aspx – Ricardo Polo Oct 15 '11 at 18:36
i only used it because the installation of the server did not found any network so through some reading articles i found that when this happens a legacy network should be installed, and after that the server found network. the server is x86 – Cmosk Oct 15 '11 at 18:49
No @Cmosk. Windows Server 2003 r2 is capable to work with normal NICS, legacy are not nececesary and are very slow. – Ricardo Polo Oct 15 '11 at 19:15
i have unistalled the legacy card but after that no network again on the server. So i have reinstalled it again. Still no contact though – Cmosk Oct 15 '11 at 19:19
Now, using devmgmt.msc do a scan for new hardware and wait if it detects someting. After that Please add to your question the snapshot of all your devices using devmgmt.msc – Ricardo Polo Oct 15 '11 at 19:22
show 5 more comments
feedback

1 Answer

up vote 3 down vote accepted

You have this issue because you are running an unssoported for Hyper-v version of Windows Server 2003 R2. You are running Windows Server 2003 R2 SP1.

You should install the Service Pack 2. Then install the Hyper-V integration services and restart the virtual machine. You will have the virtual NIC working.

Alternative if you really cannot install the Service Pack 2, you can manually install the driver from the integration services ISO using the device manager (devmgmt.msc), but this is not recommended.

link|improve this answer
1  
done it and it is working as intended. Thank you for your help Ricardo. – Cmosk Oct 16 '11 at 20:36
@Richardo: Nice catch! – tegbains Oct 17 '11 at 4:13
1  
Thank you @tegbains :) – Ricardo Polo Oct 17 '11 at 4:15
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.