VMware Cloud Community
Gary_Elkins
Contributor
Contributor
Jump to solution

VMware Infrastructure Client could not establish the initial connection with Server "local Host"

I recieved this message the first time I tried to login to VC 2.5

0 Kudos
1 Solution

Accepted Solutions
philvirt
Hot Shot
Hot Shot
Jump to solution

Are you running your VI Client from a machine other then Virtual Center?

If so, change the host to the address of the Virtual Center server.

Regards,

Fil

Thanks, phIL

View solution in original post

0 Kudos
6 Replies
philvirt
Hot Shot
Hot Shot
Jump to solution

Are you running your VI Client from a machine other then Virtual Center?

If so, change the host to the address of the Virtual Center server.

Regards,

Fil

Thanks, phIL
0 Kudos
polysulfide
Expert
Expert
Jump to solution

This could also mean the the VMware Virtual Center Server Service isn't running. Check your services applet. Also check your event log for errors.






If it was useful, give me credit

http://communities.vmware.com/blogs/polysulfide

VI From Concept to Implementation

mguruprasad
Contributor
Contributor
Jump to solution

I am facing the same problem with the ESX installtion. Let me tell you what I have done till now.

Installed the VMware Server 2.0 in my PC with XP, created VMware server and installed ESX 3.5 successfully. But unable to open the interface through IE or mozilla even tried the Virtual Infrastructure Client as it says couldnot establish the connection. The following are the steps I tried out.

Able to ping my PC from the server console.

Server is assinged IP address through DHCP

Changed the Hostname

Tried opening the interface with hostname still the same.

Modified the hostfile in VM machine and my computer.

VMware services are running properly.

In IE/Mozilla I am getting Page cannot be diplayed/could not establish connection.

Created the Machine again assigning static IP, still the same.

can I have any of your suggestions on this?

0 Kudos
ShanVMLand
Expert
Expert
Jump to solution

Hello GuruPrasad,

This may fix your problem!

By default, ESX 3.5 blocked all the ports for communicating either way.

Commands:

To query the status

esxcfg-firewall -q

To Allow the Incoming

esxcfg-firewall -allowIncoming

To Allow the Outgoing

esxcfg-firewall -allowOutgoing

So, you need to allow both way traffic. Good Luck.

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
0 Kudos
mguruprasad
Contributor
Contributor
Jump to solution

Hi Shan,

Thanks for your reply but still the same problem. I am trying both ways through explorer and Infrastructure Client. I have created a virtual machine in the VMWare server on which I have installed ESX 3.5. Now when I try opening the interface from my local machine which has XP I get this error.

0 Kudos
maartynp
Contributor
Contributor
Jump to solution

check to see that another service is not grabbing/using port 443.

0 Kudos