2V0-621 · Question #112
When attempting to connect to a vCenter Server, an administrator observes the following at the top of the vSphere Web Client: Could not connect to one or more vCenter Server…
The correct answer is A. The vCenter Server machine is not responding via the network. B. An incorrect entry for this vCenter Server exists in the Single Sign-On service. C. The SSL certificates do not match the FQDN address for the server. The vSphere Web Client SDK connection error can result from the vCenter host being unreachable on the network, an incorrect SSO registration, or an SSL certificate mismatch with the server FQDN.
Question
When attempting to connect to a vCenter Server, an administrator observes the following at the top of the vSphere Web Client:
Could not connect to one or more vCenter Server Systems:https://vCenter.corp.com:443/sdk What three reasons could be preventing the vSphere Web Client from communicating with this vCenter Server? (Choose three.)
Options
- AThe vCenter Server machine is not responding via the network.
- BAn incorrect entry for this vCenter Server exists in the Single Sign-On service.
- CThe SSL certificates do not match the FQDN address for the server.
- DThe Platform Services Controller is external to this vCenter Server.
- EThe DNS entry for the vCenter Server is incorrect.
How the community answered
(53 responses)- A79% (42)
- D15% (8)
- E6% (3)
Why each option
The vSphere Web Client SDK connection error can result from the vCenter host being unreachable on the network, an incorrect SSO registration, or an SSL certificate mismatch with the server FQDN.
If the vCenter Server machine is offline or network-unreachable, TCP connections to port 443 will time out or be refused, making SDK communication impossible and producing this error.
An incorrect or corrupt registration of vCenter Server in the SSO service prevents the Web Client from authenticating and obtaining the session context required to reach the SDK endpoint.
If the SSL certificate presented by vCenter does not match the FQDN used in the URL (https://vCenter.corp.com), the TLS handshake fails due to a CN or SAN mismatch, blocking all communication with the /sdk path.
An external PSC is a fully supported deployment topology in vSphere 6.x; its presence alone does not prevent the Web Client from establishing a connection to vCenter Server.
An incorrect DNS entry would prevent FQDN resolution before any TCP connection is made, producing a name resolution failure rather than the specific SDK endpoint connection error shown.
Concept tested: vCenter Web Client SDK connection failure root causes
Source: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-8B3DCCD4-D0C1-4B2C-A4E0-89E2625FD40B.html
Topics
Community Discussion
No community discussion yet for this question.