In this article, we will discuss one issue respecting the "Authenticity of the host certificate is not verified." At the vCenter server, we can't make any change in the connected host or we can't add the host into our vCenter server.
There are two possible reasons that can be responsible for this problem. The first one is the double DNS entry. And the second one is changing the hostname for the ESXi host machine. We will start using the second one.
If we change the hostname for the ESXi host machine that is already connected to the vCenter server then this issue will arise. The reason behind that, during joining the ESXi host machine to the vCenter server a certificate has been issued by the vCenter server for that ESXi machine using that machine hostname. That's why if the hostname is changed after adding the ESXi host to the vCenter server the certificate value will be mismatched for that ESXi machine and that error message will have appeared. For that, to resolve this issue just replace your hostname with the previous one if you changed it.
Now we will discuss the first one means double DNS entry. If we get that error message during adding a host to the vCenter server, then the possible reason for that is double DNS entry. If there are two entries available for the same hostname but with a different IP address then this issue will have arisen. The computer will get confused about what entry it will use to reach the destination. To resolve this issue just remove one entry.
That's it. No more problem will have appeared.
No comments:
Post a Comment