Virtual client can't reach host.

[burtininkai]

Dear all,

May be You'll be able to

help me. I just installed ESX server 3.0.1 into one of our physical

servers. All installation completed now and it's running, but I can't get to it

remotely. So address is not responding. I checked all setting few times already.

I tried to sent ping command from another pc on my network, and it's

working in both cases then I am using IP or Host name. Even ssh connection is working.

May be someone has any ideas?

Thanks in advice.

[branfarm1]

I can think of a few things that might prevent remote access to your ESX host.

1. Do you have the HTTP service disabled? Use esxcfg-firewall -q to see if it's enabled

2. Is your physical server behind a firewall? VC uses a handful of ports to connect over to each ESX host and if you're behind a firewall you might need to open those up to that machine.

I pulled this from page 183 in the Server Configuration Guide, http://www.vmware.com/pdf/vi3_server_config.pdf .

VC - VI Client uses port 902.

VI Client to ESX uses port 903

VI Web access uses https, port 443.

VC-ESX uses port 902, 27010 (incoming), and 27000 (outgoing)

That's not an exhaustive list of ports... just a place to start. Someone else out there might know better off the top of their head.

[burtininkai]

Hi,

I've checked already all settings. On esx firewall HTTP is enabled and running. There are no firewalls in my network, I even tried to connect other PC throung cable not through network. Still have no ideas. Reinstalling haven't changed anything.

[AWo]

Are you sure that your browser doesn't try to reach the ESX host via a proxy?

Try to add ":80" at the end of the IP address as this is by default the only port which is allowed to the web service.

AWo

[burtininkai]

I've Tryied it already, so I am sure regarding Proxy. With port 80 it's the same problem.

[AWo]

Do you use VC? Does this work?

Is the web process startet?

Check the ESX firewall settings by using the local ESX console:

esxcfg-firewall -q incoming

esxcfg-firewall -q outgoing

Post the output here.

Try to set the security level to low (for testing) by using:

esxcfg-firewall --allowIncoming --allowOutgoing

service mgmt-vmware restart

AWo

[burtininkai]

No problem, but Like I said, firewall is turned off.

Output:

Incoming ports not blocked by default. Outgoing ports not blocked by default. Chain INPUT (policy ACCEPT 18057 packets, 2275K bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 801 packets, 35432 bytes) pkts bytes target prot opt in out source destination Neither incoming nor outgoing blocked by default Enabled services: CIMSLP CIMHttpsServer vpxHeartbeats AAMClient LicenseClient sshServer CIMHttpServer Opened ports:

[christianZ]

Have you tried

ip address>

[AWo]

Try "netstat -anp | grep 80" and look if something is listenling on port 80

Should look like this:

tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1205/vmware-hostd

Try "https://:443", as you wrote that ssh works.

AWo

[burtininkai]

Output

tcp 0 0 127.0.0.1:8005 0.0.0.0:* LISTEN 896/webAccess tcp 0 0 0.0.0.0:8009 0.0.0.0:* LISTEN 896/webAccess tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 896/webAccess tcp 0 0 131.18.11.1:8080 131.18.105.31:4390 TIME_WAIT -

So like I understand, WeAccess isn't listning on port, to which I am trieng to connect. May be You have any solution to change this?

[AWo]

For me it looks like the web service is not running as vmware-hostd is missing as a process in this list.

Check it by using "/etc/init.d/mgmt-vmware status" and by "ps -e | grep ".vm.". The second test should list a process called "vmware-hostd".

If it is not running start it with "/etc/init.d/mgmt-vmware start"

If it is running restart it with "/etc/init.d/mgmt-vmware restart"

AWo

Message was edited by: AWo

[burtininkai]

Output:

vmware-hostd is stopped Starting (or restarting) Stopping VMware ESX Server Management services: VMware ESX Server Host Agent Watchdog [60G[ [0;32mOK VMware ESX Server Host Agent [60G[ [0;32mOK Starting VMware ESX Server Management services: VMware ESX Server Host Agent (background) [60G[ [0;32mOK Availability report startup (background) [60G[ [0;32mOK checking status vmware-hostd is stopped

So You were right, service stopped but the problem is that I can't start it.

[AWo]

If you have added documents to your post, I can't open them....

Are you logged in as root whil etrying to start the service?

Do a 'grep -lr "vmware-hostd" *' while in "/var/log". If any file is listed wich was modified today (file timestamp), have a look what is written there. Try "mgmt-vmware", too.

AWo

[burtininkai]

No I didn't. Tommorow morning I'll try your suggestions. But for me it's quite strange that it's so difficult to reach ESX server through webAccess. ?:|

[AWo]

Just a note: it isn't hard to use the web frontend, just use the URL and yor are there. Something went wrong with your installation. However, as soon as you get to the website, you better use the Virtual Infrastructue Client for managing the stuff. Under normal circumstances you'll never return to the web frontend.

AWo

[burtininkai]

May be this will help. I'am not sure, but may be.

Growing Up is a small slow death as it is sad. With each centimeter noted on a door jamb, with each new class, with each new read through book children turn to adults. And adults are in the habit to die.

Sergej Lukjanenko.

[AWo]

1. Check your free space on "/var" if it is a partition by using "df -h"

2. Do a "esxcfg-nics -l" and check the status of all physical NIC's. Post it.

3. Use "esxcfg-vswif" to check how your console connection is configured. Post it.

AWo

[burtininkai]

Sorry for may late responce.

Pls find attached info about NIC's and console.

[AWo]

Are you sure all your NIC'S are supported?

Have a look here: http://communities.vmware.com/message/498071

AWo