VMware Cloud Community
shedy77
Contributor
Contributor

Cannot find nic driver for Win2k3 X64 after P2V (Intel pro mt 1000)

Can someone help me with this issue. I P2Ved a Windows 2003 std x64 server, after the P2V completed the nic driver for Intel pro MT is unavailable. I saw that vmware tools is trying to install vmxnet but Windows is asking for Intel Pro MT 1000 driver. I verified that the template was correct. I am running ESX 3.5 managed by Vcenter 4.0.

0 Kudos
9 Replies
AWo
Immortal
Immortal

Install the VMware Tools (in every guest, always). These contain all necessary drivers and more important things.


AWo
VCP / VMware vEXPERT 2009

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
shedy77
Contributor
Contributor

Vmware tools is tintalled. When I did an interactive install I saw that its trying to install VMXnet instead of an Intel Driver

0 Kudos
AWo
Immortal
Immortal

That depends on the configuration of teh virtual NIC. If it treis to install a vmxnet it is set to vmxnet. You can use that. But for 64 bit systems the e1000 driver is offered also because most of the 64 bit OS have this one in their package included.

You can go and edit the guest settings and change the vNIC type to e1000.


AWo
VCP / VMware vEXPERT 2009

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
shedy77
Contributor
Contributor

ethernet0.present = "true"

ethernet0.virtualDev = "e1000"

ethernet0.wakeOnPcktRcv = "false"

ethernet0.networkName = "VM Network"

ethernet0.addressType = "vpx"

ethernet0.generatedAddress = "00:50:56:82:79:e4"

it was set to e1000. see above

0 Kudos
AWo
Immortal
Immortal

So what's the status, now? Do you have an active vNIC (or better an actove and working connection in Windows)? Regardless of vmx or e1000.


AWo
VCP / VMware vEXPERT 2009

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
shedy77
Contributor
Contributor

Everytime I start the VM, Hardware wizard starts and asked to install the Driver for the Intel e1000. Currenlty no nic is available or installed

0 Kudos
AWo
Immortal
Immortal

Shutdown the guest, remove all vNIC's, reboot it and open the command line. Enter

set devmgr_show_nonpresent_devices=1

devmgmt.msc

click on "View > Show hidden devices". Remove all the NIC's. Shut it down and add the vNIC again. Start it and reinstall the VMWare Tools.

!! Create a snapshot before you do this!! so you have a point to fall back to.


AWo
VCP / VMware vEXPERT 2009

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
shedy77
Contributor
Contributor

No dice, I even remove and reinstall vmware tools. It still tries to install vmxnet driver

0 Kudos
Scissor
Virtuoso
Virtuoso

Download the driver from Intel's web site.

0 Kudos