Koozali.org: home of the SME Server
Obsolete Releases => SME 7.x Contribs => Topic started by: eiceic on May 22, 2011, 02:04:22 AM
-
I've installed VMware server Version 1.0.9.156507 on two SME servers -- one 7.3 and the other 7.5.1
I can access the 7.3 server with the VMware console on a windows PC but not the 7.5.1
On the 7.3 server, I do these commands and get this...
[root@linux1 etc]# /etc/init.d/xinetd status
xinetd (pid 3887) is running...
[root@linux1 etc]# netstat -tnlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 3813/tcpsvd
tcp 0 0 0.0.0.0:515 0.0.0.0:* LISTEN 3906/lpd
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 3853/tcpsvd
tcp 0 0 0.0.0.0:548 0.0.0.0:* LISTEN 4926/afpd
tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 3995/slapd
tcp 0 0 0.0.0.0:903 0.0.0.0:* LISTEN 3887/xinetd
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 4286/smbd
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 3837/tcpsvd
tcp 0 0 127.0.0.1:783 0.0.0.0:* LISTEN 4218/perl
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 3805/tcpsvd
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 741/httpd
tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 4097/tcpsvd
tcp 0 0 127.0.0.1:980 0.0.0.0:* LISTEN 4133/httpd-admin
tcp 0 0 10.0.0.4:53 0.0.0.0:* LISTEN 19402/dnscache
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 4066/tcpsvd
tcp 0 0 127.0.0.2:53 0.0.0.0:* LISTEN 2788/dnscache
tcp 0 0 10.0.0.4:22 0.0.0.0:* LISTEN 4115/sshd
tcp 0 0 127.0.0.1:3128 0.0.0.0:* LISTEN 4239/squid
tcp 0 0 10.0.0.4:3128 0.0.0.0:* LISTEN 4239/squid
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 4079/perl
tcp 0 0 127.0.0.1:26 0.0.0.0:* LISTEN 2804/perl
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 741/httpd
tcp 0 0 0.0.0.0:1723 0.0.0.0:* LISTEN 4169/pptpd
tcp 0 0 127.0.0.1:4700 0.0.0.0:* LISTEN 4922/cnid_metad
[root@linux1 etc]#
On the 7.5.1 computer I do the same commands and get this... -- why would it show the xinetd is running, but not listening?
[root@linux1 etc]#root@drenchmate-main ~]# /etc/init.d/xinetd status
xinetd (pid 5666) is running...
[root@drenchmate-main ~]# netstat -tnlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 4329/tcpsvd
tcp 0 0 0.0.0.0:515 0.0.0.0:* LISTEN 4426/lpd
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 4366/tcpsvd
tcp 0 0 0.0.0.0:548 0.0.0.0:* LISTEN 5404/afpd
tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 4514/slapd
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 4812/smbd
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 4357/tcpsvd
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 4318/tcpsvd
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 4687/httpd
tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 4600/perl
tcp 0 0 127.0.0.1:980 0.0.0.0:* LISTEN 4642/httpd-admin
tcp 0 0 127.0.0.2:53 0.0.0.0:* LISTEN 4320/dnscache
tcp 0 0 192.168.1.115:53 0.0.0.0:* LISTEN 4249/dnscache
tcp 0 0 192.168.1.115:22 0.0.0.0:* LISTEN 4621/sshd
tcp 0 0 127.0.0.1:3128 0.0.0.0:* LISTEN 4779/squid
tcp 0 0 192.168.1.115:3128 0.0.0.0:* LISTEN 4779/squid
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 4592/perl
tcp 0 0 127.0.0.1:26 0.0.0.0:* LISTEN 3424/perl
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 4687/httpd
tcp 0 0 127.0.0.1:4700 0.0.0.0:* LISTEN 5400/cnid_metad
[root@drenchmate-main ~]#
-
Here's a little more info from the server that I can't communicate with..
http://screencast.com/t/uobMTPHCKN5R
on the good computer, I get this..
[root@linux1 init.d]# config show vmware
vmware=service
status=enabled
[root@linux1 init.d]#
-
why install version 1 when version 2 has been out for awhile
second, i have also had problems in installing vmware, but i have been practicing on another linux version for 64 bit memory
installing vmware server is so wishy washy that it drives me crazy and you will get all kinds of wrong instructions everywhere on the internet or at least instructions that pertain to your individual linux kernel.
I suggest using a test machine to install vmware server then once you have that going then duplicate what you have done on your production machine.
I am a newbie to vmware server by i have used other virtual machines for years.
What i am learning is that you have to pay great attention to any console text messages while installing vmware server.
Also i have had success sometimes in just rerunning the "vmware-config.pl" setup program.
I personally think that in setting up vmware server there is no silver bullet, you have to endure the pains of installation until you get it write and that may will involve making changes to scripts. Basically making jabs at changing code until it installs.
Once you get everything right, just make a tar file from your install directory and transfer that to your working computer using an exact directory structure using the scp command or whatever way you can do so then untar the your transferred file.
After fighting wmware server installs, i would never, i repeat NEVER install vmware on a production server until you have perfected it on a practice server.
What would be best is that somebody could tar the wmware server install on a working machine and you place that on a practice server before you tried it on your production server.