vSphere Client "domain controllers in confidence."

Similar Questions

• Install VMware vSphere Client on the domain controller computer

  Hi team,

  How to install VMware vSphere Client on the domain controller computer? Can someone guide me?

  Thank you

  John

  Please follow this link:

  http://www.vmwarearena.com/2015/01/how-to-install-vSphere-client-on-domain-controller-machine.html

  Thank you

  Venance

• logging of errors in vsphere client with the domain credentials

  I have a 5.5 esxi host managed by 5.5 vcenter.

  I need enable a domain user to be a power user on the host, but don't have access to other hosts managed by the vcenter, so I added their domain account to the permissions tab on the host as a power user.

  I want him connect directly to the host by using the client Vsphere and Vcenter not connect at all.

  However, when he tries to connect to the host using the host name, it gets the error:

  "cannot complete the connection due to a bad user name or password"

  I added myself to the host as a power user and I get the same error

  I have added my name from AD domain host, added an entry in my DNS, more I added a domain suffix to the host.

  No change.

  I can log in as root to the host through the vsphere client.

  What Miss me in this Web of permissions?

  THX

  I had already joined the domain of the host and adding the user directly didn't work.

  I finally called in Vmware and has technical support do that too many questions.  Finally, he created a role group on the host via the Vsphere Client containing the options I needed for this user and it worked.

• the root account not working for vSphere Client 5.5, for SSH works fine

  Hey.

  I got this:

  I can connect to vCenter 5.5 by SSH and the root user and password works fine

  I can connect to vCenter 5.5 by vSphere Client and use domain user and everything works fine

  I cant't connection 5.5 by user of vSphere vCenter Client and use of root and the password. I have information on

  "Cannot complete the connection because username or password incorect.

  IM shure I use the right password for root.

  A suggestion?

  

  Ok. Thank you community vExpert and Lukasz of my team, we found easy reason perhaps, but not at the first glance for me

  We had the installer by default "Source of identity" for Active Directory then when I used only root for connection I got the error with wrong password.

  In this possible case is just to connect to vcenter using root@localos credintials.

  

  But in addition we sam of similar mistakes inside the SSO connects:

  Location of the vCenter Single Sign-On log files for vCenter Server 5.1 and 5.5 (2033430) | VMware KB

  /var/log/VMware/SSO/VMware-STS-idmd.log

  2016 06-21 13:57:31, ERROR 142 [IdentityManager] could not authenticate [root] main tenant [vsphere.local]

  javax.security.auth.login.LoginException: failed connection

  at com.vmware.identity.idm.server.provider.ldap.LdapWithAdMappingsProvider.authenticate(LdapWithAdMappingsProvider.java:327)

  at com.vmware.identity.idm.server.IdentityManager.authenticate(IdentityManager.java:2412)

  at sun.reflect.GeneratedMethodAccessor24.invoke (unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)

  at java.lang.reflect.Method.invoke (unknown Source)

  at sun.rmi.server.UnicastServerRef.dispatch (unknown Source)

  to sun.rmi.transport.Transport$ 1.run (unknown Source)

  to sun.rmi.transport.Transport$ 1.run (unknown Source)

  at java.security.AccessController.doPrivileged (Native Method)

  at sun.rmi.transport.Transport.serviceCall (unknown Source)

  at sun.rmi.transport.tcp.TCPTransport.handleMessages (unknown Source)

  to sun.rmi.transport.tcp.TCPTransport$ ConnectionHandler.run0 (unknown Source)

  to sun.rmi.transport.tcp.TCPTransport$ ConnectionHandler.run (unknown Source)

  at java.util.concurrent.ThreadPoolExecutor.runWorker (unknown Source)

  to java.util.concurrent.ThreadPoolExecutor$ Worker.run (unknown Source)

  at java.lang.Thread.run (unknown Source)

  Caused by: com.vmware.identity.idm.InvalidPrincipalException: could not find the main id: {name: root domain: OurAdDomain.local}

  at com.vmware.identity.idm.server.provider.BaseLdapProvider.findAccountLdapEntry(BaseLdapProvider.java:543)

  at com.vmware.identity.idm.server.provider.ldap.LdapWithAdMappingsProvider.getUserDN(LdapWithAdMappingsProvider.java:1715)

  at com.vmware.identity.idm.server.provider.ldap.LdapWithAdMappingsProvider.authenticate(LdapWithAdMappingsProvider.java:323)

  ... 15 more

  2016-06-21 13:57:31, 144 ERROR [IdentityManager] failed to main checkUserAccountFlags [root] for tenant [vsphere.local]

  "2016-06-21 13:57:31, 144 exception ERROR [ServerUtils] ' com.vmware.identity.idm.IDMLoginException: the connection has failed.

  com.vmware.identity.idm.IDMLoginException: failed connection

  at com.vmware.identity.idm.server.IdentityManager.authenticate(IdentityManager.java:2481)

  at sun.reflect.GeneratedMethodAccessor24.invoke (unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)

  at java.lang.reflect.Method.invoke (unknown Source)

  at sun.rmi.server.UnicastServerRef.dispatch (unknown Source)

  to sun.rmi.transport.Transport$ 1.run (unknown Source)

  to sun.rmi.transport.Transport$ 1.run (unknown Source)

  at java.security.AccessController.doPrivileged (Native Method)

  at sun.rmi.transport.Transport.serviceCall (unknown Source)

  at sun.rmi.transport.tcp.TCPTransport.handleMessages (unknown Source)

  to sun.rmi.transport.tcp.TCPTransport$ ConnectionHandler.run0 (unknown Source)

  to sun.rmi.transport.tcp.TCPTransport$ ConnectionHandler.run (unknown Source)

  at java.util.concurrent.ThreadPoolExecutor.runWorker (unknown Source)

  to java.util.concurrent.ThreadPoolExecutor$ Worker.run (unknown Source)

  at java.lang.Thread.run (unknown Source)

  2016-06-21 13:57:31, 144 INFO [IdentityManager] authentication failed for user [root] the tenant [vsphere.local] in milliseconds [4]

  When I used the credentials with appropriate domain name:

  root@localos we received newspapers below:

  2016-06-21 14:11:58, 971 INFO [LinuxNativeAuthDbAdapter] [root] user authentication

  2016-06-21 14:11:58, 974 INFO [IdentityManager] authentication successful for the user [root@localos] [vsphere.local] tenant in milliseconds [3]

  2016-06-21 14:11:58, 984 INFO [LinuxNativeAuthDbAdapter] to get local groups for the [root] user. Recursive? [Yes]

  When I temporary switch the source of identity - "localos" and use the root account to log logs below, we received and I connected without problem:

  2016-06-21 14:14:37, 545 INFO [LinuxNativeAuthDbAdapter] [root] user authentication

  2016-06-21 14:14:37, 549 INFO [IdentityManager] authentication successful for the user [root] the tenant [vsphere.local] in milliseconds [4]

  2016-06-21 14:14:37, 564 INFO [LinuxNativeAuthDbAdapter] to get local groups for the [root] user. Recursive? [Yes]

  Now, for me, more clearly

  Once again thank you

  Sebastian

• VSphere client web - Remote Console error: unable to connect to the connection of mks (name of user and password) incorrect

  Hello

  I am running vmware Fusion on my mac computer. I created a domain with 2 vm ESXI, VSPHERE client and a DC inside the merger. My mac is not inside the area, but can access the area through clearOS router which is also inside the virtual machine. my mac has IP 192.168.2.x and my management in the 10.0.0.x field segment

  When I try to access a virtual machine on my esxi from my mac, I get the error failed to connect to the connection of mks (name of user and password) incorrect. I guess it has something to do with my mac is not in the area, but no idea how I can solve this problem?

  Thank you

  solved by adding the ip address of my ESXI in my macs hosts file

• vSphere client using the name Netbios on ESXi host does not connect using the credentials of a Windows session

  I have 3 ESXi 5.5 hosts, all connected to a single server vCenter, where we try to authenticate directly to the host by using the windows logon credentials. I have installation of the Administrators group of ESX and filled with the admin accounts that I want to be able to authenticate to the host. The Netbios name of the domain is tstdomain (for example) where the domain name is tstdomain.com. If I connect directly to a host and check the checkbox 'Use Windows Session Credentials', the vSphere client will default by using the Netbios name of tstdomain\adminusername and the connection will fail indicating that the username and/or password is incorrect. If I enter the domain name of tstdomain.com\adminusername, I am able to connect to the host without error.

  Does anyone know how get past that this matter have the vSphere client uses the domain name or to use the Netbios name and connect with the credentials to active directory? I looked by editing the file/etc/hosts and checked that the SPN of the host is correct in active directory with the command hostname setspn - l, with no luck on one. I also tried to change the field of research for the Netbios name of tstdomain rather than the tstdomain.com domain name, also did not work.

  Thanks in advance for your suggestions on how to correct the problem.

  Seems that this issue was due to a slow network and the connection timeout when you try to talk to the domain controller. I am able to connect with windows creds now, but the connection is very slow. I increased the default period of 30 to 60 seconds to help work around the problem.

• 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é

• vSphere client of web posting the inventory is empty

  When I connect to my web as admin@system-domain vsphere client, I see an empty inventory.

  In vsphere client it is the things you

  any idea?

  Add + assign permission to user "admin@system-domain" required on the virtual tab permissions Center.

• Cannot save orchestrator in vsphere client of web (v5.5)

  Hello

  We have difficulties registration orchestrator to use in the web client.  Control https://**server-ip**/mob shows that it is registered as an extension and that heart rate were received recently.  However, even after a reboot of the vcenter server services and services of orchestrator, logging out and back in the vsphere client, try to save it manually in the web client, etc is not always appearing.

  When you try to save it manually, what format should be used?  We tried several methods

  1. https://FQDN:8281

  2 https://FQDN:8281 / api

  3. COMPLETE DOMAIN NAME

  4 FQDN:8281

  5. INTELLECTUAL PROPERTY

  6 https://IP

  7 https://IP:8281

  8 https://IP:8281 / api

  All of these methods give a negative result.

  Also, even if SINGLE sign-on is configured, and perform a connection test using configuration orchestrator web page succeeds, we are unable to log into the customer orchestrator!  It indicates that the user is not allowed, even if it's the same user specified in the orchestrator as administrator of the active directory configuration.  Just in case this might help, we use MS SQL Server Enterprise 2012 for the two vcenter orchestrator and.  In order to ensure that orchestrator db was fully complient, we duplicated the DB original vcenter then creates a user in the connection to the db vco and populated SQL tables.  The reported configuration wizard success.  (Note we also tried it with a fresh database and let orcestrator populate tables - which was also successful, but we still had the same problems with integration and customer sign; so to maximize compatibility, in case the db does not have the necessary objects, we have reproduced the vcenter db... the reason for this wsa as orchestrator can use the vcenter server db if installed in "easy" mode)

  We have searched communities and found many people with the same problem, but none of the cases that we found was actually marked "resolved."

  Could someone help us please with it?  Although version 5.5. impressive regarding the progress made and new features, etc., it has been an absolute nightmare of application.  I hope that VMware is working on fixes of bugs because if we had it to do over again, we would stay with version 5.1 for awhile.

  Thanks in advance for your help.  If anyone has had problems with the installation of version 5.5 (fees or upgrade), we can help... just ask me.  At our facility, we had about 6 or 7 different issues to which we have documented resolutions (most are easy to solve, but in a production environment, no downtime is not good!

  Sincerely.

  Post edited by: sietec2 - changed the ports that have attempted to 8081 8281, typo.

  Solved!  After the suggestions from you, I had a hunch and checked the file 'vco.properties'... then noticed something strange.  Here is the content of the file

  INSTALLER_UI = SILENT

  USER_INSTALL_DIR = C: / $Program Files$ / $$ / $VMware Infrastructure$ / $Orchestrator$ / $

  CHOSEN_INSTALL_SET = CS

  VC_Database_User_Name =

  VC_LogOn_User_Name = administrator

  JDBC_URL = jdbc:vdb:vcdb

  VC_web_Service_Http_Port = 8080

  VC_web_Service_Https_Port = 8443

  VC_Http_Port = 80

  VC_Https_Port = 443

  Upgrade_or_Fresh_install_Flag = fresh

  SSL_Certificate_location = C:\ProgramData\VMware\VMware VirtualCenter\SSL\

  Customer_information = Windows user #.

  [email protected]

  SSO_URL =https://Our.domain.com:7444 / sso-adminserver/sdk

  [email protected]

  LS_URL =https://our.domain.com:7444/lookupservice/sdk

  IS_URL =https://our.domain.com:10443 /

  [email protected]

  SSO_DISABLED = 0

  Notice the line "BOLD", VC_LogOn_User_Name, went to the administrator.  Change that to administrator@{ourdomain.com} and restarting the server orchestrator, then logging on and in the web interface of vcenter server resolved the problem and the server of the vco appeared!

  So if anyone has the issue where it won't register in the web client, check the server.properties file in {orchestrator_install_root} and make sure the log the user name is correct for your environment!

  Thanks to those who helped!

• vSphere Client 5.1 & Win2008

  I have the vSphere Client 5.10 build 786111 installed on an XP laptop and it connects to my ESXi 5.10 host ok

  This laptop is really old, so I installed vSphere Client 5.10 on my server, Win2008 R2 SP1. it installed ok, I think. but it connects to the host due to return a connection failure error message.

  I can ssh in the host, I watched the auth.log and syslog.log but I still do not see connection errors.

  his long time I put all that to the top and his race well enough so I do not remember if I have something has configured on the XP machine or ESXi host to allow this XP machine for you to connect or if installing vSphere Client 5.10 on the Win2008 messed up or what.

  any ideas as to what I can check or missed?

  Only in vSphere 5.5 client cannot be installed on the domain controller. Your vSphere installation 5.1 succeeded in server 2008 and you were able to launch the client. probably something is blocking you to access host

• I need some help please (web Vsphere client connection problem with Vcenter)

  Dear professionals

  I can not connect to the server via the customer web vicenter.

  I have installed and configured the following successfully:

  -esxi5.5

  -Win 2008 server1 (installed on AD)

  -Server2 Win 2008 joined to the domain, then I installed on: sso, inventory, customer web Vsphere and vcenter server service

  as you can see in the attached photos, when I double click on the client vsphere of wen I should be able to log on to the server vcenter, but I couldn't do it.

  do not forget that I logged Win 2008 server2 as a domain administrator, then I installed sso, inventory, customer web Vsphere and vcenter server service

  the WebClient service is runningand I tried https://server.example.com:9443 / vsphere client.

  There are more than two things, I noticed:

  -When I turned the web customer service I got the certificate error (see photo).

  -When I typed nslookup in the domain controller I got the error message.  web vsphere client error is related to the DNS error in the domain controller?

  
  

  Please see the pictures attached.

  Please tell me what to do if you have any idea or what is the cause of this problem.

  Please let me know as soon as possible because I've stuck to that point where I can't connect to the via customer web vsphere vcenter.

  Best regards

  
  

  naoufl

  Please register these two servers to the DNS entry field. and make sure both servers firewall set OFF mode.  If the production environment please check the network connection by using the network firewall team.

• Unable to connect to new ESXi 5.5 with vSphere Client hosts

  Completed the new installation of ESXi 5.5 on two new Dell PowerEdge servers last night.

  Trying to connect to them through the vSphere client fails.

  I can ping both servers without any problems from the server where the vSphere client is installed (it is not a domain controller but a Windows 2003 server - it has not .net 3.5 SP1 is installed).

  If I try to open the IP address of the host in a web browser http://xxx.xxx.xxx.xxx expires, however, if I try http://xxx.xxx.xxx.xxx:902 It connects to the server, but rather than get the web page, I'm used to waiting with 5.1 I get this message:

  "220 VMware authentication daemon Version 1.10: required SSL, ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC, VMXARGS taken in charge, taken NFCSSL in charge." I get this exact message even though I have telnet to port 902.  So I know that I can speak to the host, but have no idea why I can't connect to it or they have the tools to display in a web browser. »

  Try to use the same IP address with port 902 in the vSphere client to connect, I get this error:

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

  A unknown connection error has occurred. (The client received an invalid response from the server. (The server committed a protocol violation. Article = ResponseStatusLine))

  I noticed that there was a lag of 2 hours and 4 minutes between the host server and the client's server.  I have reset the time to match up in the BIOS of the host server.  The test gave the same results.

  Probably unrelated, but throw it out there in case it points to an answer, when executing the "Test management network", ping passes to the default gateway and the DNS server secondary (which is Google 8.8.8.8) but fails for the main DNS (local IP) server and host name resolution is faulty.

  Ideas, help or solution would be much appreciated.  I need to get the network to this customer virtualized this week, and I would prefer not to have to go back to 5.1 if possible.

  Thank you

  Mark Bowker

  This is resolved.

  And it's one of those things that you just kick yourself for.

  I tried this on two servers, Server 2003 and using IE8

  Tested a theory using a VPN to my laptop Windows 8 IE 10 and it has worked perfectly, then tested on a Server 2008 R2 using IE9 and it worked perfectly.

  Installed Chrome on the two Server 2003 servers and worked perfectly.

  So in the end it was IE8 that was not compatible and all the problems at the origin!

  Thanks again to you Andrew for trying to help!

  Mark

  Ed.  In fact, this is the exact reason that it did not work

  5.5 use OpenSSL ciphers and we will not be able to run the 2003 32-bit
  http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2049143&sliceId=1&docTypeID=DT_KB_1_1&dialogID=47844467&StateID=1%200%2047848621
  There is a fix for 2003 x 64 but not 32-bit

  Post edited by: Mark Bowker

• vim.fault.HttpFault during the sorting of virtual machines in vSphere Client after update 5.1

  Hello. I recently completed an upgrade to vCenter 5.0 > 5.1. I came across some problems common to the teeth with SSO, but things look ok at the moment. I have a problem I would really in trouble - when you try to sort virtual machines in the vSphere client, I see the following error message:

  Impossible to connect to the web service to run the query. Check that the service 'VMware VirtualCenter Management Webservices' works https://vcenter_server_fqdn: 10443 vim.fault.HttpFault

  It is reproducible on multiple systems running the VI client. The Viclient log shows:

  [viclient:SoapTran:P:43] 10:25:30.193 07-01-2013 invoke 4283 finishing on SessionManager:SessionManager [vcenter_server_fqdn] AcquireSessionTicket - series: 0.000, server: 001.425 [ERROR]

  Vmomi.Fault.SystemError: vim.fault.HttpFault

  to VirtualInfrastructure.ManagedObject.InvokeMethod (MethodName, Object [])

  at Vmomi.SessionManager.AcquireSessionTicket (String)

  at VmomiSupport.Services.AuthenticationTicketSource.Next)

  at VMware.VimServices.Query.Impl.LoginByTicketQueryCommand.CreateWebQuery)

  at VMware.VimServices.Query.Impl.WebCommandBase.Execute)

  at VMware.VimServices.Query.QueryServiceBase.Login)

  at VMware.VimServices.Query.Impl.QueryCommandBase.PreProcess)

  at VMware.VimServices.Query.Impl.WebCommandBase.Execute)

  at VMware.VimServices.Query.QueryServiceImpl.ExecuteQuery (QueryWebCommand)

  at VMware.VimServices.Query.QueryServiceImpl.Query (String, Int32, LanguageId)

  at VMware.VimServices.Search.Impl.Utils.NewResults (ResultsInternal)

  to VMware.VimServices.Search.ResultsImpl.RetrievePage (Nullable'1)

  to VMware.VimServices.Search.FilterOrderObjectSetProviderImpl'1.GetObjectSet)

  to VirtualInfrastructure.ObjectSetPoller'1.DoPoll)

  to VirtualInfrastructure.ObjectSetPoller'1. < survey > b__2 (Object)

  ...

  at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback (Object)

  [viclient:SoapMsg: P:43] 07-01-2013 10:25:30.193 Vmomi.SessionManager.AcquireSessionTicket of application of RMI - 4283

  " <: containing soap envelope = ' http://www.w3.org/2001/XMLSchema "" xmlns: xsi = " " http://www.w3.org/2001/XMLSchema-instance "xmlns:soap =" " http://schemas.xmlsoap.org/SOAP/envelope/ ">

  < soap: Header >

  < operationID > 4C83B7E2-000010BB < / operationID >

  < / soap: Header >

  < soap: Body >

  < AcquireSessionTicket xmlns = "urn: internalvim25" >

  < _This xsi: type = "ManagedObjectReference" type = "SessionManager" serverGuid = "3089D6D0-307C-4B0D-8BD8-94606298C034" > SessionManager < / _this >

  < serviceKey > 1b27d894-3e47-4431-9d7b-c8cb2fd457aa / VIMWEBSVC < / serviceKey >

  < / AcquireSessionTicket >

  < / soap: Body >

  < / envelope soap: >

  Invocation of method error Vmomi.SessionManager.AcquireSessionTicket - 4283

  Message: vim.fault.HttpFault

  XML server:

  " < = xmlns:soapenc soapenv:Envelope ' http://schemas.xmlsoap.org/SOAP/encoding/ "xmlns:soapenv =" " http://schemas.xmlsoap.org/SOAP/envelope/ "container =" " http://www.w3.org/2001/XMLSchema "" xmlns: xsi = " " http://www.w3.org/2001/XMLSchema-instance ">

  < soapenv:Body >

  < soapenv:Fault >

  ServerFaultCode < faultcode > < / faultcode >

  vim.fault.HttpFault < faultstring > < / faultstring >

  < detail >

  < HttpFaultFault xmlns = "urn: internalvim25" xsi: type = 'SystemError' >

  < reason > invalid problem < / reason >

  < / HttpFaultFault >

  < / details >

  < / soapenv:Fault >

  < / soapenv:Body >

  < / soapenv:Envelope >

  [viclient:Error: P:43] 07-01-2013 10:25:30.193 RMI error Vmomi.SessionManager.AcquireSessionTicket - 4283

  < type = "Vmomi.Fault.SystemError error" >

  < message > vim.fault.HttpFault < / Message >

  vim.fault.HttpFault < DetailedMessage >

  < / DetailedMessage >

  lack of < reason > disabled < / reason >

  < / error >

  [viclient:Error: M: 4] 01-07-2013 10:25:30.193 System.Exception: unable to connect to web services to run the query.

  Verify that the 'VMware VirtualCenter Management Web services' service is running on https:// vcenter_server_fqdn: 10443

  to VMware.VimServices.Search.FilterOrderObjectSetProviderImpl'1.GetObjectSet)

  to VirtualInfrastructure.ObjectSetPoller'1.DoPoll)

  Vmomi.Fault.SystemError: vim.fault.HttpFault

  to VirtualInfrastructure.Soap.SoapServiceWrapper.DoInvokeSync (ManagedObject mo, MethodName, methodName, Object [] parameters, Int32 timeoutSecs)

  to VirtualInfrastructure.Soap.SoapTransport.VirtualInfrastructure.Transport.InvokeMethod (pars ManagedObject mo, MethodName, methodName, object [])

  to VirtualInfrastructure.ManagedObject.InvokeMethod (MethodName, methodName, Object [] leave)

  at Vmomi.SessionManager.AcquireSessionTicket (String serviceKey)

  at VmomiSupport.Services.AuthenticationTicketSource.Next)

  at VMware.VimServices.Query.Impl.LoginByTicketQueryCommand.CreateWebQuery)

  -End of the exception stack trace internal-

  [: Sink: M: 4] 01-07-2013 10:25:30.240 error: unable to connect to web services to run the query.

  Verify that the 'VMware VirtualCenter Management Web services' service is running on https:// vcenter_server_fqdn: 10443

  vim.fault.HttpFault

  Stack trace:

  at VirtualInfrastructure.Utils.Log.Trace (String, String, traceCategory)

  at VpxClientCommon.Util.Dialogs.Trace (String, String, String, traceCategory)

  to VpxClientCommon.Util.Dialogs.ShowError (IWin32Window, String, String)

  at VpxClientCommon.ListViewData.OnDisplayMessage)

  at VMware.CustomControls.ListViewEx.DoDisplayMessage)

  at VMware.CustomControls.ListViewEx.WndProc(Message&)

  ...

  at System.Windows.Forms.Application.Run)

  Any ideas/suggestions would be welcome

  My apologies for not updating this post - I completely forgot

  I ended up spending a call with VMware and the resolution in my case was to add my user account in domain directly to the vCenter administrator group - before I had been a member of a group of ESX-Admins who was a member of the Administrators group. I hope this helps...

• vSphere Client Credentials

  Hello

  Whenever I want to connect to vCenter I have to enter 'Domain\username' to the vSphere Client GUI.

  Is it possible to set a domain, while I just enter the username (without the domain name)?

  Concerning

  Hello

  You use 5.1 I presume?

  Take a look at steps enclosed in http://communities.vmware.com/message/2115795 , if so, to see if that helps

• VSphere client, cannot connect to Vmachine on ESXi5

  Hello

  I hope someone can helpme or guide me on this one.

  I already create two VMs on ESXi5 and their spouse on my domain, I can controlit from the console on esxi (via vsphere client)

  but... If I try to connect directly to the vmachine of my office via vsphere client I had a conection error

  I try with my domain user and the password

  I try with the checkbox "use the same windows credentials" and still the same...

  I thought maybe I give permmits to the vmachine directly from Esxi5, but I noticed that does not show in my area and I can't add my name of user or groups. I wonder if theres some how to join my esxi5 welcome to my domain and then can show my domain name such as an option to choose some users of group or individual userid

  (see attached)

  Thank you and have a nice day of departure (sound almost 07:00)

  Sawyer_MX wrote:

  I thought maybe I give permmits to the vmachine directly from Esxi5, but I noticed that does not show in my area and I can't add my name of user or groups.   I wonder if theres some how to join my esxi5 welcome to my domain and then can show my domain name such as an option to choose some users of group or individual userid

  You can join your ESXi your unter AD-> authentication services configuration.

  But that can only be allows you to assign permissions to allow users to connect to your server ESXi with the vSphere Client and do things over there, like create virtual machines or use its console your AD.

  To access the operating system inside the virtual machine remotely, use RDP, VNC, XDMCP, etc as a.p. said

  Concerning