I recently installed ubuntu w/ vmware server ontop of this linux distro.....

what's suppose to happen is I go to the following site:
http://NAT ADDRESS:8222

I go there and NOTHING loads....... (It works for weeks!!!) until today....

NO CHANGES WERE MADE WHAT SO EVER......

So I go into the terminal session I stop ALL vmware services: I get the following:

Stopping VMware autostart virtual machines:
Virtual machines failed
Stopping VMware management services:
VMware Virtual Infrastructure Web Access

Lately, I have been experiencing a funny network issue when using VMware Workstation VMs with NAT interface. Roughly, the IP network was working fine, but DNS resolution was not anymore. It happened intermittently, but I could see that this mainly happened when I was suspending my laptop, going to another location and resuming.

Forcing the VM to use a public DNS would solve the issue.

Lately, I have been trying vmware-server 2.0 beta build 63231. It worked pretty well, but for the fact that the Remote Console to the VM was not working through the MUI.

This article will describe the step to take in order to get it working.

At the moment, the vmware-tools provided with workstation 6.0.2 do not compile under Ubuntu Gutsy 7.10.
Only one module fails: vmhgfs. This module allow one to share a folder on the host with the guest.

This tutorial will show the few changes required in order to be able to compile this module, and therefore ease file sharing between the host and the guest.

Since Ubuntu 7.04, Feisty Fawn, Ubuntu is using a standard kernel 2.6.20. Because of a few changes in the API, VMware-server and VMware-workstation 5.5 fail to install under Ubuntu 7.04 Feisty Fawn.

This how-to will show the steps to follow in order to get it install.

Lately I gave a go to VmWare Server. After installing it, I pretty enjoyed installing virtual machines from my desktop environment.
Unfortunately, when I rebooted my computer, I could not used VMware Server Console anymore. This was actually due to the fact that vmware-serverd could not start properly and resulted in configuring vmware as unconfigured.