Yep, that did it for DHCP. Quoting you link from technogeezer:
"Try configuring your network manually rather than relying on Network Manager in its default roaming settings. Open the Network Manager, and select the "Wired Connection". Click on the "Properties button, which brings up the properties. Uncheck the "Enable Roaming Mode" button, and set "Configuration" to "Automatic Configuration (DHCP). Hit the "OK" button and you will be returned to the "Properties" screen. Make sure the box next to the "Wired Connection" is a check and not a dash."
That worked for me (so now I moved from using the "static address kludge" to DHCP), and I got similar values for ifconfig:
marcopapa@ubuntu-desktop:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0C:29:72:E2:EC
inet addr:192.168.75.130 Bcast:192.168.75.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe72:e2ec/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:59 errors:48 dropped:0 overruns:0 frame:0
TX packets:92 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:38059 (37.1 KB) TX bytes:12695 (12.3 KB)
Interrupt:16 Base address:0x2024
In the thread you refer to, the other way to "re-enable" the net card was this:
"It seems that after disabling roaming some people, including myself, have to run these commands to get networking back up and running:
sudo ifconfig eth0 up
sudo dhclient
(end of quote)
I didn't have to do that, as my previous setting it to "static address" apparently "revived" eth0. It seems that installing VMTools put the eth0 card in "roaming mode" which breaks it and makes it not visible. See this link for the details:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/153635/comments/16
The assumption is that this bug was also present in Fusion 1.1, and there are a number of threads related to this in the Ubuntu forums.
Everything is good. Thanks.
