Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Access VMWare 2.0 Server with Apache installed (Resolved)
The latest VMWare as switched to using a browser plugin to do all management of your virtual machines. And as such this means you must access it through http://localhost/ The problem I'm having is that with Apache installed I am unable to get to the vmware server. In order to try and find it I have tried adding the port http://localhost:902 which is the default set for remote access. Unfortunately this does not get me what I want. So I am wondering where I should be pointing my browser or configure my programs.
Last edited by he_the_great; 10-12-2008 at 06:17 PM.
Reason: Resolution found
Apache has absolutely nothing to do with VMware Server and doesn't interfere with it. During the VMWare install, you should have specified a port that it listens to, and that is where you need to connect. If you specified port 902, maybe you should describe what you're seeing so we can help you better.
A search on google gets me some stuff on fedora forms which is a jungle of misunderstanding. And ubuntu which seems to say that I am getting a correct message.
My assumption is that this is the port the VM Client connects to. Problem is I'm trying to get to the VM Client, which before I installed apache was just http://localhost/ and I have reinstalled VMWare with the latest RC2.
My assumption is that this is the port the VM Client connects to. Problem is I'm trying to get to the VM Client, which before I installed apache was just http://localhost/
That is just weird since http://localhost defaults to port 80, and since you didn't have Apache installed, nothing should have been listening there. Unless, of course, you had configured VMWare to listen on port 80.
Anyway, I did some googling and the common thread seems to be that not all bits of VMware seem to start at boot, even if vmware-config.pl runs successfully. Take a look at your running processes for vmware and see what is there. For me it is:
Also make sure that your firewall isn't blocking access to port 902. And while your doing that, have a look at your lsof -i output and see if anything is listening on port 902.
The part I don't get about the Ubuntu thread you linked to is why xinetd is required. Slackware uses inetd, not xinetd and I've got no problems. However, if you haven't already, you might try either installing (or reinstalling) xinetd and see if that makes a difference.
I'm not running a firewall, have been considering setting one up but haven't for the whole I might need to unblock something I don't know about :P I also may not be recalling the whole just going to http://localhost thing, it's been a while.
Anyway, original I had some vmnet stuff and only:
webAccess (Java thing)
I ran vmware-hostd and that gave me vmware-authdlauncher (aka vmware-authdlau) Which listens on port 902. Still no good. And hostd doesn't seem to continue to run.
FYI I'm running Debian, and did try xinetd (confused me because I read it with xine first) didn't help. And tell you what, I might be getting parts for a new computer so I'll probably end up reinstalling too, I'll try and see if I can avoid this problem. (If I get it working I can use a VM to try and reproduce it
Thank you for your help so far, I'll post back with an update.
I have installed the latest VMware on my new system. During the vmware-config.pl stage, it asked for the standard http and https ports after the remote port. It was not doing this before, for what ever reason. The defaults were, http 8222 and https 8333
The defaults were for VMware, and at this point I don't have apache installed but I can get to VMware. Since the setup actually requested port numbers, I don't think I will be having any issues. With my previous system, I had only been asked to provide a remote access port (whatever that is used for), it did not ask the follow up questions about http ports for the vmware server.