Industry guru Dave Taylor offers free tech support on a wide variety of technical and business topics, including HTML, Apple iPhone, online advertising, Cascading Style Sheets, Web design, management, Unix, Linux, search engine optimization, online dating, Mac OS X, shell script programming and Microsoft Windows.

How do I enable Ethernet wifi access within VMware for Windows 7?

I've been experimenting with Microsoft WIndows 7 beta on my Mac OS X system through using VMware and while I don't know of anyone else doing this, I have read on the Internet that it's a viable combo. Problem is, when I actually try it, I find that there's no Internet access and Windows 7 complains that there's no "Ethernet driver" installed? How do I fix that?

Dave's Answer:

You're not alone with this problem, the "missing Ethernet driver" error, where opening Internet Explorer in Windows 7, for example, generates the error message "cannot display the webpage" and when you click on "diagnose connection problems" you get to see the new improved Windows Network Diagnostics system run, just to have it report the relatively unhelpful error: "Windows did not detect a properly installed network adapter. If you have a network adapter, you will need to reinstall the driver."

Here's what you need to do, and it involves munging around (yes, that's the technical term) with one of the VMware configuration files. To do this, your first step is to completely shut down VMware and Windows 7 within it.

Done with that? Good. Now you need to find where the system is storing your VMware Windows 7 image.

Probably it's in /Users/your user ID/Documents/Virtual Machines/the name of your Win7 VM

On my system, for example, it's:

/Users/taylor/Documents/Virtual Machines.localized/Windows 7.vmwarevm

In that directory are a bunch of files:

3722496 Windows 7-s001.vmdk
3815936 Windows 7-s002.vmdk
2635904 Windows 7-s003.vmdk
    128 Windows 7-s004.vmdk
 266880 Windows 7-s005.vmdk
    512 Windows 7-s006.vmdk
     24 Windows 7.nvram
      8 Windows 7.vmdk
      0 Windows 7.vmsd
      8 Windows 7.vmx*
      0 Windows 7.vmx.lck/
      8 Windows 7.vmxf
   1584 vmware-0.log
    280 vmware-1.log
    144 vmware-2.log
    784 vmware.log

The file we seek is called "partition name.vmx". Mine is "Windows 7.vmx". In that file are a few lines that define the Ethernet configuration:

ethernet0.present = "TRUE"
ethernet0.connectionType = "nat"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet0.linkStatePropagation.enable = "TRUE"

You need to add one line to the file here:

ethernet0.virtualDEV = "e1000"

This can be easily done with "TextEdit" or any other editor that'll leave the file as plain text. I used the "vi" editor within the "Terminal", but I'm kind of old school in this regard.

With this line added, simply restart your VMware, restart Windows 7 and, if the bitgods are with you, you'll find that you miraculously have Internet connectivity!

If not, make sure you have networking enabled, and that you've selected NAT:

Hope that helps you get up and online with Windows 7 on your Mac. It's a weird concept, but it's helpful to know what's coming!

Help others find this article at Del.icio.us, Digg, Netscape, Reddit, and Stumble Upon

Categorized: Mac OS X Help , Windows Help (Article 8858)
Tagged: mac os x, microsoft windows 7, virtual machines, vmware fusion
Previous: Advertising through Social Networks?
Next: How do I recover a hijacked Web site?

Subscribe!

Never miss another useful Q&A article again! Subscribe to AskDaveTaylor with Google Reader.

Comments

That was a SUPER solution by Dave...
It worked like a GEM....

Posted by: Dominic at May 12, 2009 3:21 AM

Awesome.
I lost a lot of time on this problem but still, you made me save a lot.
Many thanks !

Posted by: mehdi at May 26, 2009 10:51 AM

This was exactly what I needed to make my installation talk to the network. Just what the doctor ordered and saved me tons of time wondering why things weren't connecting.

Posted by: Cliff at June 24, 2009 2:17 PM

I have the following situation.

VMWare Fusion - Windows 7
Networked using "Bridged"
I can see my home other computers on my home network. But I can not access the internet. Windows 7 keeps suggesting to reboot the physical router!

If I change the network type to "NAT" from "Bridged" I have the opposite problem. I have internet access but can not see other computers on the home network.

Please help!

Thanks!

Posted by: Jeff at July 21, 2009 11:12 AM

I have the same problem as described by Jeff above. That is:

Environment: Windows 7 (RTM) running on Mac OS X VMWare Fusion 2.0

If I set the network adapter to NAT, I have internet access but can't see my home network.

If I set the network adapter to 'bridged' I can see the home network but can't access the internet.

Whats going on and how can I fix this?

Thanks.

Posted by: Dennis Lillee at August 18, 2009 11:55 PM

Great Man!!!
Thank you so much!
It works!

I use Boot Camp partition and on my Mac virtual machine config files stores in
/Users/epavlov/Library/Application Support/VMware Fusion/Virtual
Machines/Boot Camp/%2Fdev%2Fdisk0/Boot Camp partition.vmwarevm/
It's not the directory. I had to open it in another file manager, not in Finder.

Thank You once again!

Posted by: Pavlov at August 30, 2009 4:44 AM

Guys, Having the same problem I selected "bridged". I went into the adapter properties, set a fixed IP address like (192.168.1.117) mask 255.255.255.0 gateway 192.168.1.1 and DNS 192.168.1.1 (these depend on your network and router. Doing so this worked fine but not for NAT! When I run a VPN with my IP set to automatically selected I can connect normally so the problem is with WIN7 (Vista) there is an error in obtaining an IP address from the router using bridged and NAT connections so try to fix (assign yourself) an IP address and hope it works for you! :-)

Posted by: ammoun at November 7, 2009 6:52 PM

To be fair the error is evidently that of VMware not Win 7!

Posted by: ammoun at November 7, 2009 7:20 PM

Just to confirm, if I set my own IP address, Gateway IP and DNS IP, my "Bridged" network adapter works fine and I can see my network printer ...etc. If I leave the IP to Automatic then I cannot see the printer, my "Bridged" network adapter setting does not connect to the internet, my "NAT" connects, however it fails to see local network, only the internet! This is weird and most definitely has to do with the VMware/Win 7 combo failing to obtain and IP address (register on the network) properly. Any suggestions from anyone? I do not wish to keep my IP set as I move from one WiFi network to another at different venues.

Posted by: ammoun at November 10, 2009 2:50 AM

I just tried a fresh Win 7 installation with Parallels Desktop 5 and it is exactly the same problem as with VMware Fusion 3 with Win 7. So.... it seems that the problem is Win 7 (and Vista before it)!
So I withdraw my comment up there the error is that of Windows 7 not VMware!
This is as far as my knowledge goes! Anyone with an answer?
Bless you all.

Posted by: ammoun at November 11, 2009 3:08 PM

Helllo
I have same problem with Ethernet controller but not sure understand when you mention to shut down VMware and Windows 7, need how to find VMware tomake this change

Posted by: darviol at November 11, 2009 7:59 PM

Guys,
I just changed my router to Belkin (from LiveBox that came with my ISP provider subscription) and my NAT and BRIDGED networks both worked well!! It seems that neither VMware Fusion v3 nor Windows 7 are at fault, it was my router!! So please try to change your routers or fiddle with the settings!
Bless you all.

Posted by: ammoun at November 17, 2009 6:46 AM

I am sorry, I rushed my comment! I restarted and found out my NAT network does not "see" my printer or other computers on my local network! We are back to square one with no help from VMware or Microsoft!

Posted by: ammoun at November 17, 2009 7:11 AM

My final comment and the resolution of my problem; as explained to me by the VMware support (very good people indeed); NAT networks use virtual IP addresses assigned by the virtual machine's DHCP not by the router and hence the virtual machine is not given an IP in the physical local network which explains why NAT networks do not "see" network printers and other computers on the physical network (router and devices connected to it), it only connects to the internet through the NAT (and router) and connects to the MAC of course.
Bridged networks, however, obtain an address from the DHCP of the router and are, therefore, part of the physical network and hence can "see" the local network devices and other computers connected to the router and are on the network along with the MAC of course.
The above has been the case since I changed my router and so I am now OK. Support tells me that some routers act weird and for some reason refuse to assign IPs to some computers on the network and this is documented with several models out there. So, if your computer is not able to get an IP from the router or the router is failing to act as a DNS for your network in Bridged network configuration, then try another router before anything else.
I hope this is useful to someone.
Good luck to all and God bless.

Posted by: ammoun at November 17, 2009 4:18 PM

I have something to say, now that you mention it, but ...

I do have a lot to say, and questions of my own for that matter, but first I'd like to say thank you for all your efforts on this Web site by buying you a cup of coffee!

I do have a comment, now that you mention it!