PrepAway - Latest Free Exam Questions & Answers

What three reasons could be preventing the vSphere Web Client from communicating with this vCenter Server?

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.)

PrepAway - Latest Free Exam Questions & Answers

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:

5 Comments on “What three reasons could be preventing the vSphere Web Client from communicating with this vCenter Server?

    1. Nigel says:

      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




      0



      2
  1. JFS says:

    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




    1



    0

Leave a Reply