I am running Centos 5 64 bit. For somer reason i cannot get the windows client to connect to the server. The port is set to 904 as per the install but when i try to connect to the server i get the error the machine is actively refusing it. I do not have a firewall on and the apache server and everything else is running. I can check the status webpage in my browser just fine. Any ideas?
William Warren wrote:
I am running Centos 5 64 bit. For somer reason i cannot get the windows client to connect to the server. The port is set to 904 as per the install but when i try to connect to the server i get the error the machine is actively refusing it. I do not have a firewall on and the apache server and everything else is running. I can check the status webpage in my browser just fine. Any ideas?
Check to be sure xinetd is running and the port is open. And in my case, running VMWare Server the port is 902(default), not 904.
netstat -an | grep LISTEN | grep 902
Likely xinetd isn't running.
nate
when i loaded vmware up it went to 904 on it's own.
netstat -an | grep LISTEN | grep 904 tcp 0 0 0.0.0.0:904 0.0.0.0:* LISTEN [root@enoch ~]# netstat -an | grep LISTEN | grep 902
I gave xinetd a start command as well.
nate wrote:
William Warren wrote:
I am running Centos 5 64 bit. For somer reason i cannot get the windows client to connect to the server. The port is set to 904 as per the install but when i try to connect to the server i get the error the machine is actively refusing it. I do not have a firewall on and the apache server and everything else is running. I can check the status webpage in my browser just fine. Any ideas?
Check to be sure xinetd is running and the port is open. And in my case, running VMWare Server the port is 902(default), not 904.
netstat -an | grep LISTEN | grep 902
Likely xinetd isn't running.
nate
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Jan 27, 2008 7:53 AM, William Warren < hescominsoon@emmanuelcomputerconsulting.com> wrote:
when i loaded vmware up it went to 904 on it's own.
netstat -an | grep LISTEN | grep 904 tcp 0 0 0.0.0.0:904 0.0.0.0:* LISTEN [root@enoch ~]# netstat -an | grep LISTEN | grep 902
I gave xinetd a start command as well.
nate wrote:
William Warren wrote:
I am running Centos 5 64 bit. For somer reason i cannot get the
windows
client to connect to the server. The port is set to 904 as per the install but when i try to connect to the server i get the error the machine is actively refusing it. I do not have a firewall on and the apache server and everything else is running. I can check the status webpage in my browser just fine. Any ideas?
Check to be sure xinetd is running and the port is open. And in my case, running VMWare Server the port is 902(default), not 904.
netstat -an | grep LISTEN | grep 902
Likely xinetd isn't running.
nate
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Registered Microsoft Partner
My "Foundation" verse: Isa 54:17 _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Have you told the Windows clients to use port 904? I have tunneled vmware console through ssh, then I had to tunnel a few ports The ports where, 902,8222,8333 and 80. Then from the vmware console, I connect to localhost, it work nicely
Tronn
yes i have the rule setup in the .ini file to use 904. The web status console works fine..it's the management client on the windows box that won't connect. The windows machine is not firewalled or anti-anything it's wide open. firewall on the centos box is off as well. I'm at a loss..
Tronn Wærdahl wrote:
On Jan 27, 2008 7:53 AM, William Warren <hescominsoon@emmanuelcomputerconsulting.com mailto:hescominsoon@emmanuelcomputerconsulting.com> wrote:
when i loaded vmware up it went to 904 on it's own. netstat -an | grep LISTEN | grep 904 tcp 0 0 0.0.0.0:904 <http://0.0.0.0:904> 0.0.0.0:* LISTEN [root@enoch ~]# netstat -an | grep LISTEN | grep 902 I gave xinetd a start command as well. nate wrote: > William Warren wrote: >> I am running Centos 5 64 bit. For somer reason i cannot get the windows >> client to connect to the server. The port is set to 904 as per the >> install but when i try to connect to the server i get the error the >> machine is actively refusing it. I do not have a firewall on and the >> apache server and everything else is running. I can check the status >> webpage in my browser just fine. Any ideas? > > Check to be sure xinetd is running and the port is open. And in > my case, running VMWare Server the port is 902(default), not 904. > > netstat -an | grep LISTEN | grep 902 > > Likely xinetd isn't running. > > nate > > _______________________________________________ > CentOS mailing list > CentOS@centos.org <mailto:CentOS@centos.org> > http://lists.centos.org/mailman/listinfo/centos > -- Registered Microsoft Partner My "Foundation" verse: Isa 54:17 _______________________________________________ CentOS mailing list CentOS@centos.org <mailto:CentOS@centos.org> http://lists.centos.org/mailman/listinfo/centos
Have you told the Windows clients to use port 904? I have tunneled vmware console through ssh, then I had to tunnel a few ports The ports where, 902,8222,8333 and 80. Then from the vmware console, I connect to localhost, it work nicely
Tronn
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Jan 26, 2008 10:46 PM, William Warren hescominsoon@emmanuelcomputerconsulting.com wrote:
I am running Centos 5 64 bit. For somer reason i cannot get the windows client to connect to the server. The port is set to 904 as per the install but when i try to connect to the server i get the error the machine is actively refusing it. I do not have a firewall on and the apache server and everything else is running. I can check the status webpage in my browser just fine. Any ideas?
Are you specifying to connect to port 904 from the Windows client (VMware Server Console, I assume)? For example, if your server is at IP 192.168.0.100, specify 192.168.0.100:904 in the server address box (likewise, if you connect with a name, just put :904 after the name). 902 is the standard port. However, 902 is allocated in /etc/services already, so VMware bumps it up to 904. If you want to change this, edit /etc/services to comment out the two 902 lines, then rerun vmware-config.pl and tell it to run on port 902. Then you will not need to specify the port explicitly.
Jonathan
that's what i missed. I misunderstood the directions. Now i know in the hostname to put :<port> in there. Let me reinstall vmware and try it again.
Jonathan Berry wrote:
On Jan 26, 2008 10:46 PM, William Warren hescominsoon@emmanuelcomputerconsulting.com wrote:
I am running Centos 5 64 bit. For somer reason i cannot get the windows client to connect to the server. The port is set to 904 as per the install but when i try to connect to the server i get the error the machine is actively refusing it. I do not have a firewall on and the apache server and everything else is running. I can check the status webpage in my browser just fine. Any ideas?
Are you specifying to connect to port 904 from the Windows client (VMware Server Console, I assume)? For example, if your server is at IP 192.168.0.100, specify 192.168.0.100:904 in the server address box (likewise, if you connect with a name, just put :904 after the name). 902 is the standard port. However, 902 is allocated in /etc/services already, so VMware bumps it up to 904. If you want to change this, edit /etc/services to comment out the two 902 lines, then rerun vmware-config.pl and tell it to run on port 902. Then you will not need to specify the port explicitly.
Jonathan _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos