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.)
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.
D.
The Platform Services Controller is external to this vCenter Server.
E.
The DNS entry for the vCenter Server is incorrect.
Explanation:
Explanation/Reference:
A is correct, network issue.
B is correct as well. vCenter needs to be part of a Single Sign-On service.
C is correct also. The SSL certificates must match with FQDN address.
D is not correct. External deployment: PSC and vCenter
E is not correct. In this case, you would get a non presponse error from your browser.
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2050273
‘C’ normally causes a warning in a Web browser about communicating to a potentially dangerous site. As such, I would rather go with A, B, and E.
I’d say E is definitely not correct. If the DNS entry is wrong, you would not even reach the error described above. You would, instead, get an error (based on the web browser you’re using), that says the DNS entry cannot be found.
With C.. I’m not so sure. But Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth.
– Arthur C Doyle
C is correct
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2050273
Looking at my vCenter shell, there is nothing listening on 443 according to netstat.
Tried restarting and no difference.
# netstat -an | grep 443
tcp 0 0 :::9443 :::* LISTEN
tcp 0 0 :::10443 :::* LISTEN
tcp 0 0 :::8443 :::* LISTEN
tcp 0 0 :::12443 :::* LISTEN