How is your VM configured to see the network (bridged/nat/host-only)?
Did you answer "move" or "copy" when you first powered on the VM with Player?
I am using version 2.0.4 build 93057 of the player.
When I start it I select Open as I have the redhat linux that stopped working from vmware server
I browse to the .vmx (?) file for the redhat and it starts booting the linux instance.
during the boot it can't 'determining IP information for eth0' and fails on this
The network is bridged and was working on the vmware server version.
I got the same problem running a Ubuntu VM Applicance on the newest VMPlayer 2.0.4 on XP Pro Host. No network. Doesn't matter if the network cards are bridged, NAT, custom to vmnetx. I thought it was a problem with vmx file configuration which it could be, but I found it strange that in the Ubuntu VM while it is playing the only recognized interface is (lo) after running the ifconfig command.
Even after configuraring manually /etc/network/interfaces file for (eth0) and (eth1) they would not startup up. It mentioned something about devices not existing. Although dhclient created the appropriate pid files for all interfaces defined in /etc/network/interfaces. Sounds like an issue with drivers for the bridged virtual ethernet interface.
I am running a Dell Latitude D530 my interfaces are Broadcom Gigabit Ethernet and Intel Wireless Card. Should I just uninstall VMPlayer and install the VMWare Server?
I found some usefull information that might help you out at these posts:
Neither worked for me, although they may work for you.
I finally got it working after staying up all night. Apparently when you run a VM on VMPlayer you cannot install VMWare Tools unless you are running your VM on VMWare Server. This proved to be a problem with my configuration in my vmx file. So in my particular case not only was my /etc/iftab needed to be edited to match the newly created MAC addresses in my vmx file. But the vmx file needed to point to the appropriate vmnet0 and vmnet2 as a bridged network device. My mistake was to use the vmxnet driver instead of the Intel e1000. vmxnet doesn't work without VMWare Tools.
So I needed to change: ethernet0.virtualDev = "vmxnet" ==> ethernet0.virtualDev = "e1000"
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.startConnected = "TRUE"
ethernet0.connectionType = "bridged"
ethernet0.vnet = "/dev/vmnet0"
ethernet0.addressType = "generated"
ethernet0.generatedAddressOffset = "0"
And most important as everyone else has stated the MAC address of your eth0 defined in /etc/iftab must match:
the MAC address in vmx file on line: ethernet0.generatedAddress = "00:XX:XX:XX:XX:XX"
Repeat the process for all network devices including wireless. Just be sure that for every network card listed in vmx and /etc/ifstab match the vnet bridged interface. For my eth0 as defined ethernet0.vnet = "/dev/vmnet0" if running VMPlayer on Windows XP you must run vmnetcfg.exe in the VMPlayer directory and disable automatic bridging and set your network devices to their corresponding vmnet's. This is usually a problem when the machine that is hosting the VM has more than one network interface card. Good Luck.
Thank you for taking the time to post that information. Several months after you posted, I ran into a similar problem when trying to use VMware Player to run a machine that was created under VMware Server. Your fix was not directly applicable to my problem, but reading about your fix opened up a very promising new line of investigation.
Sorry about your having to stay up all night. 'Been there, done that (and gettin' way too old for it these days). Thanks again.
William L. Dye ("willdye")
Lincoln, Nebraska, USA
Appreciate, if someone can provide me the link to download Redhat Enterprise linux / any other suite of Redhat linux vmware appliance. I will be using it for education purpose. Thanks.