Hello!

I'm running VmWare 4.05 (6030) under Windows XP, with 3 vritual machines.

Virtual Machine 1) Windows 2000 + SP4 - running with vmware N.A.T. @ 100%
V M 2) RedHat Linux 9.0 - running with vmware Bridge on eth0 and vmware N.A.T. on eth1 both @100%
V M 3) Fedora Core 1 - running with vmware N.A.T. on eth1 @100% and running with vmware bridge on eth0, with last one not working properly.

I've already tried the fix mentioned on this forum (the one from the vmware manual) and it stops the cable signal problem, but while the N.A.T. device works great with ifup eth1, eth0 just starts trying to get a new IP and after a while it displays this message:

"Determining IP information for eth0... failed."

The bridge protocol is installed on a "real" National Semiconductor DP83815-Based PCI Fast Ethernet Adapter NIC, which is connected to a 3COM Cable Modem.

Has anybody ever experienced this with fedora, because with RH9 it works fine.

BTW, if I check my CM's diagnostic page, the NICs parameters all show up right (even the MAC Address), but the IP shows up as 0.0.0.0 .

PS: I have a felling it has something to do with fedora and vmware 4.05, since fedora isn't officially supported by VmWare.

Thanks in advance!

Yuri1312

Me. too!

There is a problem with link checking... it 'thinks' that the link is down... so the solution is that you add the following lines in to /etc/sysconfig/network-scripts/ifcfg-eth0 (if that is your bridge device in host system).

At the end add the following:

check_link_down () {
return 1;
}

hi
i am running VmWare under Windows XP with Red hat Linux 9

VMnet0 bridged to an automatically chosen adapter
Vmnet1(NAT) used 2 sahre Hosts IP address
VMNET 2 bridged to the USB interface for internet conn.
Vmnet8(host only) a private n/w shared by host

the problem is during boot it shows eth0 enabled but i am not able to connect to the inetrnet

Help


annette