VMware Communities > VMTN > Desktop Products > VMware Fusion (for the Mac) > Discussions
Up to Discussions in VMware Fusion (for the Mac)

This Question is Not Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
4 Replies Last post: Jun 19, 2009 2:36 AM by fatboy2duplicate
Reply

no internet connection -- no ip address with fusion 2.0.4/ Leopard 10.5.7/Windows RC7

Jun 15, 2009 11:47 AM

Click to view fatboy2duplicate's profile Lurker fatboy2duplicate 3 posts since
Jun 15, 2009
Internet connection (wifi) works great in MacOsX and in boot camp. VM uses boot camp install. Documentation says VM DHCP server supplies "pass through" ip address to VM. I'm guessing that the VMWare DHCP server may not be running. Not sure how to stop/start this and how to check if its running. Tried NAT / Bridge and Host Only. Ipconfig chokes with : "The operation failed as no adapter is in the state permissible for this operation." Any ideas? Thanks
Reply Re: no internet connection -- no ip address with fusion 2.0.4/ Leopard 10.5.7/Windows RC7 Jun 15, 2009 1:36 PM
Click to view n4phth4's profile Novice n4phth4 11 posts since
Sep 18, 2006

Quick possible fix:

  1. Shutdown your VM
  2. Shutdown the Fusion app
  3. From Terminal, execute: sudo '/Library/Application Support/VMware Fusion/boot.sh' --restart
  4. (the password that is asked for in (3) is your Mac user password)
  5. Startup Fusion and your VM
That may or may not work, but it's worth a shot.
Reply Re: no internet connection -- no ip address with fusion 2.0.4/ Leopard 10.5.7/Windows RC7 Jun 15, 2009 3:00 PM
in response to: n4phth4
Click to view fatboy2duplicate's profile Lurker fatboy2duplicate 3 posts since
Jun 15, 2009
Thanks for the suggestion. Stopped VM, Fusion. Ran sudo command in terminal. Started Fusion, VM. Unfortunatle same problem as before. When Windows starts up, the bar graph (for wifi) shows up as an icon at the bottom of the screen, it tries connecting -- or is busy anyway -- and then changes to an icon showing a screen with ethernet cable with a red X, with the error that no adapter was found.
Reply Re: no internet connection -- no ip address with fusion 2.0.4/ Leopard 10.5.7/Windows RC7 Jun 15, 2009 5:02 PM
in response to: fatboy2duplicate
Click to view I_C's profile Enthusiast I_C 40 posts since
Jun 3, 2008
On your mac you can open terminal.app and run : "ps aux | grep -i vmnet-dhcp". You should see some vmware processes running if it is running. I dont use Boot camp; but I have had issues getting Windows Vista and Windows 7 working correctly with NAT. It never seems to trust the connection. Bridged seems to work fine.

You could try setting the network to bridged in fusion. Boot the windows system. Go into device manager and scan for new devices or look for something with a yellow exclamation point.

You could also remove non present devices and then rescan for changes but that would be getting cumbersome. So only remove devices if you are comfortable adding them back later when the system is not a vm.

(to show the non present devices in windows: open a command prompt as administrator, run "set devmgr_show_non_present_devices=1", run devmgmt.msc, select "show hidden devices" devices that arent present look faded out.)

Reply Re: no internet connection -- no ip address with fusion 2.0.4/ Leopard 10.5.7/Windows RC7 Jun 19, 2009 2:36 AM
in response to: I_C
Click to view fatboy2duplicate's profile Lurker fatboy2duplicate 3 posts since
Jun 15, 2009
Hi, I_C, thanks for the suggsetions. Ran the ps-aux and saw the four dhcp tasks. Have tried bridged, didn't change anything.

The only device that had driver problems was the ethernet controller (no driver). It was not identified (just generic).

At this point I created a new VM that did not point to boot camp, but used the iso to create a new VM. It HAS internet connectivity. I checked the ethernet controller, it was an Intel MT 100/1000 pro. I VMed back to boot camp. Identified ethernet controller as Intel pro MT 100/1000. Could not find driver in system 32, but did find it elsewhere and used it as driver for ethernet device (this process copied driver to system 32). Alas, even after restarting with the driver-loaded ethernet device, it made no difference.

I noticed on bootcamp proper, the icon for wireless is a bar graph. On VM it is a PC with an ethernet plug. On bootcamp VM, it starts trying to connect with teh bar graph, but when it fails, it switches over to the pc/ethernet plug icon (with a red x). Maybe there is an incompatability in this area with bootcamp trying to use different software from VM for the purposes of wifi?

Thanks for your suggestions. Since I have a working VM, I could walk away from thi sproblem, but I think it is worthwhile for other users to resolve this.

I must say that the VM of boot camp REALLY SUCKS. It is MUCH slower than booting into boot camp. The VM machine (non boot camp) works great.
Actions
Up to Discussions in VMware Fusion (for the Mac)