VMware

This Question is Answered

1 2 Previous Next 25 Replies Last post: Jan 31, 2008 4:30 PM by neptune2000  

VMware Fusion 1.1.1 breaks Ubuntu 7.0 networking posted: Jan 29, 2008 10:57 AM

Click to view neptune2000's profile Enthusiast 52 posts since
Dec 28, 2007
I upgraded to 1.1.1, and reinstalled / updated the tools on three guest systems. Here are my exeriences:

1. Windows XP Home Edition: all is good. Everything still works.

2. Red Hat Linux Enterprise Edition 5 Desktop: All is well, after re-running the VMware Tools tarball install.

3. Ubuntu 7.10: this system worked just fine for me in 1.1. After the update and re-running the VMware Tools install, I have no network. Pretty much the system is not usable. I tried to put the net in both Bridge or NAT mode. No difference: Ubuntu 7.10 sees no network hardware available.
Click to view Albertus's profile Novice 8 posts since
Jun 22, 2007
Same thing just happened to me. XP/CentOS 5 work fine. XUbuntu 7.10: no networking at all.

I've reinstalled XUbuntu 7.10 from scratch, installed VMWare Tools and still no network access.

Any ideas?

Click to view Albertus's profile Novice 8 posts since
Jun 22, 2007
Albertus wrote:Same thing just happened to me. XP/CentOS 5 work fine. XUbuntu 7.10: no networking at all.

I've reinstalled XUbuntu 7.10 from scratch, installed VMWare Tools and still no network access.

Any ideas?

It's me again: now it works (2nd attempt)

What I've done:

  1. Install XUbuntu 7.10
  2. Install VMWare Tools and restart
  3. DNS information (which I entered before) wasn't there (??). I've reentered it and now I have network access again.

Click to view Albertus's profile Novice 8 posts since
Jun 22, 2007

Go to Network Settings (click on network icon left to the clock)

Note: I have manual settings here, not DHCP.

You'll see 4 tabs labeled Connections, General, DNS & Hosts.

Just click on DNS and enter your DNS ip. (In my personal case, my ADSL router's ip)

If you have DHCP enabled, try opening first a Terminal(Applications/Accessories/Terminal) and write: 'ifconfig' (without the quotes).

Look for first entry named eth0. On the second line you must have 'inet addr:xxx.xxx.xxx.xxx' where xxx must be a valid ip number.

Then try pinging some other computer on your network.

Hope this helps

Click to view WoodyZ's profile Guru 10,142 posts since
Apr 22, 2004
Ubuntu 7.10 isn't a supported Guest OS and that fact that it worked in a previous release was nice but officially is wasn't and still is not supported. If having to manually configure the network adapter is all that has to be done to get it to work untill it's official supported then that's not such a bad thing to have to do!
Click to view WoodyZ's profile Guru 10,142 posts since
Apr 22, 2004
neptune2000 wrote:Well, then why even add to the release notes specifics about a fix for Ubuntu 7.10? Fixing it in one place and braking in another that worked before is not really good policy. It would have been just better if you'd left it alone.


I beleive they fixed an issue that showed up in Linux VMware Tools that in the last release one member of the comunity found and posted how to manually edit the config file for and another wrote a patch to make it easy to fix for the previous release however I doubt they intentionally set out to break it or anything for that matter! At least there is a work-a-round so stop whining and manually set the information or don't use it! Either way Unbuntu 7.10 is not officially supported yet and therefore you have no rights to gripe!

Click to view WoodyZ's profile Guru 10,142 posts since
Apr 22, 2004
neptune2000 wrote:I guess my bug s different than yours. Ifconfig returns this:

eth0 does NOT have a "inet addr" value associated to it before or after adding the DNS ip of my router (Apple extreme Base Station).

Have to tried assigning it a IP Address, Subnet Mask and Gateway Addresses as well as the DNS Servers?

While I know it's a pain to have to do you should be able to assign the relevant Network TCP/IP Information to allow it to communicate with the Router. Just choose an IP Address that is outside the scope of the DHCP Server Address Pool. Example, Say the Gateway Address is 192.168.1.1 and the DHCP Server Scope is from .100 on the last octet to .149, just set the NIC's IP Address to 192.168.1.99 or lower or 192.168.1.150 or higher. Subnet Mask is most likely 255.255.255.0 and add the reported DNS Servers. Do not use .1 or .255 for the last octet of the NIC's IP Address.


VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities