Warner, the symptoms you describe can happen if you're trying to connect
to a port that nothing lis listening on. Since you say that you're
trying to get VMware started it sounds to me like the problem is that
you may be missing a step in starting up VMware. In order to have
something listening on port 8333 a process needs to be started and told
to listen on that port. Typically this happens when you boot the system
as the various startup scripts in /etc/init.d or /etc/rc.d are run. Most
Linux systems use shell scripts in /etc/init.d to start and stop these
long running processes, called daemon processes, and so you should be
able to find a script in there related to vmware that would start a
process that listens on port 8333. After starting that the chances are
that you'll then be able to continue with your web-based setup.
Dan
Warner White wrote:
Keith--
I am following the instructions for VMware server. And the first time
I installed it, they worked. Yes, I am trying to get it up and running
from the machine I installed it on. No, the software is not running
this time. That's what I'm trying to do--get it running. I uninstalled
VMware and then reinstalled, but the same problem.
The setup is one in which VMware uses Firefox as its starting
point--only this time it doesn't work. Now I put
https://127.0.0.1:8333 into Firefox and get the error message, whereas
earlier, with the first installation, before things went wrong, I used
to get the management window for VMware server.
OK--so the address is that of my machine. (I didn't know that.) And
since it used to work, I must have done something to screw it up so
that now it doesn't respond. But what? (And http://127.0.0.1:8222--the
other address they mention for starting it--doesn't work either. Same
error message.)
Hoo boy.
Warner
Warner White
12 Harbor Watch Road
Burlington VT 05401
H: 802-863-0182
C: 802-318-0956
www.warnerwhite.org <http://www.warnerwhite.org>
------------------------------------------------------------------------
*From:* Keith MacMartin <[email protected]>
*To:* [email protected]
*Sent:* Saturday, March 21, 2009 6:40:42 PM
*Subject:* Re: Connection to Server Refused
Hi Warner,
127.0.0.1 is also known as localhost or the loopback address. Pinging
it just means that the machine is pinging itself. Unless something is
really screwy with your networking configuration, that should work.
Are you trying to connect to the VMware server from the same machine
that you installed it on? If not then you'll need to know the name or
address of the machine that VMware is installed on. Is the Vmware
server software running?
Keith
On Sat, Mar 21, 2009 at 5:09 PM, Warner White <[email protected]
<mailto:[email protected]>> wrote:
Vaguers--
I gotta problem.
I've been trying to set up VMware Server 2. I had it running for a
while and was trying unsuccessfully to get it to connect to the
internet and to mount its usb ports, and then it just stopped
running. I would start Firefox, enter https://127.0.0.1:8333
(which used to bring up the management interface for VMware
server) and I kept getting Connection to Server Refused. I've
tried the firewall possibility by running usf allow http (and usf
allow https) and that does not succeed. One of my browsers
suggested that the server may not be configured to allow requests.
(How do I do that? I'm not even sure what server 127.0.0.1 is. I
pinged it and it responds.)
Suggestions?
Warner
Warner White
12 Harbor Watch Road
Burlington VT 05401
H: 802-863-0182
C: 802-318-0956
www.warnerwhite.org <http://www.warnerwhite.org>
