Title: VMWare Fusion networking problem solved!
Post by: andreas_g on October 28, 2009, 01:16:32 PM
Post by: andreas_g on October 28, 2009, 01:16:32 PM
Finally i have solved the networking issue, that existed for VMWare Fusion users since v2.0.1!
It was not possible to set up a network connection, because the VMXNet driver did not load correctly.
Now this is the solution:
Under Mac OS X find the file your virtual machine is stored in (usually it is called something like "name_of_your_virtual_machine.vmwarevm"). Open the file (package) as folder in the finder. Find "name_of_your_virtual_machine.vmx" and open it using TextEdit.
Within the file find the line: ethernet0.virtualDev = "e1000"
Delete this line!
That's it!
After booting NeXTStep (you will have to hit ctrl-c at some point during start up) go to the HostManager and open "local..." select "Use local domain only", "Readable only by local net" should be true. As hostname choose whatever you want, for the NIS domain name choose "none". Ignore network time!
Within the Finder open: "/Library/Application Support/VMware Fusion/vmnet8/dhcpd.conf"
There you can look up IP-adress, broadcast-adress, netmask and router-adress. Set your preferences, but do not reboot and quit HostManager.
Within NeXTStep open Edit.app and type only: "nameserver xxx.xxx.xxx.xxx" (where xxx.xxx.xxx.xxx is the adress of the domain-name-server, stored in dhcpd.conf, it is the same as the router-adress)
Hit "alt-shift-r" and save the file as "/etc/resolv.conf"
Now reboot and you should be able to surf the internet!
I hope i could help!
My setup: iMac (early 2009), Mac OS X v10.6.1, VMWare Fusion v2.0.6 running NeXTStep 3.3 with all patches
It was not possible to set up a network connection, because the VMXNet driver did not load correctly.
Now this is the solution:
Under Mac OS X find the file your virtual machine is stored in (usually it is called something like "name_of_your_virtual_machine.vmwarevm"). Open the file (package) as folder in the finder. Find "name_of_your_virtual_machine.vmx" and open it using TextEdit.
Within the file find the line: ethernet0.virtualDev = "e1000"
Delete this line!
That's it!
After booting NeXTStep (you will have to hit ctrl-c at some point during start up) go to the HostManager and open "local..." select "Use local domain only", "Readable only by local net" should be true. As hostname choose whatever you want, for the NIS domain name choose "none". Ignore network time!
Within the Finder open: "/Library/Application Support/VMware Fusion/vmnet8/dhcpd.conf"
There you can look up IP-adress, broadcast-adress, netmask and router-adress. Set your preferences, but do not reboot and quit HostManager.
Within NeXTStep open Edit.app and type only: "nameserver xxx.xxx.xxx.xxx" (where xxx.xxx.xxx.xxx is the adress of the domain-name-server, stored in dhcpd.conf, it is the same as the router-adress)
Hit "alt-shift-r" and save the file as "/etc/resolv.conf"
Now reboot and you should be able to surf the internet!
I hope i could help!
My setup: iMac (early 2009), Mac OS X v10.6.1, VMWare Fusion v2.0.6 running NeXTStep 3.3 with all patches
Title: VMWare Fusion networking problem solved!
Post by: Morgon on October 28, 2009, 05:38:47 PM
Post by: Morgon on October 28, 2009, 05:38:47 PM
Sounds reasonable that my driver can't load if Fusion tries to emulate an EtherExpress 1000 card as suggested by that configuration line.
The original VMWare network driver and thus my VMXNet are using an AMD PCNet32 for initialization before switching to the special VMWare mode.
The original VMWare network driver and thus my VMXNet are using an AMD PCNet32 for initialization before switching to the special VMWare mode.
Title: VMWare Fusion networking problem solved!
Post by: andreas_g on October 29, 2009, 06:56:11 AM
Post by: andreas_g on October 29, 2009, 06:56:11 AM
It seems VMWare silently changed the default network adapter to the "e1000" with VMWare Fusion v2.0.1 and wrote the line to specify it to the .vmx files of all virtual machines.
Removing this line reactivates the previous default network adapter.
This is a little bit wired!
Removing this line reactivates the previous default network adapter.
This is a little bit wired!
Title: VMWare Fusion networking problem solved!
Post by: andreas_g on January 17, 2010, 10:52:41 AM
Post by: andreas_g on January 17, 2010, 10:52:41 AM
Edit:
My first post has been updated:
Do not delete the "localhost" entry using NetInfoManager. This will draw some applications (for example UserManager.app and NetInfoManager.app) unusable.
My first post has been updated:
Do not delete the "localhost" entry using NetInfoManager. This will draw some applications (for example UserManager.app and NetInfoManager.app) unusable.
Title: VMWare Fusion networking problem solved!
Post by: aragon on January 18, 2010, 03:19:34 AM
Post by: aragon on January 18, 2010, 03:19:34 AM
I followed your advice and deleted the 'localhost' entry.
Indeed, NetinfoManager did not work any longer.
I had to restore the Netinfo db from a copy and reboot to get it working again.
Indeed, NetinfoManager did not work any longer.
I had to restore the Netinfo db from a copy and reboot to get it working again.
Title: VMWare Fusion networking problem solved!
Post by: pawel on February 24, 2010, 08:13:37 AM
Post by: pawel on February 24, 2010, 08:13:37 AM
Just tried this method, did't get it to work though. The boot now stops on "Starting network services" for 2.5min and then goes on and stops on "Starting automounter".
I'm not sure I followed you right. In HostManager after setting everything I started up Edit.app and made the "/etc/resolv.conf". Than I pressed "SET" in HostManager where I was followed by 3 statements and than a restart.
Am I not suppose to press "SET" in HostManager?
Also my "/Library/Application Support/VMware Fusion/vmnet8/dhcpd.conf" has a d
I'm not sure I followed you right. In HostManager after setting everything I started up Edit.app and made the "/etc/resolv.conf". Than I pressed "SET" in HostManager where I was followed by 3 statements and than a restart.
Am I not suppose to press "SET" in HostManager?
Also my "/Library/Application Support/VMware Fusion/vmnet8/dhcpd.conf" has a d
Title: VMWare Fusion networking problem solved!
Post by: andreas_g on February 24, 2010, 11:14:22 AM
Post by: andreas_g on February 24, 2010, 11:14:22 AM
I obviously made a mistake in my instructions. As you told, the file is called "dhcpd.conf". I already corrected my initial post. Sorry about that.
Now to your problem:
If you follow the above instructions everything should work well. Personally I did first press "set" in HostManager.app, cancelled the reboot and then quit HostManager.app.
After that I set up "resolv.conf" and then did a reboot.
But I don't think this makes any difference from what you did.
Maybe your configuration got messed up at some point. You may try this:
Type into the Terminal:
rm -rf /etc/netinfo /etc/hostconfig
cd /usr/template/client/etc
cp -rp netinfo /etc
cp hostconfig /etc
reboot
After that you have to do some initial setup again (including setup of user passwords). Try to configure the network again. Follow the above instructions carefully. Maybe it was just a typing mistake you made at some point.
Now to your problem:
If you follow the above instructions everything should work well. Personally I did first press "set" in HostManager.app, cancelled the reboot and then quit HostManager.app.
After that I set up "resolv.conf" and then did a reboot.
But I don't think this makes any difference from what you did.
Maybe your configuration got messed up at some point. You may try this:
Type into the Terminal:
rm -rf /etc/netinfo /etc/hostconfig
cd /usr/template/client/etc
cp -rp netinfo /etc
cp hostconfig /etc
reboot
After that you have to do some initial setup again (including setup of user passwords). Try to configure the network again. Follow the above instructions carefully. Maybe it was just a typing mistake you made at some point.
Title: VMWare Fusion networking problem solved!
Post by: pawel on February 24, 2010, 11:39:33 AM
Post by: pawel on February 24, 2010, 11:39:33 AM
Thanks a lot. I tried again...had the wrong IP-adress.
Now it works!
I got a few Kernel Panics when I googled around, but now it seems to work.
OT :I would need a good FTP-app. Can someone recommend one?
Now it works!
I got a few Kernel Panics when I googled around, but now it seems to work.
OT :I would need a good FTP-app. Can someone recommend one?
Title: VMWare Fusion networking problem solved!
Post by: eagle on June 17, 2014, 09:08:26 PM
Post by: eagle on June 17, 2014, 09:08:26 PM
Andreas, THANK YOU so much for this post!
I reinstalled OPENSTEP 4.2 tonight, into Fusion 6 on Mavericks. The vmxnet network driver wasn't working, and through some Google searches I found this post. Changing that fixed it.
Now I need to figure out how to get sound working...
I reinstalled OPENSTEP 4.2 tonight, into Fusion 6 on Mavericks. The vmxnet network driver wasn't working, and through some Google searches I found this post. Changing that fixed it.
Now I need to figure out how to get sound working...
Title: VMWare Fusion networking problem solved!
Post by: emendelson on August 01, 2014, 09:06:07 AM
Post by: emendelson on August 01, 2014, 09:06:07 AM
I just want to add my thanks. One added detail (which will be obvious to most users): when editing /etc/resolv.conf, you need to be logged in as root. Or at least I needed to be logged in as root.
Also, if you have a Windows VM installed on the same Fusion setup, you don't need to search for the Fusion conf file (which is now at a different location from the one listed in the original post). Just run the Windows machine, enter IPCONFIG at the command prompt, and get the router address from the output. As far as I can tell, this address will always be 192.168.xxx.2, but xxx will be different in different Fusion (or VMWare Workstation) setups.
Also, if you have a Windows VM installed on the same Fusion setup, you don't need to search for the Fusion conf file (which is now at a different location from the one listed in the original post). Just run the Windows machine, enter IPCONFIG at the command prompt, and get the router address from the output. As far as I can tell, this address will always be 192.168.xxx.2, but xxx will be different in different Fusion (or VMWare Workstation) setups.