Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 189307

Re: Unable to loginwith vSphere Client

$
0
0

dfcv wrote:

 

Hello,

 

I have just finished installing the ESXi 5 server and the vSphere client on the client computer. However, every single time, I am met with a cryptic message:

 

 

The request failed because of a connection failure. (Unable to connect to the remote server)

Call "ServiceInstance.RetrieveContent" for object "ServiceInstance" on Server "172.17.32.20" failed.

 

 

I've captured some packets to see what's going on with the following communique:

 

Client->Server:

 

GET /clients/clients.xml HTTP/1.1

User-Agent: VMware VI Client/4.0.0

Host: 172.17.32.20

Connection: Keep-Alive

 

 

Server->Client:

 

HTTP/1.1 200 OK

Date: Fri, 28 Oct 2011 13:56:56 GMT

Connection: Keep-Alive

Content-Type: text/xml

Content-Length: 373

 

 

<ConfigRoot>
  <clientConnection id="0000">
    <authdPort>902</authdPort>
    <version>5</version>
    <exactVersion>5.0.0</exactVersion>
    <patchVersion>1.0.0</patchVersion>
    <apiVersion>5.0</apiVersion>
  </clientConnection>
</ConfigRoot>
With the exception of a few opening and closing packets, that's all that went between the two. I have redownloaded the client and reinstalled it again, but I am still getting the same error message. Can somebody shed some light on how to get this to work?
Thanks.

Hi

 

follow below three steps

 

1-

  1. Verify that network connectivity exists from the Client workstation to the ESX/ESXi host. For more information, seeTesting network connectivity with the Ping command (1003486).

  2. Verify that the ESX/ESXi Server Management service on the ESX/ESXi host is running. For more information, seeVerifying that the Management Service is running on an ESX host (1003494)andRestarting the Management agents on an ESX or ESXi Server (1003490).

    3.Verify that you can connect from the vCenter Server to the ESX/ESXi host on port 902 (If the ESX host was upgraded from version 2.x and you cannot connect on port 902, verify that you can connect on port 905). By default ESX/ESXi listens on port 902 and therefore if the previous steps are all correct it most means that a physical firewall is blocking connectivity on port 902. For more information, seeTesting port connectivity with Telnet (1003487).

    4.Verify that the configured permissions for the account are sufficient to allow you to log in to the ESX/ESXi host. For more information, seeTroubleshooting permissions errors when connecting to an ESX Server with the Virtual Infrastructure client (1003887).

    if still having problem  plcollect log file
    Gather the VMware Support Script Data. For more information, seeCollecting Diagnostic Information in a VMware Virtual Infrastructure Environment (1003689).


     

    Yours,

    Satya


Viewing all articles
Browse latest Browse all 189307

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>