VMware Communities
TexAustin2
Contributor
Contributor
Jump to solution

Network driver / Ethernet Controller & Fusion 3

So I upgraded my XP virtual machine to Fusion 3 w/o issue. Everything worked fine. I then upgraded XP to Windows 7. When I start Windows 7 it states "NO internet connectivity". When checking device manager you can see no driver is installed for the ethernet controller / networ card. I tried install VM Ware tools again... still no luck.

I have had this same EXACT issue on both my machine at home (iMac) and my work machine (Macbook Pro).

Any help would be much appreciated. Where do I get the driver for the ethernet controller? How can I resolve this issue?

Roger

Reply
0 Kudos
1 Solution

Accepted Solutions
Technogeezer
Immortal
Immortal
Jump to solution

What's kind of NIC hardware is Windows 7 asking about when it asks for a device driver? What does the Device Manager say about the networking card that it's found?

If Windows 7 is like Vista, it probably doesn't have a AMD PCnet NIC driver out of the box. If you upgraded from a Windows XP VM, the NIC is probably being offered to the VM as the PCnet NIC, which would explain why Windows 7 is complaining about a missing driver.

My bet is that Windows 7 VMs have the same default virtual NIC type as Vista VMs. (I don't have a copy of Fusion 3 yet to try this out). The defaults for Vista VMs are, I believe, an Intel e1000 NIC, which Vista had an out-of-the-box driver for. Try shutting down the VM (not suspend), modify the VM's OS type setting to reflect that it's a Windows 7 VM, not a Windows XP VM and then reboot the VM. See if the NIC gets a device driver claimed.

If that doesn't work, shut down the VM, exit Fusion, and add the following line to the .vmx file found in the VM's bundle:

ethernet0.virtualDev = "e1000"

Start Fusion and the VM and see if the device gets a driver assigned properly.

- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides

View solution in original post

Reply
0 Kudos
37 Replies
Technogeezer
Immortal
Immortal
Jump to solution

What's kind of NIC hardware is Windows 7 asking about when it asks for a device driver? What does the Device Manager say about the networking card that it's found?

If Windows 7 is like Vista, it probably doesn't have a AMD PCnet NIC driver out of the box. If you upgraded from a Windows XP VM, the NIC is probably being offered to the VM as the PCnet NIC, which would explain why Windows 7 is complaining about a missing driver.

My bet is that Windows 7 VMs have the same default virtual NIC type as Vista VMs. (I don't have a copy of Fusion 3 yet to try this out). The defaults for Vista VMs are, I believe, an Intel e1000 NIC, which Vista had an out-of-the-box driver for. Try shutting down the VM (not suspend), modify the VM's OS type setting to reflect that it's a Windows 7 VM, not a Windows XP VM and then reboot the VM. See if the NIC gets a device driver claimed.

If that doesn't work, shut down the VM, exit Fusion, and add the following line to the .vmx file found in the VM's bundle:

ethernet0.virtualDev = "e1000"

Start Fusion and the VM and see if the device gets a driver assigned properly.

- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides
Reply
0 Kudos
aggiejy
Contributor
Contributor
Jump to solution

Sounds too simple, but try restarting your mac. There are a couple other threads about some issues with the network adapter, and that could resolve your problem. (assuming you haven't tried that anyway)

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

Hi Roger,

Thanks for the post and sorry about the problems you are having. When you say you upgraded your XP virtual machine to Fusion 3 w/o issue, what did you upgrade from? When you upgraded dod yoou do the tools install at this time? Which version of XP and Window 7 are you upgrading from/to? What OS are your Mac's running? When you installed tools again in your Windows 7 VM did you notice if you received an error during the install of the network driver?

Any additional information you can give me would be helpful. I will try to reproduce this issue in-house.

Sincerely,

Michelle Barreda

VMware Fusion QA

Reply
0 Kudos
sshravan
Contributor
Contributor
Jump to solution

I am having a similar issue. Migrated from parallels, running windows 7. Removed the parallels tool, installed VM ware tools and still no network driver. Everything else seems to be working, but no network. On Fusion 3.

Reply
0 Kudos
TexAustin2
Contributor
Contributor
Jump to solution

Michelle,

Mucho thanks for jumping in and helping me. In answering your questions.

1. I had the latest version of XP with all service packs installed.

2. I successfully installed VMWare 3 & VM Ware tools and XP worked Fine.

3. I then upgraded to Windows 7 Professional.

4. No network (specifically when I look in device manager it states "no driver for ethernet controller").

5. I re-installed VM Ware tools. Still no luck getting network or driver to be recognized.

6. I un-installed VM Ware tools and re-installed. STill no luck.

7. I just rebooted machine, un-installed and re-installed VMWare tools.... no luck

8. I did not receive any error messages during the VMWare tools install.

9. I am running Snow Leopard 10.6

10. The EXACT same issue happen on both my iMac and Macbook Pro (upgraded at different times)

Screen shot of error from Windows 7 device manager attached. Any help appreciated.

Roger

rlewis@alliancetech.com / roger.lewis@mac.com

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

Hi Roger,

What version of XP? Was it professional (32 or 64bit)? Just want to make sure I follow your exact workflow. Can you collect the support information and send it to me? You can do this using the Help menu while Fusion is running. This will create a tgz file that you should be able to email to me.

Thank you,

Michelle Barreda

VMware Fusion QA

Reply
0 Kudos
TexAustin2
Contributor
Contributor
Jump to solution

OH... and I am running the lite version of VMWare (Version 3.0.0 (204229)).

Roger

Reply
0 Kudos
TexAustin2
Contributor
Contributor
Jump to solution

XP Professional 32 bit

Reply
0 Kudos
TexAustin2
Contributor
Contributor
Jump to solution

I am new to these forums. How do I send you the .tgz file? Should I just attach it to this post? I did not see a way to attach it to a private message. Thanks again for all your help.

Roger

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

Yes, you can attach it to the post.

Thank you,

Michelle Barreda

Reply
0 Kudos
pinti59
Contributor
Contributor
Jump to solution

I had the same issue this morning. my 2008 and windows 7 box could not connect to the Network adapter. After reinstalling the tools and rebooting each VM, I rebooted my MAC and everything to seems to be working again.

Reply
0 Kudos
ChrisABass
Contributor
Contributor
Jump to solution

Was there any resolution to this? I am having the exact same issue.

MacBook Pro 2.4 GHz Intel Core 2 Duo 4 GB 667 MHz SDRAM

Vmware 3.0.0

Windows 7 Professional on Bootcamp Partition

Reply
0 Kudos
pinti59
Contributor
Contributor
Jump to solution

have you tried rebooting your MAC? Worked for me.

Reply
0 Kudos
sshravan
Contributor
Contributor
Jump to solution

I had the same issue as mentioned before. Tried reinstalling, rebooting nothing worked. Finally went into Device Manager and told windows to look for the driver, it found it, installed it, took another reboot for it to finally connect. The first time it gave me an IP address conflict.

Try that and see if it works.

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

This post is specifically an issue while upgrading from XP to Win 7. Did you do an upgrade?

Reply
0 Kudos
ChrisABass
Contributor
Contributor
Jump to solution

Yup, rebooted the MAC and still not working

Reply
0 Kudos
ChrisABass
Contributor
Contributor
Jump to solution

Yes I did upgrade from XP Vmware 2.0 -> XP Vmware 3.0 -> Windows 7 Vmware 3.0

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

OK, I am investigating this upgrade process now. Will update to the forum when I have more info.

Thank you,

Michelle Barreda

VMware Fusion QA

Reply
0 Kudos
ChrisABass
Contributor
Contributor
Jump to solution

I have a possible workaround solution. I shut down my Windows 7 Vm and in the VmWare Network Adapter Settings Control Panel I tried changing the setting from NAT to Bridged. That didn't seem to do anything.

I then added a new Network Adapter and set it to Bridged while having an existing NAT Network Adapter and when I restarted my vm the network adapter was properly installed.

I don't know why it worked but it did. I'll let you know if it stops working.

Reply
0 Kudos