--On Sunday, March 22, 2009 4:04 AM -0700 Warner White
<[email protected]> wrote:
war...@josie:~$ netstat -a | grep ":8"
tcp6 0 0 localhost:8005 [::]:*
LISTEN
tcp6 0 0 [::]:8009 [::]:*
LISTEN
tcp6 0 0 [::]:8308 [::]:*
LISTEN
Yep, so it looks like the VMWare services aren't running.
think that's what I'm trying to do--run it--by doing
https://127.0.0.1:8333 in Firefox.
No, when you do that, you are accessing the server.
I've just now received a message from Dan Coutu and looked, as he
suggests, at /etc/init.d. I found four vmware related scripts in
there--vmware, vmware-autostart, vmware-core, and vmware-mgmt. One look
inside them and I say, "Wow! I don't want to fuss with this without being
very careful."
I didn't see what version of Linux you're running, but typically, you can
do something like this :
sudo /etc/init.d/vmware start
This will start the VMWare services on your box. IT may also display an
error message that indicates what the problem is.
When I do it on mine, I see this :
mhm06...@drwatson:~$ sudo /etc/init.d/vmware start
Starting VMware services:
Virtual machine monitor failed
Virtual machine communication interface done
Virtual ethernet failed
Bridged networking on /dev/vmnet0 done
mhm06...@drwatson:~$
Of course, on mine, VMWare is already running. If you do get an error
about not finding a module for the runnign kernel, you will need to run the
VMWare configuration utility.
sudo /usr/bin/vmware-config.pl
That's my two cents ... maybe it'll help!
Michael
--
--------------------------------o---------------------------------
Michael H. Martel | Systems Administrator
[email protected] | Vermont State Colleges
http://www.vsc.edu/~michael | PH:802-241-2544 FX:802-241-3363
