problem connecting to the vSphere client

Recently I found myself unable to connect to the Esxi host at the data center via vsphere client 5.5 by multiple computers (Windows 7). It shows:

vSphere Client could not connect to "xxx.xxx.xxx.xxx".

A unknown connection error has occurred. (The client may not send a request to the server. (La connexion sous-jacente a été fermée: une erreur inattendue s'est produite sur un envoi.))

All virtual machines resume normal. And the result of telnet seems normal to port 902:

VMware authentication daemon Version 1.10 220: required SSL, ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC, VMXARGS taken in charge

However, if I access http://xxx.xxx.xxx.xxx:902 . He showed:

VMware authentication daemon Version 1.10 220: required SSL, ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC, VMXARGS taken in charge

SSL: Unknown error SSL

VMAuthdSocketRead: failed to read. The closure of socket for playback.

SSH access has not been enabled, and I can't find any way to access the Esxi host.

Anyone have any idea on the issue?

You can try to restart on the host through DCUI management agents.

This article might help you: VMware KB: restarting on a host ESX or ESXi management agents

Tags: VMware

Similar Questions

  • How to change the IP host address list when you connect in the vSphere client?

    Is it possible to edit the list of hosts/ip I get when connecting in the vSphere client?

    ScreenShot022.png

    Thank you!

    As far as I know it is possible by editing the registry. The key you are looking for is HKEY_CURRENT_USER\Software\VMware\VMware Infrastructure Client\Preferences\RecentConnections

    André

  • Impossible to connect to vCenter Server 5.5 using the vSphere Client

    Hello


    I'm trying to configure VMware Lab home using the link below and I have reached a stage where I need to connect to vCenter Server using the vSphere client.


    http://boerlowie.WordPress.com/2011/12/13/building-the-ultimate-vSphere-lab-part-9-ESXi/


    I installed the package of 5.5 full vCenter server using the simple installation option and it includes vCenter server, single sign - on, Webclient vSphere, vCenter server and vCenter Server inventory service. All the the latter is installed on a virtual machine that is running Windows server 2008 R2 guest OS.


    Whenever I try to open a session on the vCenter Server uses the vSphere client, one of the following error is displayed.


    1. you do not have the permissions to connect to the server 'vCenter server IP address.

    2. cannot complete the connection incorrect username or password-, this error is visible when I do not specify domain\username domain user name and simply enter the user name.


    For the details of the error, please see the screenshots - vSphere_client_1, vSphere_client_2 and vSphere_client_3.


    As suggested in the link below, I tried to create an SPN and then set the SPN (Principal of Service name) and the UPN (User Principal name) in the Active Directory identity Source using the web of vSphere client (please see screenshot vSphere_Webclient_2)


    http://vinfrastructure.it/2014/01/issue-in-logging-into-vCenter-server-using-Windows-ad-credentials/


    To fix the permission error, I tried to add the domain user to the Administrators group on the server vCenter (see screenshot vSphere_Webclient_1).


    However, none of the above-mentioned resolution has worked.


    So can someone please help? I am stuck because of this problem and badly need help to move forward.


    Thank you

    AJMAL

    Able to connect to the vSphere Client do you use the [email protected] account?

    Have you already set up permissions on the server vCenter object?

    André

  • Cannot connect directly to Esx via the vSphere Client.

    Hello

    I can not connect directly to ESX through the le VSphere client. I have the following message:

    "Can not connect to "xxx"vSphere Client. Un unknown connection error has occurred. (

    The customer not able to send a complete application on the server. (Underlying connection was closed. An unexpected error has occurred when sending.)). »

    Le ESX reply to ping et name resolution are correct. They are seen by the vCenter and sshh connection to ESX is possible.

    Version: Esxi, 5.5.0, 1892794
    VSphere Client 5.5.0, 1880841 on Windows XP SP3

    Thank you for your help

    Have a look here: vSphere Client 5.5 and WindowsXP/Windows2003 & #8211; Unknown connection error & laquo; Mike Landry & #8230;

  • Connection to the client with VSphere ESX host makes me download the old version of the VSphere client

    Welcome the OS Version: 5.1.0 - 2013

    Question: When I connect to my guests with the VSphere client it forces me to re-download the VSphere client. As you can see from the attached PDF there pretty much all installed versions. Yet, he's trying to go to vsphereclient.vmware.com to try to download again (which cannot because it is on a closed network). It is meaningless to me, as you can see I have all versions of the installed client. My boss who also has the same installed versions can connect. Actually, I installed 5.1 client so that should be enough. VSphere shows the host to 5.1.0 - 2013.

    Why is this not with my Vsphere client?

    Looks like your Client vSphere is version 5.1.0b (source: Match VMware vCenter 5.1 component Versions |) Virten.NET) and your ESXi host is version 5.1 Patch 4 (KB VMware: Products VMware correlating build numbers to update level )

    You need download the vSphere Client 5.1 update 2 version to directly connect to this host.

  • Can I connect a workflow to the vSphere Client GUI (Web)

    Hello

    I see that in workflows, you can do almost anything, but how can I get users 'normal' trigger / start the workflow? For our team to servicedesk (1st level) I wish I had some workflows that I want to connect to the vSphere GUI client. For example, a right-click on a virtual machine to create a snapshot that requires them to enter the name, days that should last the snapshot, email address and change the number.

    Gabrié

    You must configure vCO to integrate into the web client of vSphere. Once done, you can run workflows from there.

    If you use the vCO device, there is a document that I wrote in the documents tab.

  • Unable to connect to the Web Client

    Hello

    It is impossible to connect to the Web Client. They receive the following error message:

    Error RSL # 29
    Error 2046

    We use vSphere 5.0 U3.

    Hello

    If please try kb article below and choose the right answer if it solves your problem.

    VMware KB: VSphere 5.0 Web Client does not load and displays the error message: Error # 2046 29 with RSL

    Thank you

    RAM

  • Help, I changed the password of root ESXi via powerCli, now I can not connect with the web client or the console.

    Help, I've changed the root ESXi via powerCli password, now I can not connect with the web client or the console, but I can still connect to powerCli. The command I used was;

    SE connect-VIServer esxihostname-user root - password newpasswd

    This production network btw, I have connected to each host and run the above command, these ESXi hosts are not on a domain

    y at - it something I have left out. I really appreciate any assistance that you people can provide.

    Thank you, Joe

    It is probably a longshot, but a lot of things in the land of windows is not sensitive to capital letters as Unix is.  I wonder if your new password you put through powerCLI mixed uppercase in it and if the capitalization was abandoned by command windows powerCLI Analyzer, or he interpreted as all capitals or something.   If you can still get through the powerCLI you could try to reset the password again to something simple without capitalization mixed case and if your password on ESXi strategy requires a special character, try something different than a "$", like a "_" (I find that a '_' is less likely than some other special characters (, as a '-' or a ' / ' to cause problems with analyzers.).

    Edit:

    Another thing, you can try before playing with the password once again, is to create a different username ESXi using powerCLI and see if the password ends up what you think, it should be, and if you can get with the client vsphere using it.  In this way, you can find out if there are some problems with certain characters or Cap through command powerCLI Analyzer without losing your remaining root by powerCLI access.  After some tests, you can understand what went wrong with your initial password change and may be able to fix it with less risk of losing access.  I also assume that you can not create a new username on ESXi who is able to change the root password no matter what authority give you it, otherwise, you could create a new username with PowerCLI, then connect to the client vsphere with it and change the password to root from there.

  • Create a local user with the vSphere Client

    Hello

    I want to create a new user with the permission of readonly. In the vmware documation salon, they say I have to go to the tab local users and groups, but there is no tab with that name.

    And sorry for my English I'm not a native speaker.

    Hi and welcome to communities,

    This tab is visible only when you connect to the ESXi directly with the vSphere Client. You won't see when you connect to a vCenter server.

  • Unable to connect via the Web client

    Dear team,

    Web customer service is installed on the SSO Server (SSO installed on seprate VM), since last year 1 it works very well, but as of today I m not able to connect through webclient get below error

    https://SSO.test.com:9443 / vsphere client / #.

    Unable to connect to the server vCenter Single Sign On https://SSO.test.COM:7444/ims/STSService? wsdl .

    Note: I am able to connect VC via vsphere client but not to Web client.

    concerning

    Mr. VMware

    After you restart the WebClient service, wait 5 minutes. Now, I m able to connect VC via the web client.

    Thanks for all the help and support.

  • Setting up a location of scrape persistent by using the vSphere Client

    Hello

    I have an application on behalf of data store when you configure the location scratch using vsphere client.

    This is the step that I have to perform to set up the scratch location and my query is

    I have to specify the name of the data store for step 10, as what I see through the vsphere client IE Datastore1 (vmfs/volumes/Datastore1/.locker - ESXHostname)

    OR

    What I need to specity the unique id that I am able to see in ESXi console that is to say 50060160c46036df50060160c46036df (/vmfs/volumes/50060160c46036df50060160c46036df/.locker- ESXHostname)

    What would be the effect? Configuration with the name of the data store for the vSphere client.

    You can configure the workspace for ESXi using the vSphere Client:

    1. Connect to vCenter Server or ESXi host using the vSphere Client.
    2. Select the ESXi host in the inventory.
    3. Click the Configuration tab.
    4. Click storage.
    5. Click a data store, and then select Browse.
    6. Create a directory named only for this ESX host (for example, .locker-ESXHostname )
    7. Close the browser to store data.
    8. Click Advanced under software settings.
    9. Select the ScratchConfig section.
    10. Change the configuration option to ScratchConfig.ConfiguredScratchLocation , indicating the full path to the directory.

      For example:

      / vmfs/volumes/DatastoreName /. Locker-ESXHostname


    11. Click OK.
    12. The ESXi host in maintenance mode and restart so that the configuration change to take effect.

    I ran a quick test on my test environment. You can safely enter data store, it will be automatically replaced by UUID data store when required restarting.

    André

  • old question: where to get the latest version of the vSphere client

    Hello

    I reinstalled my W7 SP1.

    I need to access ESXCi 4 host couple and 4.1

    The customer I have in my backup is probably ESXi 4 (always a update option when starting installation).

    As you understand that this client cannot be successfully installed on W7 sp1.

    I get famous:

    ---------------------------
    Could not connect
    ---------------------------
    Error analysis of the file "clients.xml" Server "172.20.32.192".

    Logon will continue, contact your system administrator.
    ---------------------------

    I found a few long threads about this at the suggestion of delete MS KB... I doh't see this KB under updates installed in my W7 (probably due to the SP1).

    I would like to install the client in the normal way. Please provide a link to the latest version of the vSphere client that will allow access to my boxes.

    It cannot find in the section download vmware.com

    THX.

    Michael.

    You can also get it from https://ESXiHOSTNAME/

    The link takes you to the internet: http://vsphereclient.vmware.com/vsphereclient/3/4/5/0/4/3/VMware-viclient-all-4.1.0-345043.exe

  • Disable root for the vsphere client access

    Hello community VMWare,

    I have a need to disable the account root to be able to connect to a server from vsphere with the vsphere client. Is this possible?

    Thank you

    The simple vSphere Client permission can be manipulated with the authorization tab.

    Create a new user and delete permission to the user root.

    Or, if you have vCenter, just leave only the permission of vpxa.

    André

  • Link to maps software iSCSI NIC vmkernal and the vsphere client

    Hello

    IM playing with our VMware 4.1 hosts a Dell Equallogic PS4000E, connection

    So far, I have:

    Created ports VMkernal

    Apply adapters

    The iSCSI initiator enabled

    But apparently, I need to run the following command to bind the ports of iscsi software adapter:

    Add an esxcli swisscsi nic - n vmk # vmhba d #.

    Is anyway in the Vsphere Client?

    Hello.

    Unfortunately, there is no way to do it from the vSphere client.

    Good luck!

  • Problem connecting to the server

    Whenever I open the pictures, I get an alert that reads: 'there was a problem connecting to the server "my-server", which is another Mac on my network.

    If I close the dialogue box, Photos keeps trying to connect and it appears again a few seconds later.

    Does anyone have an idea as Photos is all this and how I can stop doing?

    No idea - don't forget we can not see you if you have details

    We do not yet have an idea what software you use or you use 'MyServer' for

    What are the versions of the operating system and Photos do you use? What is your server? How are you connected to it?

    LN

Maybe you are looking for