-
1. Re: Network driver / Ethernet Controller & Fusion 3
Technogeezer Oct 27, 2009 5:03 PM (in response to TexAustin2)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.
-
2. Re: Network driver / Ethernet Controller & Fusion 3
aggiejy Oct 27, 2009 6:04 PM (in response to TexAustin2)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)
-
3. Re: Network driver / Ethernet Controller & Fusion 3
leftideas Oct 27, 2009 6:20 PM (in response to TexAustin2)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
-
4. Re: Network driver / Ethernet Controller & Fusion 3
sshravan Oct 27, 2009 7:23 PM (in response to TexAustin2)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.
-
5. Re: Network driver / Ethernet Controller & Fusion 3
TexAustin2 Oct 28, 2009 9:50 AM (in response to leftideas)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
-
NetworkError.tiff 888.9 K
-
-
6. Re: Network driver / Ethernet Controller & Fusion 3
leftideas Oct 28, 2009 9:53 AM (in response to TexAustin2)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
-
7. Re: Network driver / Ethernet Controller & Fusion 3
TexAustin2 Oct 28, 2009 9:54 AM (in response to TexAustin2)OH... and I am running the lite version of VMWare (Version 3.0.0 (204229)).
Roger
-
8. Re: Network driver / Ethernet Controller & Fusion 3
TexAustin2 Oct 28, 2009 9:54 AM (in response to leftideas)XP Professional 32 bit
-
9. Re: Network driver / Ethernet Controller & Fusion 3
TexAustin2 Oct 28, 2009 10:00 AM (in response to leftideas)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
-
10. Re: Network driver / Ethernet Controller & Fusion 3
leftideas Oct 28, 2009 10:13 AM (in response to TexAustin2)Yes, you can attach it to the post.
Thank you,
Michelle Barreda
-
11. Re: Network driver / Ethernet Controller & Fusion 3
pinti59 Oct 28, 2009 10:44 AM (in response to TexAustin2)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.
-
12. Re: Network driver / Ethernet Controller & Fusion 3
ChrisABass Oct 28, 2009 10:52 AM (in response to leftideas)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
-
config.jpg 332.6 K
-
-
13. Re: Network driver / Ethernet Controller & Fusion 3
pinti59 Oct 28, 2009 10:54 AM (in response to ChrisABass)have you tried rebooting your MAC? Worked for me.
-
14. Re: Network driver / Ethernet Controller & Fusion 3
sshravan Oct 28, 2009 11:01 AM (in response to pinti59)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.